The demo went great. The physician on the call lit up, asked smart questions, and said the words every founder wants to hear: “We need this.” You sent the follow-up, got a warm reply, maybe even talked about a pilot. And then the replies got slower, the meetings got pushed, and somewhere around week eight you realized the deal wasn’t moving at all.
If that sounds familiar, you’re not alone, and it usually isn’t your product. Health tech startups don’t stall because the buyer said no. They stall because they only ever talked to one buyer.
Healthcare doesn’t have a buyer. It has a buying committee.
Most of my career has been in healthcare, and a lot of it was spent writing for the people who actually sit in that room: CMIOs, CIOs, CFOs, quality leaders, and the clinicians who use the tools every day. What I learned early is that each of them is weighing a different kind of risk, and each one can quietly stop a deal.
- The clinical champion wants to know if it makes care better and their day easier.
- Clinical informatics and IT want to know if it integrates, if it’s secure, and who supports it when something breaks.
- Finance wants to know what it costs, what it saves, and which budget it comes out of.
- Quality and compliance want to know if it holds up to regulation and whether it moves the measures they report on.
- Operations and end users want to know how much training it takes and what it does to a workflow that’s already stretched.
- Procurement wants a clean contract and a vendor that won’t become a headache.
The person who loved your demo is usually just one of those seats. They can open the door. They almost never sign the check alone.
Five places health tech deals get stuck
1. Your champion can’t carry the story
Your champion is excited, but now they have to sell you internally, in meetings you’ll never be in, to people who weren’t on the demo. If all they have is a slide deck built for clinicians, they’re walking into a finance conversation empty-handed.
2. The pilot never ends
Pilots are where a lot of good products go to wait. Without agreed success measures, a timeline, and a named decision maker, a pilot can run indefinitely while everyone stays polite and nobody commits. A pilot without an exit isn’t a step toward a contract. It’s a holding pattern.
3. IT and security show up late
Integration and security questions are going to come. When they arrive in month four instead of week one, they reset the clock. Every surprise in a security review reads as risk, and risk is the one thing every person on that committee is paid to avoid.
4. Your ROI talks to the wrong budget
“Saves clinicians time” is a real benefit, but it doesn’t always show up on anyone’s budget. If the savings land in one department and the cost lands in another, finance will hesitate. Your value story has to connect to a number someone in the room is actually accountable for.
5. One message for a room full of different people
This is the one underneath all the others. The same pitch goes to the physician, the CIO, and the CFO, and it only really lands with one of them. It’s the healthcare version of a problem I see everywhere: strong positioning, one-size-fits-all messaging. (If that distinction is fuzzy, start with positioning vs. messaging explained.)
How to get a stalled deal moving
Map the committee before the first demo
Ask your champion early who else needs to be involved and what each of them will worry about. You’re not being pushy. You’re making their job easier.
Build a message for each seat
Keep the positioning the same and translate it for every person in the room. The clinician hears about care and workflow. IT hears about integration, security, and support. Finance hears about cost, savings, and timing. Quality hears about outcomes and compliance.
Design pilots with an exit
Before a pilot starts, agree in writing on what success looks like, how long it runs, and who makes the call at the end. If nobody will commit to that, you’ve learned something important about the deal.
Arm your champion
Give them something they can forward without you in the room: a short summary written for leadership, answers to the security questions before they’re asked, and a simple business case in plain language.
Bring proof that matches the risk
Healthcare buyers are skeptical for good reason. Case studies, references, and outcome data from organizations like theirs do more to move a committee than any feature list. If you don’t have that proof yet, a well-designed pilot is how you earn it.
A quick gut check
- Can you name every role that has to say yes before you get a signature?
- Do you have a version of your story written for each of them?
- Do your pilots have success measures, an end date, and a decision owner?
- Could your champion explain your business case to finance without you there?
- Are you answering IT and security questions before they become objections?
If a few of those made you wince, you’re in good company. Most stalled deals I see aren’t a product problem. They’re a buyer problem, and that’s fixable.
Healthcare rarely says no fast. More often it says “not yet,” and keeps saying it. Give every person in the room their own reason to say yes, and “not yet” starts turning into a signature.
Keep reading: How I helped Greenway Health restore customer trust and drive product adoption