Healthcare · Demo Call
Healthcare Product Demo Script: Running a Clinical Demo for a CMIO Who's Already Killed Two Vendors
The person on this demo has already sat through the pitch. They said yes to seeing it, which means they are not here to learn what your product does — they are here to find out where it breaks in their environment. If it's a CMIO, they were probably in clinic this morning and still have twelve results in their in-basket. If it's the Director of Clinical Informatics, they're already thinking about the SMART on FHIR build and whether it survives the next quarterly upgrade. If it's the VP of Clinical Operations, they want to know what changes at the front desk on Monday and who owns it after your implementation team leaves. This healthcare product demo script is built for that room.
The trap in healthcare demos is that the standard tour is genuinely impressive and completely irrelevant. You open the admin console, you show the analytics dashboard, you walk the note template library — and somewhere in minute six the CMIO stops asking questions. That silence is not agreement. It's a physician deciding you've never watched a real 15-minute visit. They've survived an EHR conversion, a telehealth scramble, a portal rollout and at least one scribe vendor that half the medical staff abandoned in month two. Their bar isn't "does it work." It's "will my ortho group still be using it in month four."
So run the demo as three or four moments in their week, in their vocabulary, with their specialties on screen. Answer every interruption in their environment. Say no out loud when the answer is no. And leave the call with the gap list, the governance date, and the next meeting already on the calendar — because in health systems, the deal doesn't die at the demo, it dies quietly in the eight weeks afterward while nobody owns the security review.
The demo call script
Say it in your own words. The structure is the part that matters.
- 1
Pre-call: confirm the stack in writing (send 3–4 days out)
Email, short, subject line "Two questions before Thursday so I don't waste your time": "Looking forward to Thursday. So I show you things that actually apply — three quick ones: 1. Which EHR, and which flavor? Epic community-connect or your own instance, Oracle Health, athena, eCW? And roughly how customized — do you have a lot of home-grown SmartPhrases and note templates people are attached to? 2. Who's joining? If your clinical informatics analyst or someone from security is on, I'll build in a 10-minute architecture segment rather than making them sit through the clinical workflow. 3. Which specialties are hurting worst on after-hours time? You mentioned primary care last time — is it just family and internal med, or is ortho and behavioral health in the same shape? If you can send me two or three of your site names and the specialties, I'll load them into the demo environment so you're not looking at 'Test Clinic 1.'" If they won't share anything: at minimum use real specialty vocabulary, real chief complaints, and a note structure that matches their EHR's layout. Never demo a health system with sample data called ACME.
- 2
Pre-call: decide the three screens, and what you will not show
Pick the three moments tied to what they named on the pitch call. Typical set for a documentation buyer: 1. A physician in the room — ambient capture running, phone or badge mic, doctor never touches a keyboard. 2. The note landing in the chart — in their EHR's layout, with the HPI and A/P structured the way their coders want it, and the E&M level supported. 3. Chart closure — provider reviews, edits two lines, signs. Encounter locked before they leave the building. What you do not show unless asked: the admin console, the analytics dashboard, the template library, the mobile app settings, anything on the roadmap. Every extra feature is one more thing their EHR governance committee has to evaluate and one more thing that can fail in a pilot. Have ready but closed: the architecture diagram, the completed security questionnaire, the BAA, and the specialty coverage list.
- 3
Opening: 60–90 seconds, set the contract
"Before I show you anything — last time you told me your primary care providers are averaging over 90 minutes of after-hours EHR time a day, your target is under 30, and you've got two family med docs you're genuinely worried about losing this year. And that chart closure inside 72 hours is where your coders start screaming. Is that still the picture? [let them correct it — they usually will] Anything shifted since we spoke? New budget cycle, someone new in the seat, anything? One request. I'd rather you stop me than sit through something that doesn't apply here. If you're thinking 'that won't survive contact with my ortho group' — say it while I'm on the screen, that's the useful part of this call. And last thing before I share: what's the one thing that, if this can't do it, we don't need to keep talking?" Whatever they answer, demo that first. If they say "it has to be inside Epic," your first screen is the launch from inside the chart, not the note quality.
- 4
Core loop 1 — the exam room
**Problem:** "So it's Tuesday, your 2:15 is a 68-year-old, diabetic, three problems on the list, and your doc has fourteen minutes because clinic's running behind." **Screen:** narrate as the physician, not the software. "She taps once on the badge mic. That's it — she doesn't touch the keyboard again. She's facing the patient. Foot exam, med reconciliation, the patient goes off on a tangent about her daughter for ninety seconds — watch what happens to that in the note." **Consequence:** "She walks out of the room and the draft's already there. What stops happening is the 8:40pm session at the kitchen table." **Check:** "Is that how your docs actually room a patient, or is your MA doing the intake and the vitals first? Because that changes where the capture starts."
- 5
Core loop 2 — the note in their chart, and the coding
**Problem:** "Here's where your last vendor probably lost the medical staff. The note comes back and it reads like a transcript." **Screen:** "This is what lands in the chart. HPI in her voice, not a wall of dictation. Assessment and plan problem-by-problem, matching how your Epic note template is laid out. And here — the diabetic foot exam and the neuropathy are documented specifically enough for the HCC to recapture, which your risk adjustment team is chasing every fall." **Consequence:** "For revenue cycle, the E&M level is supported by what's in the note rather than what the doc remembered to type at 9pm. Your denial rate on medical necessity is a documentation quality problem before it's a coding problem — your Director of Revenue Cycle Management will recognize that immediately." **Check:** "Show me where this note would fail your coders. Genuinely — what would they send back?"
- 6
Core loop 3 — chart closure and the in-basket
**Problem:** "You said 72-hour closure is where you're bleeding." **Screen:** "She's got the draft open between patients. Two edits — she changes 'moderate' to 'severe' and adds a line about the referral. Signs. Encounter locked, 4:50pm, before she's out of the building." **Consequence:** "Chart closure rate inside 24 hours goes up because closing is a two-minute review, not a forty-minute rebuild. And the in-basket doesn't compound, because she's not doing yesterday's notes on top of today's results." **Check:** "How do you currently measure closure — is that a report your informatics team pulls, or is it in your provider scorecard already?" Stop here. Three workflows completely beats twelve partially. If they want more, they'll ask.
- 7
Pressure line 1 — EHR integration, answered in their vocabulary
Raise it before they do: "Let me get ahead of the integration question, because it's the one that kills these deals. We launch as a SMART on FHIR app from inside the encounter — same SSO, no second login, no toggling to a browser window. We read the patient context and the problem list; we write the note back as a draft into your note activity. We do not write orders, we do not write to the medication list, and we do not touch billing. Ever. The note is a draft until a licensed provider signs it. We're live in production on [EHR] at [named systems]. If your clinical informatics analyst wants to see the actual build rather than take my word for it, I'd rather do that as a separate 30-minute technical call than argue it here. One thing I need from you: how customized is your instance, and what's your upgrade cadence? If you're heavily templated with home-grown SmartPhrases, I want to know that now, not in week six." Then flip it: "What's the last third-party tool that actually got adopted inside the chart here — and what made that one stick?"
- 8
Pressure line 2 — who owns it after you leave
"Ongoing ownership: this is not an IT job. It's roughly two hours a month and it's user management — adding providers, deactivating people who leave, changing which specialty template a provider is mapped to. Your practice administrator or a clinical informatics analyst does it. You do not need an FTE, which matters because I know you're carrying MA and front-desk vacancies you can't fill as it is. On our side: [name] runs implementation, [name] is your CSM afterward and stays with you — it's not a handoff to a queue. Providers who have a note problem contact us directly, not through your help desk, because otherwise your service desk eats the ticket volume and your CNIO ends up as tier one support. If your admin leaves, the handover is about a 45-minute session. I'll send you the runbook so you can judge that yourself."
- 9
Pressure line 3 — what happens when it breaks at 7:40am Monday
Do not lead with an uptime number. "Here's the failure mode, which is what you actually care about. If we're down, the capture keeps running locally on the device and queues — you don't lose the encounter audio, you lose the turnaround. The provider's fallback is exactly what they do today: they type the note. Nothing in your EHR breaks, because we're not in the write path for anything except a draft note. Support: a clinical-impacting issue is a phone number, 24/7, a human answers. Individual note quality complaints are email, next business day, and I'm not going to pretend otherwise. If you want, ask me about our last incident and I'll describe it — what happened, how long, what we told customers. I'd rather you hear it from me than from a reference call."
- 10
Pressure line 4 — three dates, not one
"I'll give you three dates rather than one, because 'go-live' means nothing. **Live** — first provider dictating into a real encounter: about [X] weeks after the BAA and the security review are done. Those run in parallel, not in sequence, and the security review is usually the long pole, not us. **Useful** — one pod stops staying late. That's typically inside the first two to three weeks of use for primary care. Specialty takes longer because the vocabulary tuning takes a few dozen encounters. **Fully rolled out** — all sites, all specialties: depends entirely on your governance calendar and how many providers you onboard per wave. What I need from you, in hours: a provider list with specialties and NPIs, a named informatics analyst for about six hours across the build, a 20-minute training session per provider — that's it, 20 minutes, not a half day — and a decision on how consent gets captured at rooming. That last one is the piece that stalls projects in week three because nobody assigned it. What's your EHR governance committee's next two meeting dates? I want to work backward from that, not forward from today."
- 11
Reading disengagement — say this the moment it goes quiet
Signals: short answers, flat "yeah, that makes sense," audible typing, camera off, a CMIO who was interrupting and suddenly isn't. Stop. Pick one: - "I've been talking a while. Is this the part you care about, or should I jump to something else?" - "Let me stop the tour. What's the thing you're worried about that I haven't touched? I'd guess it's either the specialty coverage or whether your docs will still be on it in month four." - "Do you want to drive? Tell me what to click and I'll do it." - "I think I'm showing you the wrong things. Can I stop, spend ten minutes understanding what actually matters here, and come back Thursday with a demo built for that?" What does not work: talking faster, adding a feature, "one more thing I want to show you."
- 12
Closing the demo
"Let me play back where we are, including the gaps. Three things landed: the note lands inside the chart with no second login, the A/P structure works for your coders, and closure happens before the provider leaves the building. Two open: whether our ortho note holds up — you're right to be skeptical, I'm sending you three de-identified ortho notes by Thursday and you can hand them to your sports medicine lead. And the consent language for a two-party state, which I'll send with how [named system] operationalized it at rooming. Where does this sit for you now — worth pursuing, or is there something that's already ruled it out? Who else needs to see it? I'd run a separate 20-minute version for your informatics analyst that's purely architecture and security, nothing clinical. And if your Director of Revenue Cycle Management is going to be a second sponsor — and in these deals they usually have to be — I'd show them the coding and HCC piece on its own. Can we get the governance submission date on the calendar right now? What's the packet they require?" Send within 24 hours: the gap list with answers, the four screens that mattered, the security questionnaire and BAA, the consent one-pager, and a one-sentence reference — not a logo slide.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Before I share my screen — last time you said your family medicine group is averaging over 90 minutes of after-hours EHR time a day and your board target is under 30. Still the picture, or has something moved?
Buyer
It's worse in internal medicine, honestly. But let me save you some time. I've seen four of these. They all demo beautifully on a straightforward URI visit. What's the one thing that if you can't do it, we're done?
Rep
That's my question for you, actually — I'll answer whatever you name first. But I'd guess it's either that it has to launch from inside Epic, or that the note has to hold up outside primary care.
Buyer
Both. And the second one is what killed the last vendor. Their family med notes were fine. Our ortho group got notes that read like a transcript of somebody describing a knee, and forty percent of them stopped using it inside six weeks. My medical staff doesn't forget that.
Rep
Then let's start in ortho, not primary care. This is a post-op knee follow-up — real structure, de-identified. I'm going to play thirty seconds of a visit and you tell me where the note fails. What I want you looking at is whether the range-of-motion findings and the return-to-activity plan are in the A/P or buried in the HPI, because that's usually where these fall apart.
Buyer
Hold on. Who's dictating there — is the surgeon wearing something? Because our surgeons will not carry a badge mic. They barely carry their phone into the room.
Rep
Phone in the coat pocket, screen down, one tap on the way in. No badge, no dedicated hardware. If your surgeons won't do the one tap, there's an auto-start tied to the appointment status when the encounter opens in the chart — but I'd tell you honestly, most sites turn that off in the first month because it captures hallway conversations. Which one would your ortho group tolerate?
Buyer
The tap, probably. Okay, that note's better than I expected. But this is all theoretical until it's in our instance. Our Epic build is heavily customized — we've got note templates that our informatics team has been layering SmartPhrases onto for eight years, and we're on a quarterly upgrade cadence. What breaks in November?
Rep
Straight answer: we launch as a SMART on FHIR app, so upgrades don't break the launch itself — that's the point of the standard. What can break is your template mapping, because if your team changes the note template structure, our output structure has to follow it. That's a configuration change on our side, about two hours, and we do it in your non-production environment before the upgrade hits prod. I'd want your informatics analyst on our upgrade notification list. Is that [name], or is that a different group?
Buyer
That's clinical informatics, yes. But none of this happens without our EHR governance committee, and they meet the third Tuesday. Last cycle they rejected two vendors. And before that, third-party risk has to clear you, which took our last clinical vendor about four months.
Rep
Then those two are the actual timeline, not my implementation. Two things. One — I want to start third-party risk now, in parallel with this conversation, not after. We sign BAAs as standard, here's SOC 2 Type II, and I've got a completed security questionnaire already submitted to two other systems on Epic that I can send today. Who owns third-party risk review here? Two — what did governance reject last cycle, and why? I'd rather know what the packet needs to contain than guess.
Buyer
One was rejected because the vendor presented alone and nobody clinical vouched for it. The other because it required a separate login. And I'll tell you the other thing that comes up in that room — our CFO. Operating margin is under two percent. There is no budget line for something that isn't billing or compliance.
Rep
Then I don't want to be a software line item. Two places it shows up on a P&L you already have. First, turnover — you said you've got two internists you're worried about. What does replacing one internist cost you all in, including the ramp on the panel? Second, throughput — if a provider gets 45 minutes back a day, that's one or two more visits. What's your contribution margin per encounter?
Buyer
Recruiting plus lost panel revenue on an internist is well into six figures, and we're running around twelve percent physician turnover. Contribution margin per visit I'd have to pull. But I know where you're going and I'll grant you the arithmetic — that's not my problem. My problem is month four. Every one of these things works in month one.
Rep
Then let me put that in writing rather than promise it. I'll propose a utilization threshold — active use by a named percentage of enrolled providers, measured weekly, reported to you not by you. If we're below it at day 60, we pull it out and you're not on the hook. I'd rather volunteer the exit than have your medical staff discover they're stuck with vendor number three.
Buyer
That's the first thing anyone's said today that I'd repeat to my CMO. Send me the ortho notes and the consent language — we're a two-party consent state and legal will be all over that.
Rep
Both by Thursday, plus how two comparable systems handled consent — most added one line to the existing consent-to-treat and captured it verbally at rooming, and the front desk barely noticed. Third Tuesday is the 18th. Can we hold 30 minutes with your informatics analyst the week before, so your submission packet has the architecture already reviewed and you're co-presenting instead of me presenting? I've got the 9th or the 11th open.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “If it doesn't live inside our EHR, clinicians won't touch it. Nobody's toggling to another window in a 15-minute visit.” | Agree immediately — anything that adds a login is a dead product. Then be specific enough that they can verify you: "We launch as a SMART on FHIR app from inside the encounter, same SSO, and we write the note back as a draft into your note activity. We're in production on [EHR] at [named systems]." Offer the technical call instead of arguing it with the CMIO: "I'd rather your clinical informatics analyst see the actual build than take my word for it." Then flip it: "What's the last third-party tool that actually got adopted inside the chart here, and what made that one work?" Their answer tells you the real integration bar, which is almost always cultural rather than technical. |
| “We'll need a BAA and you'll have to go through our full third-party security review.” | Never resist this — it's a qualification signal, not a stall. "Of course. We sign BAAs as standard, here's SOC 2 Type II and our HITRUST status, and here's the completed vendor security questionnaire we've already submitted to two other systems on your EHR." Then ask the question that actually moves the deal: "Who owns third-party risk review here, and how long did your last clinical vendor take to get through it?" If the answer is four months, you now know your close date — and you start the review in parallel with the pilot conversation rather than after it. |
| “Our operating margin is under two percent. There's no budget for anything that isn't billing or compliance.” | Stop selling software; sell a P&L line they already carry. Two levers: physician retention — one avoided departure in a specialty line often covers a multi-clinic contract, and they can tell you their turnover rate off the top of their head — and throughput, where 45 minutes recovered per provider per day is one to two more visits. Make them do the arithmetic out loud with their numbers: "How many providers, and what's your contribution margin per encounter?" The business case has to be in their handwriting, not on your slide, because that's the version that survives the CFO conversation you won't be in. |
| “We tried a scribe vendor two years ago. Half the docs stopped using it after a month.” | Ask what killed it — turnaround time, note quality, specialty coverage, or that it was optional. It's nearly always one of those four, and the answer is diagnostic for how you run the pilot. Then reframe adoption as something you own with them: name a utilization threshold, propose measuring it weekly and reporting it to them, and offer a clause that says if you're below it at day 60 you pull the product out. Physicians and CMIOs trust a vendor who volunteers an exit far more than one who promises success. |
| “Anything touching clinical workflow goes to our EHR governance committee, and they meet monthly.” | Don't route around it — get on the agenda and get your sponsor to co-present. Ask three questions: what has the committee approved and rejected in the last two cycles and why, what does the submission packet have to contain, and who on the committee is the skeptic. Then arm your champion with the one-pager, the architecture doc and a reference call before the meeting. These deals die in governance because the sponsor showed up alone with a vendor slide deck. |
| “Our EHR vendor says they're shipping something like this natively next year.” | The honest answer beats the defensive one: "They probably will, and it'll be fine for the average primary care note. The question is what your physicians are doing for the next 18 months while it's in early adopter release." Then ask which of their sites is actually on the vendor's roadmap and when — usually nobody knows, or it's three releases out. Then ask about specialty coverage. Native tools tend to launch strong in primary care and thin in ortho, derm and behavioral health, which is exactly where the after-hours charting is worst. |
| “We're a two-party consent state — we'd need patient consent to record.” | Have this ready before they raise it, because fumbling it makes you look like you've never sold into a health system. Bring the standard consent language other systems use, whether it's captured verbally at rooming or added to the intake packet, and exactly what the product does when a patient declines. Offer to share how two or three comparable systems operationalized it — most handled it as a one-line addition to the existing consent-to-treat and the front desk barely noticed. It's usually a legal reflex, not a blocker. |
Questions reps ask about this call
- How is a healthcare product demo script different from a normal SaaS demo?
Three differences. First, the buyer's clinicians hold veto power in practice even when they don't on the org chart, so the demo has to survive a physician's judgment about note quality or workflow realism, not just a manager's feature checklist. Second, nothing moves without a BAA and a third-party security review, so integration and PHI handling belong in the first fifteen minutes rather than the follow-up. Third, the purchase usually needs two sponsors — a clinical one like the CMIO or CNO and a financial one like the Director of Revenue Cycle Management — because the pain and the budget sit in different departments. Your demo has to give each of them something to repeat internally.
- What should I show first when the CMIO is on the call?
Whatever they named as their deal-breaker in the opening 90 seconds, not your rehearsed opening. If they said the note has to hold up in ortho, start with an ortho note. If they said it must launch from inside Epic with no second login, your first screen is the in-chart launch. Never open with setup screens, the admin console, or a dashboard — a CMIO who was in clinic that morning reads a dashboard-first demo as evidence you've never watched a real 15-minute visit.
- Which metrics should I put into the demo narration?
Use the ones they're already measured on and make them say the numbers, not you. After-hours EHR time per provider per day against a target of under 30 minutes. Chart closure rate inside 24 or 72 hours. Physician and APP turnover, where every point costs six figures. Visits per provider per day and wRVUs per FTE. Denial rate split by prior-auth denials, and first-pass clean claim rate. For ops leaders, no-show rate and slot fill rate by clinic. Ask them for their current number rather than quoting an industry figure — the business case only survives the CFO conversation if it's built from their data.
- How do I handle 'will it handle X?' in a clinical demo?
Slow down and get the specific case first — "will it handle specialty notes" is unanswerable, but "will it handle a post-op knee follow-up where the surgeon dictates range of motion" is demoable. Then answer one of three ways honestly: yes and here it is, live; yes but not how you'd expect, and show the workaround plainly; or no, we don't do that today and it isn't on this year's roadmap. Follow a no with "how often does that come up — daily, or is that a quarter-end thing?" Never say "we can build that." An experienced health system buyer hears that as the exact promise their last vendor broke.
- What's the right way to answer the reliability question?
Describe the failure mode, not an uptime percentage. Say what still works when you're down, what the clinician's fallback is, and whether anything in the EHR is affected: "Capture queues locally, you lose turnaround not the encounter, and nothing in your chart breaks because we're not in the write path for anything but a draft note." Then give support reality — which issues get a 24/7 phone number with a human, which get next-business-day email, and who the named CSM and escalation contact are. Health system buyers trust a vendor who can describe a past incident cleanly far more than one who claims never to have had one.
- What should the next step be at the end of a healthcare demo?
Two things booked on the call, not one. A 20–30 minute technical session with their clinical informatics analyst covering architecture, SMART on FHIR launch, SSO and security only — no clinical content. And a date tied to their EHR governance committee calendar, working backwards: what the submission packet requires, who co-presents with you, and who on the committee is the likely skeptic. Also start third-party risk review in parallel that week rather than after a pilot decision, because in most systems that review, not your implementation, is the longest item on the timeline.