Selling Into Healthcare: What a CMIO Actually Cares About (and It Isn't Your Roadmap)

Healthcare is not a hard market, it is a slow one with more veto points

Most reps who fail in healthcare do not fail because the product was wrong. They fail because they ran a normal SaaS motion — champion, demo, business case, close — at an organization that has five people who can say no and only one who can say yes, and the one who can say yes cannot say yes alone.

I have sold inside AWS and Dell, and I have built and exited four businesses. Nowhere else have I seen a buying process where a single unanswered question in a security review can freeze a deal for a quarter while everyone involved still tells you they love it. Healthcare does that routinely. The deal does not die loudly. It just stops moving, and your forecast rots from the inside.

The fix is not more persistence. It is mapping the committee properly, understanding what each person can kill, and changing what you talk about. Your roadmap is not what a CMIO cares about. Neither is your funding round, your logo wall, or your AI. What they care about is whether this thing makes a clinician's day shorter or longer, and whether it will embarrass them in front of the medical staff if it goes wrong.

The committee, and what each seat can kill

Write these down as separate lines in your CRM. Not "stakeholders." Separate lines, each with a name, and each with the specific thing that person can stop.

The CMIO

The Chief Medical Information Officer is usually a practicing or formerly practicing physician who owns the intersection of clinical care and technology. This is the person who has to stand in front of the medical executive committee and defend the decision. They are not a technologist who happens to have an MD. They are a clinician who got tired of bad software and took the job.

What the CMIO can kill: clinical credibility. If they decide your product creates work for physicians, adds clicks, or produces alerts that will be ignored, the deal is over and no amount of ROI modeling revives it. They have seen alert fatigue destroy a rollout. They have watched a vendor promise a two-week integration that took nine months. They are pattern-matching you against every vendor who has lied to them.

What wins with a CMIO: specificity about workflow. Not "we integrate with your EHR" but "this fires when the order is placed, appears in the same sidebar they already use, and requires no additional login." They will believe you when you describe their day back to them accurately.

The VP of Clinical Operations

This person owns throughput. Length of stay, discharge timing, staffing ratios, room turnover, clinic capacity. They think in flow, not features.

What they can kill: operational feasibility. If your product requires a nurse to do something extra during a shift that is already fully consumed, Clinical Ops will tell you it cannot be staffed. That is not a negotiation. There is no headroom to negotiate with.

What wins: showing where the work goes. Every product moves work. Be honest about who absorbs it. If the answer is "the unit clerk does one extra step and the nurse does three fewer," say that out loud. Clinical Ops respects a vendor who admits there is a cost, because they have never met one who did.

The CNIO

The Chief Nursing Informatics Officer, or whoever holds nursing informatics if the title does not exist. Reps skip this person constantly and it is the most expensive omission in healthcare selling. Nursing is the largest clinical workforce in the building. If the product touches documentation, handoff, med administration, or anything a nurse does at the bedside, the CNIO's opinion is decisive even when they are not on your call list.

What they can kill: adoption. And they can kill it after you have signed, which is worse, because then you have a reference that hates you.

The CISO and the security review

Assume you will face a security questionnaire, a Business Associate Agreement, a penetration test summary request, questions about where protected health information is stored and who at your company can see it, and a conversation about what happens during a downtime event.

What security can kill: everything, at any stage, silently. A security review is the single most common place I see healthcare deals stall past the quarter. Not because the answer is no, but because the review sits in a queue and nobody on your side knows how to move it.

The move here is preemptive. Ask in discovery: who runs your third-party security review, how long is the current queue, and what do you need from me to get in it? Then send the packet before they ask. SOC 2 report, HITRUST status if you have it, data flow diagram, subprocessor list, your standard BAA. If you do not have those, know it now, because the honest answer to "where are you on SOC 2" is a conversation you can survive and a surprise is not.

Procurement, supply chain, and value analysis

Many health systems route new clinical technology through a value analysis committee or new product committee that meets on a fixed calendar. Monthly. Sometimes less. If you miss the submission window, you have missed a month of your sales cycle and there is no expediting it.

What they can kill: timing and price. Procurement rarely kills a deal outright. They kill your quarter and your margin. They will also ask whether you are on an existing GPO agreement or an approved vendor list, and whether an incumbent already does part of what you do.

Ask early and directly: what committee does this have to go through, when does it meet, and what is the submission deadline? Almost every rep I have watched asks this in month four. It belongs in month one.

IT, integration, and the analyst who actually does the work

Somewhere there is an integration analyst with a backlog. Your project joins that backlog. The CMIO can prioritize it, but only against other things the CMIO also wants. This is why "we have executive sponsorship" means less in healthcare than anywhere else. Executive sponsorship gets you into the queue. It does not empty the queue.

Clinician time is the only currency

Here is the reframe that changes healthcare selling more than any other single thing.

In most B2B sales, the currency is money. You build a business case, you show payback, you win. In healthcare, the currency is clinician time, and money is downstream of it. A physician minute is the scarcest resource in the building. Everything else — burnout, turnover, throughput, patient experience, coding accuracy, the CFO's numbers — flows out of whether clinicians have enough time to do the work in front of them.

So the claim that lands is not "reduces cost per encounter." It is "gives this specific clinician this many minutes back per shift, in this specific part of their day." A CMIO can feel that claim. They can test it against their own experience. They will immediately picture the physician who complains loudest in their organization and ask whether it would help that person.

Two rules about making that claim.

First, name the exact activity. Minutes saved on chart prep before clinic is a different sale than minutes saved on discharge documentation, which is a different sale again from minutes saved chasing a specialist for a consult. Vague time savings sound like every other vendor. Specific ones sound like you have watched the workflow.

Second, never present a time-savings figure you cannot source. If the number came from another customer, say which kind of organization it came from and under what conditions. If it came from your own modeling, call it modeling. A CMIO who catches you presenting a marketing number as a clinical finding will disqualify you on the spot, and they are right to. The strongest version of this claim in a first meeting is honest and slightly uncomfortable: "I do not know what it will save you. Here is what it saved a system that looked like yours, here is why yours might be different, and here is how I would measure it in a pilot." That sentence has closed more healthcare deals than any ROI deck I have seen.

Getting to the meeting where you can say it is its own skill, and I wrote a separate healthcare cold call script for getting a CMIO or VP of Clinical Operations to give you twenty minutes because the opener that works on a VP of Sales gets you hung up on by a physician.

The EHR question that ends demos

At some point, usually eleven minutes into your demo, someone will ask: "How does this work with Epic?"

They are not asking whether you integrate. They are asking six things at once:

Does this live inside the EHR or is it another window? Does it require a separate login? Who builds the interface, us or you? What does it cost us in analyst hours? Have you done this at a system running our version, and can I call them? And if the EHR upgrades, does your thing break?

If your answer is "yes, we have an API," you have lost the room. An API is not an integration. An API is homework you are assigning to a team with a two-year backlog.

The answer that keeps you alive is structural and honest. Say what the integration actually is — read-only feed, embedded launch inside the chart, bidirectional write-back, whatever it truly is. Say who does the work on each side and roughly what it costs them in effort. Say whether you have done it before at a comparable organization and offer the reference without being asked. And if the honest answer is "we have not integrated with your version yet," say that, then say what you would do instead for a first phase.

A separate window is not automatically fatal. Pretending a separate window is an integration is. Clinicians will tolerate a lot from a product that helps them. They will not tolerate being lied to about clicks.

Most of what makes a clinical demo work is deciding what not to show, which is why I broke out a full healthcare product demo script for running a clinical demo in front of a CMIO who has already killed two vendors. The short version: demo the clinician's day, not your product's modules.

Pilot design decides the deal

In healthcare, the pilot is not a step before the deal. The pilot is the deal. How you scope it determines whether you get an expansion or a polite thank-you eleven months later.

Bad pilots share a shape. They are free, they are open-ended, they have no defined success metric, they run on one unit with one enthusiastic champion, and they end with everyone agreeing it was interesting. Interesting does not get funded.

A pilot you can convert has five things settled in writing before it starts. What is being measured, and who owns the measurement — ideally their analytics team, not yours, because their number is credible internally and yours is not. What the threshold is: state plainly what result would mean go, and what result would mean no. A CMIO will trust you more, not less, for defining a failure condition. When it ends, on a specific date. Who signs if it works, named. And what the price is if it converts, agreed before the results are in, so nobody is negotiating against a number they just watched you produce.

That last one saves deals. If you leave pricing until after a successful pilot, you have handed procurement a hostage. Set the conversion price in the pilot agreement.

Also: pick the unit carefully. Not the most enthusiastic unit. The most representative one. A win on a hand-picked unit with a superstar nurse manager proves nothing to a skeptical committee, and skeptical committee members are the ones who write the memo.

All of this scoping comes out of discovery, not out of a proposal template. If you want the question set I would use, the 25-minute discovery playbook for CMIO and clinical ops calls is built around getting committee structure, integration reality, and pilot criteria on the table in the first conversation instead of the fourth.

Why healthcare deals die between verbal yes and signature

This is the part that breaks new healthcare reps. You get the verbal. The CMIO says we want to move forward. And then nothing happens for months.

Here is what is actually happening in that gap, in my experience of watching deals stall in large, committee-driven organizations.

The security review has not started, or it started and is queued behind three other vendors. Legal is redlining the BAA and your data ownership language, and their legal team touches it once every two weeks. Capital versus operating budget turned out to matter, and nobody checked which bucket this comes from. The value analysis committee meets next month and the submission packet is missing a form. Somebody discovered the incumbent contract has eight months left and an auto-renewal clause. The clinical champion went on service for six weeks and is unreachable. Or the CFO looked at it, did not see a line item it replaces, and asked what gets cut instead.

None of these are objections. You cannot handle them with a rebuttal. They are process, and process only moves when someone inside the organization pushes it.

So you do three things. First, in your last discovery pass, ask the question directly: "Walk me through everything that has to happen between you saying yes and this being signed." Write down every step and every name. Second, build the mutual timeline backwards from their go-live target, not forwards from your quarter, and put the committee dates and legal turnaround into it. Third, give your champion something to forward. Champions in health systems are busy clinicians. They will not build your business case. Write the one-page internal memo for them — problem, what was tested, what it measures, what it costs, what happens if we do nothing — and let them put their name on it.

And when it does come down to price at the end, do not discount out of relief that it finally moved. Healthcare procurement is professional, patient, and will ask twice. Holding your number after they have already chosen you is a specific skill, which is why I wrote a separate healthcare pricing negotiation script for that exact moment.

The sequence, compressed

Open with a clinician problem in clinician language, not a product pitch. Use discovery to map every seat on the committee and every process gate, including the security queue and the committee calendar. Demo the workflow, answer the EHR question honestly, and let the clinical detail do the persuading. Scope a pilot with a named owner, a defined threshold, an end date, and a pre-agreed conversion price. Then manage the gap between verbal and signature like it is a project plan, because it is.

The reps who do well in healthcare are not the smoothest talkers. They are the ones who sound like they have spent time on a unit and who never make a claim they cannot defend in front of a physician.

If I were ramping into a healthcare territory tomorrow, I would not read more about it. I would rehearse it — the cold open on a CMIO who has thirty seconds, the moment someone asks how it works with Epic, the pilot scoping conversation, the procurement squeeze at the end — until those moments stop feeling like ambushes. That is what we built DrillCall for: live practice against the buyer you are about to call, so the first time you hear the hard question is not on the real call.