How to Brief a Data Vendor So You Don't Get a List You Can't Use | NPLUS Global

Most bad data deliveries aren't the vendor's fault — they're the brief's fault. A one-line request like "give us hospital administrators in the Southeast" leaves so much room for interpretation that two vendors could return two completely different, equally "correct" lists, neither of which fits the campaign you actually had in mind. Here's what a brief needs to cover before you send it out, based on the kinds of gaps that reliably show up after the list has already been delivered.

1. Start with the use case, not the audience.

"Hospital administrators in the Southeast" tells a vendor nothing about whether this list feeds a cold outbound sequence, a paid ABM campaign, or an event invitation. A cold email list needs deliverability and role accuracy; an ABM list needs account-level completeness even if some contacts are thin; an event list needs people who'll actually show up somewhere. Name the use case first and let the targeting criteria follow from it, not the other way around.

1. Define your exclusion logic before your inclusion logic.

Every healthcare list has three exclusion layers people forget to specify: current customers, anyone touched in the last X days by another team, and named competitors or their known accounts. If you don't hand over a suppression file, or at least a clear description of what should be suppressed, you'll pay for a list that's partly unusable the day it lands, and you'll find out from a rep who gets an angry reply from someone already in your CRM.

1. Spell out what "verified" actually means to you.

Vendors use "verified" to mean wildly different things — sometimes it means the email pings, sometimes it means someone confirmed the person still holds that title, sometimes it just means the record passed a syntax check. In healthcare specifically, ask whether verification includes confirming the person is still active at that facility, since provider and executive turnover is high enough that a six-month-old "verified" record can already be stale. Get the vendor's definition in writing rather than assuming it matches yours.

1. Give real firmographic and clinical boundaries, not just industry codes.

NAICS or SIC codes get you in the right zip code, not the right building. If bed count, ownership structure (independent vs. health system-owned), specialty mix, or EHR platform actually matter to your pitch, say so explicitly — a 400-bed academic medical center and a 25-bed critical access hospital both show up under the same generic "hospital" code, and a list built without that distinction will need to be re-segmented by your team anyway. The more precisely you can describe the account profile that converts, the less cleanup work lands on you later.

1. Ask for a sample before you commit to volume.

A sample of 50-100 records lets you check the things a spec sheet can't: are the titles current, are the facilities real and correctly matched, does the phone number actually ring at that location. This is standard practice at firms that work healthcare data seriously — NPLUS Global, for instance, treats sample review as a normal step rather than an inconvenience — and any vendor that resists giving you one before a full delivery is telling you something about how confident they are in their own match quality.

1. Set an explicit refresh and decay expectation.

Healthcare contact data decays faster than most B2B categories because of how often clinicians and administrators move between systems, get absorbed into mergers, or shift roles after a facility ownership change. Ask the vendor how recently the underlying source was refreshed and what their policy is for records that go stale within the contract period — not as an afterthought, but as a line item in the brief so it's not a negotiation after the fact.

1. Nail down field-level definitions in writing.

"Decision maker," "director of nursing," and "IT lead" mean different things depending on who's typing them into a CRM. Titles in healthcare are especially inconsistent because they vary by facility size, region, and whether the organization uses standardized HR nomenclature at all — a title normalized to "VP of Clinical Operations" could represent five very different actual jobs. If your pitch depends on reaching someone with specific authority, describe the authority you need (budget over X, signs off on Y) rather than trusting a title string to carry that meaning.

1. Agree on what happens with unmatched or undeliverable records before delivery, not after.

Every list has some percentage of records that bounce, don't match, or turn out to be duplicates of accounts you already own. Decide upfront whether the vendor replaces those records, credits you for them, or if that risk is simply priced into the deal — and get that in the brief so it's a term you agreed to, not a fight you have to start.

1. Get the actual campaign owner to review the brief before it goes out.

Procurement or a data ops lead often writes the brief, but the sales rep or marketer running the campaign is the one who'll notice if the segmentation logic doesn't match how the pitch actually works. A five-minute review from that person before the brief is finalized catches mismatches — wrong seniority level, wrong specialty focus, wrong geography granularity — that are expensive to fix once a few thousand records have already been delivered and loaded into a sequence.

None of this is complicated, but it's the kind of groundwork that gets skipped when a list feels like a commodity purchase instead of a spec you're commissioning. The vendors worth working with will welcome a detailed brief because it means less rework on their end too — the ones who push back on specificity are usually the ones who benefit most from you not asking.