Community Member
We are a 45-person HR tech SaaS company. First time buying data. I have budget for one list and I don't want to get this wrong. What should I actually be asking for?
Database Providers — Data Operations
For a first HR-tech purchase, specify on two axes and stay loose on everything else: HR function at decision-making seniority, and the company-size band where your product actually works. Those two determine whether the message makes sense to the reader and whether the deal is possible at all. Every additional filter multiplies the reduction in available records, and a list narrowed on five axes is usually too small to learn anything from. The specification that matters, in order: Function over title string. Targeting 'HR Manager' as a keyword misses Head of People, People Operations Lead, Talent Director and a dozen other variants of the same buyer. Ask for the HR function with a seniority band, not a title match. Company size as a hard filter. Most HR tech has a real floor and ceiling — a tool built for 200-person companies fails at 20 and fails at 20,000. Set that boundary firmly, because contacts outside it waste send volume and generate the complaints that damage sender reputation. Industry only if your pitch changes. If you would send the identical email to a logistics firm and a law firm, industry segmentation costs you records and buys you nothing. Our global HR coverage runs to roughly 653K records, with about 415K in the United States — deep enough that you can afford to be specific on function and seniority without dropping below a workable volume. On sizing: work backwards from pipeline. If you need ten opportunities and roughly a third of meetings convert, that is around thirty meetings, which at a 2% positive reply rate means a list in the low thousands. Buy to what you can actually send over the next six to eight weeks, not more — data decays from the day it is compiled, and the tail of an oversized file will be stale before you reach it. One structural point that matters for a 45-person company testing a channel: this is a one-time purchase. No seat licence, no credit balance to burn down, no annual renewal. You own the file. That is the difference between testing outbound as a channel and committing to a platform contract before you know whether it works. Send us the function, seniority band and company-size range and we will return a free sample from that exact segment. Run it through your own verification tool before you buy the full volume — that is what the sample is for.
Database Providers — Data Operations
Note for healthcare outreach in the US: CAN-SPAM governs the send, but if your messaging touches patient data or clinical claims, FDA promotional rules and your own regulatory review apply on top. Physician contact data is business contact information and is not protected health information, so HIPAA does not apply to the list itself — but it does apply to anything a recipient sends back to you.
Replies are reviewed before they appear publicly.
