Starting Healthcare Commercial Discovery With Workflow Questions

When a healthcare operations leader sits down with an account executive, the first thing they usually want is an answer, will this tool fix what is broken. Healthcare commercial discovery works better when the account executive resists that pull and asks about the work itself first, the trigger, the handoffs, the systems, the governance rules, and the evidence the buyer will use to judge success. A demo before that discovery leaves compliance, privacy, and operational questions unanswered. Worse, it puts the account executive in the position of guessing at a fix instead of understanding a process.

Why This Conversation Goes Wrong

Buyers in healthcare operations are busy and often frustrated. They open with a symptom, staff missed a deadline, a queue backed up, patients waited too long, and they want confirmation that your product removes that symptom. An account executive who answers directly, even with a hedge like it depends, has already made a claim about a process they do not understand. That claim gets tested later by an implementation team, a compliance officer, or a frontline supervisor who knows the real workflow. The gap between the claim and the reality becomes the reason the deal stalls.

The deeper problem is that healthcare workflows involve people and systems the account executive cannot see from a demo. A single intake task might pass through scheduling, insurance verification, a clinical reviewer, and a records team before it resolves. Each handoff carries its own rules, its own software, and often its own approval chain tied to privacy or clinical governance. Skip past that complexity and you end up selling a feature instead of solving a problem. The buyer notices the difference even if they do not say so.

How to Prepare Before the Call

Good workflow questions do not appear in the moment. They come from preparation. Before the call, write down what you already know about the buyer's role, their department, and the trigger that likely brought them to the table. If the operations leader mentioned intake delays in an email, treat that as a starting point, not an answer. Prepare three or four open questions that ask about steps, not opinions. Ask what starts the task, who touches it next, where it tends to sit unmoved, and who has to approve a change before it becomes official policy.

Also prepare for governance. Healthcare deals almost always involve a privacy review, a security assessment, or a clinical sign off that has nothing to do with your product's features. Ask early who owns that review and how long it usually takes. This is not a stall tactic. It is real information that shapes the timeline and the deal size. Skip it in discovery and you will hit it in procurement, later and more expensive to unwind. Reviewing other Healthcare practice conversations before the call can help you recognize which workflow questions open up the most useful answers.

What to Say When the Buyer Wants a Quick Answer

Picture an operations leader named Priya opening a call with an account executive named Marcus. Priya says, "We need to know whether your platform will fix our intake delays." Marcus does not answer yes or no. He says, "Before I say anything about fit, walk me through what happens the moment a new intake request comes in. Where does it start, and where does it usually sit waiting?"

Priya explains that a front desk staff member logs the request, then it moves through insurance verification and a clinical reviewer before it reaches scheduling. Marcus follows with a second question. "Of those steps, which one causes the most rework when something goes wrong, and who has to sign off before you could change that process?" Priya says the clinical reviewer step causes the most delay because requests often bounce back for missing information, and any process change would need approval from the clinical director and a review from compliance.

Marcus has not claimed his product fixes anything. He has a map of the workflow, the failure point, and the people who control change. He asks a third question that narrows toward evidence. "What would the clinical director need to see to agree this is worth changing, fewer bounce backs, a faster average time to scheduling, or something else?" That question hands the definition of success back to the buyer instead of asserting one.

Mistakes That Undermine Discovery

The most common mistake is asking a workflow question and then interrupting the answer with a feature pitch. If Marcus hears about the clinical reviewer bottleneck and immediately says our platform flags missing information automatically, he skips past everything else he needed to learn, including who owns that step and what evidence would count as success. Let the answer finish. Take the note. Ask the next question.

A second mistake is treating governance as an afterthought late in the deal. Asking about privacy review or clinical sign off only after a demo signals that you see it as a formality rather than part of how the buyer actually decides. Bring it up early, alongside the workflow questions, so it reads as normal diligence instead of a late surprise.

A third mistake is accepting a vague answer instead of asking for a concrete one. If a buyer says a few teams touch it, ask which teams, in what order, and how a task moves from one to the next. Vague answers produce vague deal notes, and vague deal notes produce a proposal that misses the actual point of friction. The same discipline shows up outside sales calls. Helping a Patient Manage Too Many Appointments shows how asking for specifics instead of accepting a general complaint changes the outcome of a healthcare conversation.

A fourth mistake is answering a question outside your expertise, such as a specific coverage detail, just to keep the conversation moving. The account executive's job in discovery is to map the workflow, not resolve every question the buyer raises. Handing Off a Benefits Question Without Giving Coverage Advice works the same way, hand off what is not yours to answer instead of guessing.

How to Practice and Score This Skill

This is a rehearsal skill before it is a live skill, so practice it before the real call. Have a manager or a peer play an impatient operations leader who opens with a direct question about fit and resists the pullback toward workflow. The account executive's job is to ask three workflow questions before mentioning a single feature. Score the attempt on three things.

Did the account executive avoid making any claim about the product until the workflow was clear. Could an observer draw the actual process, the steps, the handoffs, and the decision points, just from listening to the answers. Did the account executive surface who owns governance and what evidence the buyer will use to judge success. If the observer cannot draw the process from the answers, the questions were too general, and the next attempt should push for a specific handoff, a specific decision, or a specific source of delay.

DealSpeak sessions built around this scenario let an account executive run the same opening several times against an AI counterpart that reacts differently each run, impatient once, skeptical of the questions the next time. That repetition turns a good discovery instinct into a habit that holds up when the buyer is short on time and the deal is real.

The instinct to answer a buyer's question with a feature is strong, especially under time pressure, but healthcare deals reward the account executive who understands the workflow first. Ask about the trigger, the handoffs, and the approval chain before you say anything about fit, and let the buyer's own answers define what a good outcome looks like.