Asking About Adoption Before Proposing a Healthcare Rollout

Most healthcare account executives spend their prep time on the demo, the pricing model, and the implementation timeline, and they walk into the room ready to sell a plan. What they skip is the one question that actually predicts whether the rollout works, who is going to use this every day, and what happened the last time this organization tried to change how people work. Skip that question and you build a proposal on top of a workflow you never actually saw. Ask it first, and you change the whole shape of the conversation, because now the buyer is talking about their people instead of your product.

Why This Conversation Goes Wrong

Account executives are trained to move toward a decision. The moment a buyer describes a problem, the instinct is to connect it to a feature and start building momentum toward a proposal. In healthcare, that instinct backfires. Clinical staff have already lived through software rollouts that arrived with a training session, a laminated cheat sheet, and no plan for what happens six months later when half the staff has turned over. Ask an operations leader about adoption too late, and you get polite answers because they already assume the pitch is coming no matter what they say. Ask too early, before you have earned any credibility, and the question sounds like a script. The conversation goes wrong when the AE treats adoption as a topic to cover on the way to a proposal instead of the thing that decides whether the proposal is worth writing. It also goes wrong when the AE accepts the first surface answer, something like everyone is excited to get started, without asking who actually trains new staff or who notices when a process breaks down.

How To Prepare Before The Meeting

Before you ask anyone about adoption, learn what you can about how this organization actually runs day to day. Read the notes from every previous call and look for mentions of past software, past vendors, or past attempts at process change. If a reference call is available, ask the reference how the last major rollout went and who ended up owning the process once the vendor left the room. Pull together a short list of names, department heads, clinic managers, and shift supervisors, who need a place in the evaluation even if they never speak on a sales call. Healthcare organizations often run each clinic or department a little differently, so ask early whether the buyer expects one standard process across the organization or several local variations. Understanding the current workflow in concrete terms, not general impressions, matters here too. The guide on Finding Useful Measures of the Current Workflow in Healthcare Discovery walks through how to get specific numbers instead of vague descriptions, and the same discovery mindset applies to data handling questions, which Discovering Data Retention Questions Before a Healthcare Proposal covers in more depth. Both belong in the same early conversation as adoption, before any proposal takes shape.

What To Say During The Discovery Call

Open with a question about history, not about the future you are proposing. Ask what happened the last time this organization tried to change a clinical workflow, and let the answer sit before you respond with a solution.

Helen says, "Our staff has sat through too many launches that faded out right after kickoff. People get trained, then three months later nobody remembers the new steps."

Drew says, "What made that hard to sustain? I want to understand who trained the staff the first time and who was the first person to notice when things started slipping."

Helen says, "Every clinic ended up doing it their own way. Corporate rolled out one process, and within a year each location had drifted into something different."

Drew says, "That tells me the evaluation should include clinic leaders directly, not just corporate operations. Before we talk about any rollout plan, I would like to map how each clinic handles this process today, and hear from someone who manages daily operations at the clinic level."

Helen says, "That would actually help. Nobody outside corporate usually gets asked that."

Drew says, "Then let us set up time with two or three clinic managers before we go further. I would rather build a plan around what they tell us than guess."

This exchange works because Drew never promises a smoother rollout or a shorter training curve. Drew asks about ownership, about who noticed the drift, and about local variation, then proposes a concrete next step, talking to the people who do the work.

Mistakes To Avoid

Several habits turn this conversation into a missed opportunity.

1. Promising an adoption rate or a reduction in workload before you have seen the current process. You do not know enough yet to make that claim, and a specific number you cannot back up will come back to hurt you during the renewal conversation.
2. Asking about adoption once and treating it as answered. Adoption is not a single question, it is a thread that should run through every call, because new stakeholders surface new versions of the same problem.
3. Bringing an implementation specialist into the room too early. Wait until the discussion reaches details that need their expertise, otherwise the buyer feels like they are being sold to by two people instead of one.
4. Accepting a vague answer like our team is ready for change without asking who specifically will train new hires, who covers for staff turnover, and what happens when a clinic manager leaves.
5. Skipping the people who will use the product daily and talking only to the executive sponsor. The sponsor signs the contract, but the frontline staff decide whether the product gets used.

How To Practice And Score This Conversation

Reading about this conversation is not the same as running it under pressure, especially when a buyer pushes back with a story about a rollout that failed. Pick a past evaluation from your own pipeline and write down every question you actually asked about adoption. Most AEs find the list is shorter than they expected. Add three new questions before your next meeting, one about who trains new staff, one about who owns the process after the vendor leaves, and one about how much variation exists across locations or departments.

A manager can score this by listening for whether the AE lets the buyer finish describing the failed rollout before responding, whether the AE asks about ownership and not just satisfaction, and whether the AE resists the urge to promise an outcome. DealSpeak gives you a way to rehearse this exact exchange against an AI counterpart that pushes back the way a skeptical operations leader would, and you get scored on whether you asked about people and process before you pitched a plan. If you want more scenarios built specifically around healthcare buyers, the Healthcare practice conversations hub has more of them.

Bringing It Together

Adoption questions are not a formality before the real pitch, they are the real discovery. Ask about the last rollout, ask who owns the process, and bring in the people who will actually use the product before you propose anything. Do that consistently, and your proposals will start matching what the organization can actually sustain.