Guide · Founder GTM

Selling to the buying committee.

The demo went great. The physician loves it. And the deal still dies — because healthcare software is bought by a committee, and you only pitched one seat.

Healthcare software is bought by a committee of 6–10 people — clinicians, administrators, IT, compliance, and finance — not by the user who loves your demo. Deals close when every member gets an answer to their specific risk, and stall when even one silent veto goes unaddressed.

Who is actually on the committee.

Healthcare software isn't bought by the person who loves your demo. It's bought by a committee of 6–10 people, most of whom you'll never meet — and each one can kill the deal for a different reason:

RoleWhat they fearWhat convinces them
Clinical championLooking foolish for backing youPeer proof — named clinics, named outcomes
Practice admin / opsWorkflow disruption, staff revoltAn implementation plan measured in days, not quarters
IT / securityIntegration debt, a breach with their name on itEMR integration specifics, SOC 2, a clean security packet
ComplianceHIPAA exposureBAA ready to sign, data-flow diagram on request
CFO / ownerPaying for software that doesn't move a numberROI math in their units: chairs filled, calls answered, hours saved

Why one excited clinician isn't a deal.

The most expensive illusion in healthtech sales: the demo went great, the physician said "we need this," and the deal feels done. It isn't. Behind that one champion sit five silent vetoes — people who weren't in the demo, owe you nothing, and default to no:

  • The admin who's survived three failed software rollouts and isn't volunteering for a fourth.
  • The IT lead who hasn't seen your security documentation and assumes the worst.
  • The compliance officer who hears "AI" and reaches for the brakes.
  • The CFO who's heard "it pays for itself" from every vendor since 2015.
  • The partner-physician who wasn't consulted and vetoes on principle.

A deal is won when every veto has been answered — before it's cast. Your champion can't do that alone; your job is to arm them.

Arm the champion, don't just pitch them.

Your champion will repeat your pitch to the committee badly — unless you hand them the exact artifacts each member needs:

  • For ops: a one-page implementation timeline with staff hours required, honestly stated.
  • For IT: the security packet — SOC 2 status, integration architecture, data residency — sent before they ask.
  • For compliance: the BAA draft and a plain-English data-flow summary.
  • For the CFO: one page of math in their unit economics, with conservative assumptions they can audit.
  • For everyone: named proof. "A 12-clinic rollout in your specialty" beats any feature list.

The procurement freeze.

HIPAA review, SOC 2 questionnaires, security audits, legal redlines — in healthcare these aren't exceptions, they're the path. A "closed" deal that hits procurement unprepared freezes for months. The fix is sequencing: have the packet ready before the first demo, answer the questionnaire before it's sent, and treat procurement as a stakeholder you're selling to — not an obstacle that appears at the end.

The CFO's math comes last — and decides everything.

Soft benefits don't survive a budget meeting. Before the committee votes, the CFO needs one number: what does this return, in our units, by when? Build it conservatively — calls answered, no-shows recovered, staff hours saved, revenue per chair — and let them stress-test the assumptions. A defensible small number beats an impressive fragile one. This is the difference between a pilot that converts and a pilot that gets praised (we wrote a separate playbook on that).

Committee-ready in 30 days.

  1. Map the committee for your exact buyer: list the 6–10 roles, name the likely veto of each.
  2. Build the security packet once — SOC 2 status, integration specifics, BAA template — so it ships in minutes, not weeks.
  3. Write the per-role one-pagers: ops timeline, CFO math, compliance summary. Three pages total, not a deck.
  4. Collect named proof in the buyer's specialty — even one referenceable rollout changes the conversation.
  5. Rehearse the champion. They'll carry your case into rooms you'll never enter — make sure they can answer the five vetoes without you.

This is the motion behind the numbers on our Dripify case — 160+ enterprise accounts and a 280-seat deal, all committee sales — and behind Voxira's 12 signed clinics before the product was even finished.

Keep reading

More from the playbook.

Common questions.

Who is on a healthcare buying committee?

Typically 6–10 people: the clinical champion, the day-to-day user, IT and security, compliance (HIPAA/SOC 2), procurement, and the CFO or economic buyer. Each carries a different risk, and the deal stalls when even one silent veto goes unaddressed.

Why doesn't one excited clinician close the deal?

A champion can recommend but rarely sign. Deals close when every committee member gets an answer to their specific risk — a single unaddressed veto from security, procurement, or finance freezes a 'closed' deal for months.

How do you get through healthcare procurement faster?

Prepare for it before you're in it. Have security documentation, references, and the ROI case ready so a 'closed' deal doesn't hit procurement cold, and arm your champion with the exact materials each gatekeeper needs.

What does the CFO need to approve a healthcare purchase?

A credible ROI case they can defend — the cost of the problem today versus the price, in the CFO's own numbers. That math comes last and decides everything, which is why the pilot's real job is to produce the CFO's slide.