Most demo advice is about polish: a tighter script, cleaner slides, a smoother delivery. Connor Billing, a go-to-market leader who has spent more than a decade running solution engineering for healthcare SaaS companies, says polish is the wrong target. The demo that closes is the one built from discovery, not the one that shows the most product. In a regulated market, the decisive advantage is not performance. It is proving that you understand the buyer's world well enough to deserve their trust.
In this article
- Silence is the hardest signal in a demo
- A feature tour and a demo are not the same thing
- The Discovery-to-Demo Translation Loop
- In healthcare, trust starts before the product opens
- The honest way to sell AI into healthcare
- Discovery and demo are where regulated deals stall
- Urgency can be built. Lost trust is much harder to recover
- Curiosity beats a healthcare resume
- FAQ
Silence is the hardest signal in a demo
Ask most sales leaders to describe a bad demo and they will picture an objection, a hostile question, or a buyer challenging the price. Connor's answer is the opposite. The moment he fears most is silence.
There's only one of two options: you either completely missed the mark and they're just bored, or they just really, really like it. That dead silence is always very tough.Connor Billing
On audio alone, both possibilities sound identical. No interruptions, no questions, no visible reaction. Earlier in Connor's career, demos happened in person or over audio-only calls, so the only choice was to keep going and find out later. On video, he keeps a second screen open to watch the room while he talks.
Nodding, leaning in, eyes tracking the screen, and people looking toward one another all add meaning that words alone cannot carry. When a prospect says, "this is interesting," Connor checks the line against the twenty minutes of behavior that came before it. The phrase can express genuine interest or a polite exit. The face often tells you which.
| Signal | What it can mean | What to do next |
|---|---|---|
| Dead silence | Deep attention or a complete miss | Pause and ask a specific relevance question instead of guessing |
| "This is interesting" | Real curiosity or social politeness | Ask what part maps to the buyer's current workflow |
| Cameras off | Low visibility, not automatically low interest | Use explicit checkpoints and invite questions by role |
| Engaged body language | The buyer is following the story | Confirm what they would want to explore next |
A feature tour and a demo are not the same thing
The most common mistake Connor sees is treating a demo like a checklist: ten features, ten screens, done. In simple self-serve software, that may survive. In enterprise healthcare, it creates product fatigue because the buyer has to do the translation work alone.
The feature, they can go on to someone's website and get a feature tour of the platform. A demo, you're talking in their language, in their world, how they would use the product.Connor Billing
The distinction is not cosmetic. A feature tour answers, "what can the product do?" A real demo answers, "what changes in my day if we buy it?" The second question requires discovery that goes below the label a buyer gives the problem.
Connor asks prospects to walk him through a day in their life. How is the work handled now? Which step creates the delay? What happens before and after it? Who touches the information? Where does risk enter? That sequence tells the solution engineer what to automate, what to leave alone, and which part of the product is actually worth showing.
Persona changes the story too. In a nine to twelve month healthcare cycle, Connor may run three, four, or five versions of the same product for different stakeholders. An IT buyer may want architecture and controls. A business leader wants to know whether the system produces the required outcome. Giving both audiences the same demo is not consistency. It is a refusal to translate.
The Discovery-to-Demo Translation Loop
The most useful operating idea in Connor's episode is a loop that makes every screen earn its place.
The Discovery-to-Demo Translation Loop
Observe the current workflow. Isolate the costly or risky friction. Replay the problem in the buyer's own language. Show only the relevant slice of the product. Confirm that the buyer can explain the value and next step in their own words.
Consider a hospital team that says prior authorization takes too long. A feature-tour response is to show every automation capability. A translation-loop response keeps digging: which authorization types, where the work queues, how staff know something is missing, what the delay does to care or revenue, and who owns an exception.
The demo then follows that exact path. Show the intake, the missing-information signal, the exception workflow, and the handoff. Stop there. If the buyer can explain how that sequence changes the current process, the demo has done its job. If they cannot, another feature will not rescue it.
In healthcare, trust starts before the product opens
A hospital, a diagnostic lab, a skilled nursing facility, and a pharmaceutical manufacturer all sit under the healthcare umbrella. Connor is direct that they are different worlds. Knowing the industry's broad vocabulary is not enough. A credible seller understands the prospect's corner of it, the acronyms, the policy pressure, and the operational realities that matter to that buyer.
The other half of trust is restraint. Connor sees the solution engineer as a transparent product expert, including when the honest answer is that the platform cannot do something. That answer may feel dangerous in the moment. In a regulated sale, it is often the clearest evidence that the seller will not hide a limitation after the contract.
Buyer behavior has made that human validation role more important, not less. Gartner reported in 2026 that 69% of B2B buyers preferred to validate AI-generated insights with a sales representative. Buyers may research independently and still need a credible person when the consequence of a wrong answer rises.
The honest way to sell AI into healthcare
Healthcare buyers are wary of AI for good reason: sensitive data, regulatory scrutiny, and a long history of vendors overpromising. Connor's advice runs against the usual instinct to lead with certainty. Be more honest than feels comfortable.
AI is amazing and AI is going to fix everything and AI is always correct. That's the number one mistake you can make when talking about AI.Connor Billing
He leads with what keeps the model accountable after the sale: monitoring results, retraining when the team sees drift or hallucinations, and maintaining a feedback loop where clients can flag what went wrong. AI may outperform an average human at a bounded task. It will not be 100% accurate, and no regulated buyer should be told otherwise.
Context matters just as much as model capability. SalesTable sees teams ask for a one-hour agent build and a one-month return without stopping to ask whether the AI has the right data, definitions, workflow, and historical examples. The output cannot become more trustworthy than the context it receives.
Salesforce's 2026 State of Sales research found that 67% of sellers say customers require extensive education, while 57% say customers take longer to decide. Ongoing education is not an implementation extra. It is part of earning a regulated buyer's confidence before and after the contract.
Discovery and demo are where regulated deals stall
Suresh shared a pattern from SalesTable's work with regulated-industry teams: roughly 50 to 60% of deals stall after the first discovery call, and close to half of the remainder stall after the demo. The figures are approximate, not a controlled benchmark. They still point to a useful question: did the seller understand the problem, then translate it into something the buyer recognized?
Where regulated deals stall: discovery to demo
An illustrative funnel using approximate figures Suresh cites from SalesTable's client work
The second step assumes 50 to 60% stall after discovery. The third assumes roughly half of the remainder stall after demo. Both are approximate episode figures.
Asked which represents the bigger deal risk, a weak champion or an unclear problem, Connor chose the unclear problem. A champion can be supported. A problem no one has defined cannot be solved by relationship management or a better presentation.
Urgency can be built. Lost trust is much harder to recover
In the episode's rapid-fire section, Connor is asked what kills more deals: no urgency or no trust. His answer is trust. A serious enterprise buyer may still take 18 months, but a seller can sharpen urgency with a stronger value case, a clearer cost of delay, or better commercial structure.
It's a lot easier to show them why there should be more urgency than there is to try to build trust that you lost. As soon as you've lost trust, it's very, very tough to get that back.Connor Billing
Urgency and trust are not equally recoverable
Connor's qualitative risk comparison, shown as an illustrative scale
Illustrative. Bar length represents the relative recovery difficulty Connor describes, not measured probability.
That asymmetry makes every early interaction expensive to waste. Industry fluency, a discovery process that respects the buyer's reality, and honesty about product limitations all deposit trust. A generic pitch, an inflated AI claim, or a demo that ignores discovery spends it.
Curiosity beats a healthcare resume
Connor places the solution engineer at the intersection of marketing, product, and sales. Someone who knows only the product narrates features. Someone curious about the buyer connects the product to business value, operational reality, and the return that matters to that persona.
That is also why companies tend to hire solution engineering at a particular stage. Before product-market fit, there may not be enough product complexity or repeated demand to justify customization. The signal is when demos need to become configurable and persona-specific rather than one-size-fits-all.
Asked what it takes for a strong SaaS seller to succeed in healthcare, life sciences, insurance, or another regulated industry, Connor names curiosity, not a perfect resume. The rep willing to read the white papers, attend the conference sessions, learn the acronyms, and ask how work actually happens will outperform the person who only knows the product cold.
Curiosity is especially valuable when a new stakeholder arrives late and threatens to reset the deal. Connor treats that arrival as fresh discovery. He assumes context did not transfer internally. If the new person needs a new demo or value case, he builds it. The alternative is expecting the stakeholder to support a decision they were never helped to understand.
Key takeaways
- Silence is ambiguous. Use visual and explicit relevance checks instead of guessing.
- A feature tour explains the product. A demo translates discovery into the buyer's workflow.
- Show only the slice of the product that resolves the friction you actually diagnosed.
- In regulated healthcare, fluency and honesty build trust before the screen share begins.
- Present AI as monitored, imperfect, and accountable, never as a silver bullet.
- Urgency has commercial levers. Lost trust has very few.
- Hire and develop for curiosity, especially when the vertical is complex.
FAQ
Is a polished demo or a personalized demo better?
Personalized. A polished presentation can still fail if it does not connect to the buyer's workflow, language, and priorities. A strong demo uses discovery to decide what to show and what to leave out.
What kills more B2B deals: no urgency or no trust?
Connor argues that lost trust is more dangerous. Urgency can be built through a clearer cost of delay, stronger value framing, or commercial structure. Trust is extremely difficult to restore once the buyer believes the seller was careless or misleading.
When should a company hire a solution engineer?
Hire when the product and ideal customer profile are mature enough that demos need to become configurable and persona-specific. Before that point, there may not be enough repeatable complexity to justify the role.
How should sellers present AI in regulated healthcare?
Be explicit about limitations, monitoring, data quality, retraining, feedback, and the human accountability that remains after the sale. Do not promise perfect accuracy or position the system as a substitute for judgment.
Connor's full conversation with Suresh covers the realities of long healthcare buying cycles, the solution engineer's role across product, marketing, and sales, and what to do when a new stakeholder appears late in the deal. Listen to the complete episode of Revenue Under Pressure and subscribe for more field-tested lessons from regulated revenue teams.