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

Somewhere in almost every healthcare data postmortem, the same sentence appears: "the list just wasn't usable." Not wrong, exactly — the NPIs validate, the emails aren't bouncing at alarming rates, the job titles match what was asked for. But sales won't touch it, or marketing burns through it in two campaigns and calls it dead. The instinct is to blame the vendor. Increasingly, though, teams that actually dig into what happened find the problem sitting further upstream, in a two-line request that got typed into a chat window on a Tuesday afternoon: "Need a list of cardiologists in the Southeast, 500 contacts, ASAP."

That's not a brief. That's a hope.

As buying committees for healthcare data get more sophisticated — RevOps, marketing ops, and data ops teams increasingly sit in the same room as sales leadership when these requests go out — a quiet shift is happening in how the good ones operate. They're treating the vendor brief less like a purchase order and more like a spec document. The teams still getting burned are the ones still treating it like an order form.

The Brief Is a Filter, Not a Formality

The habit that causes the most downstream pain is describing the destination instead of the decision. "Cardiologists in the Southeast" is a destination. It tells a vendor what box to check, not what the list is actually for. A vendor with reasonable data can absolutely deliver 500 people with "cardiologist" and "Southeast" attached to their record. Whether those 500 people are the right 500 people depends entirely on information that never made it into the request.

What's it for — a webinar invite, an SDR call sequence, a direct mail piece tied to a formulary change? Is the target the physician themselves, or the practice administrator who actually manages vendor relationships? Does "Southeast" mean state licensure, practice location, or health system HQ — because for a multi-site cardiology group, those three answers can produce three different lists? None of this is exotic information. It's the stuff that lives in the requester's head and rarely survives the trip into a ticket.

More teams are catching onto this and building what amounts to a use-case field into every request — not because a vendor demands it, but because it forces internal clarity before the ask even leaves the building. If nobody on your team can answer "what does this contact need to do after they receive this?", the vendor can't either, and they'll default to the broadest reasonable interpretation of your keywords. Broad interpretations are how you end up with technically-correct, practically-useless lists.

Segmentation Logic Is Where Good Briefs Quietly Fall Apart

Even teams that write thoughtful briefs tend to under-specify the segmentation logic, because they think in categories that don't map cleanly onto how healthcare data is actually structured. "Decision-makers at mid-size hospitals" sounds like a segment. It's actually three unresolved questions stacked on top of each other: what counts as mid-size (bed count? revenue? system affiliation?), what "decision-maker" means for the specific product being sold (a CIO buys differently than a director of nursing informatics), and whether "hospital" should include critical access facilities, specialty hospitals, or only acute-care general facilities.

It's becoming common for experienced data ops people to push back on these requests before routing them anywhere — not to be difficult, but because they've been burned enough times to know that ambiguity at the brief stage doesn't disappear, it just gets resolved arbitrarily by whoever fills the list, whether that's an internal analyst or an outside vendor. Someone makes a judgment call. That judgment call becomes your dataset. If it doesn't match the judgment call your sales team would have made, you've bought a list that's wrong in a way nobody can quite articulate until it's already underperforming.

The fix isn't more precision for its own sake — it's naming the ambiguous terms out loud and resolving them before they're handed off. A brief that says "mid-size, defined as 100-400 staffed beds, non-critical-access, and decision-maker meaning clinical operations leadership with budget authority over the department, not just clinical title" takes five extra minutes to write and eliminates the single most common source of list rework.

Exclusions Matter as Much as Inclusions

There's a pattern showing up more in mature data-ops shops: briefs now spend nearly as much space on what shouldn't be in the list as what should. Recently contacted accounts, existing customers, providers in a state where the product isn't yet licensed, practices already flagged by compliance — all of this used to live in a separate suppression step, run after the list arrived, often by someone other than the person who requested it. Increasingly, teams are pushing suppression logic into the original brief instead of treating it as cleanup.

This matters more in healthcare than in most B2B categories because the downside of a bad inclusion isn't just a wasted email — it can be a compliance flag, a provider relations issue, or a sales rep calling into an account that legal has explicitly frozen. The cost of an exclusion nobody specified is rarely visible in the delivery metrics. It shows up two weeks later, in a much worse conversation.

Vendors can build suppression logic against almost anything if it's specified up front — prior engagement history, existing CRM records, licensing status, specialty overlaps that create channel conflict. What they can't do is guess which of these matter to your specific business, because the answer is different for every team and changes quarter to quarter as territories and product lines shift.

The Real Shift: From Ordering Data to Specifying It

Put together, these aren't really three separate tips. They're one shift in posture. The teams getting consistently usable lists have stopped treating the brief as a formality that precedes the real work and started treating it as the real work — the place where the actual thinking about the campaign happens, before a single record gets pulled. The vendor's job, at that point, is mostly execution against a well-specified target. That's true whether you're working with a boutique specialty-data shop or a firm like NPLUS Global that spans a wider range of healthcare and industrial verticals — no vendor, however good their underlying data, can out-execute a brief that never defined its target audience clearly.

The uncomfortable part of this shift is that it moves accountability. A vague brief lets everyone downstream blame the data. A precise one puts the pressure back on the requester to actually know who they're trying to reach and why — before they ask someone else to go find them.