The slide your investor loves and no clinician has seen
Felix has a slide that says his pilot held 94% retention across three clinics. His investor likes that slide. It's the first thing he pulls up on a call.
His next twenty clinical prospects have never seen it. If they did, most wouldn't trust it. A number with no patient attached to it reads as marketing, not evidence, to someone who's been burned by vendor stats before.
That's the gap. Two audiences reading the same company, trusting almost nothing the other one accepts as proof. Most digital health founders build proof for one of them and assume it covers both. It doesn't.
Two different questions, asked by two different readers
An investor reading your deck is asking one thing: does this work at a scale that returns the fund, and how fast. Their job is pricing growth against risk.
A clinician reading your site or your outreach is asking something else entirely: will this work for my patients, without creating more risk than it removes. Their job is protecting people who trusted them first.
Same product. Same founder. Two questions that don't share an answer, because they're not actually the same question wearing different clothes.
What actually convinces an investor
Investors want trajectory. A number that moved, a cohort that held, a curve bending the right direction over time. "94% retention across three pilot sites" works on them because it's a momentum claim, and momentum is what they're pricing.
That same line does almost nothing for a clinical buyer. It says nothing about how the product behaves in the middle of a real patient's messy week, and clinical buyers have learned to distrust aggregate percentages on sight. Too many vendors have shown up with a "94%" that turned out to mean 94% of nineteen people, in a setting nothing like theirs.
What actually convinces a clinician
Clinicians want a story with a patient in it. What happened with one person, one workflow, one week where something didn't go to plan, and what the team did about it.
A named failure with a fix attached is worth more to a clinician than a clean success story. It proves someone on your team has actually watched the product meet a patient, not just a spreadsheet. It also tells them what happens on the day something breaks with their own patients, which is the question they actually care about.
This is why the anonymized pilot story so often outperforms the polished case study. Detail reads as real. Polish reads as edited.
What not to overclaim
Digital health founders live close to language that can read as a clinical claim even when nobody meant it that way. Care matters here more than in most B2B categories.
"Completion rose to 80% after we moved the reminder time" describes one pilot. It is not a claim that this fixes adherence across every patient population, and investors will read past that distinction faster than a clinician will. A compliance reviewer at a health system will hold you to it hardest of all.
The fix is precise attribution: name the setting, name the sample size, say plainly that this is what changed in this pilot. Precision reads as credible. Vagueness reads as evasive, and a stat with no boundary around it reads like a company that hasn't yet learned what it's allowed to say.
The one thing both readers actually trust
Investors and clinicians disagree about which numbers matter. They agree on something else: both can tell when a claim was never checked.
A founder who writes "we don't have enough data on this yet, here's what we're watching for" usually earns more trust from both audiences than one who forces a stat where none exists yet. Stated plainly, that kind of limit reads as a team that knows the difference between a result and a hope. Readers who've been oversold before notice the difference immediately.
Why founders build the investor version and stop there
Investor-grade proof is the path of least resistance. The metrics already live in a dashboard somewhere. Screenshotting a chart and writing one line under it takes twenty minutes.
Clinician-grade proof takes longer. Someone has to sit with a site, write down what happened while it's still fresh, check the account with whoever was in the room, and strip anything that starts to sound like marketing before it goes near a clinical inbox.
So founders build the version that's already sitting there and assume it does double duty. A clinician who lands on a homepage full of investor stats reads it as a company that hasn't spent enough time in a clinic to have a real story yet, whether or not that's actually true.
The part that costs you at the next raise, not just the next clinical deal
It shows up in diligence too, not just in the sales conversation.
An associate reading your public footprint before a partner meeting doesn't stop at your metrics slide. Part of their job is checking whether your product holds up with the exact audience you claim to serve, and your website is where they go to check.
If every public thing you've published is investor-shaped, aggregate percentages, growth charts, a logo wall, that associate reading it as a stand-in for a clinician gets nothing useful. They can see the line goes up. They can't see whether the product survives a real patient.
Founders who publish both kinds of proof hand that associate two things at once: a number for the model, and a specific account a clinician would actually believe. The second piece is what turns a diligence call into someone advocating for you internally, rather than someone who has to take your word for the clinical side on faith.
Both come from the same work, not two separate jobs
This means pulling two different cuts from the same operational reality, not running two separate content programs.
Every pilot and every rollout throws off both kinds of material, if someone captures it close to when it happens instead of trying to reconstruct it three months later from memory.
The number is your investor line: what moved, and by how much. The account is your clinician line: what happened with one patient or one site coordinator, what broke, what the team changed. Most founders keep the first because it's already sitting in analytics. The second usually exists for about a day, in a Slack message or a note after a site visit, before it gets cut from the polished update that goes out to the board.
Keep that note instead of deleting it. It's the raw material for the piece a clinician will actually read.
Two habits make this easy to sustain: someone writes the messy version down within a day of it happening, and nobody edits it into board language until after it's been saved somewhere the founder can find it again.
What this looks like with a real pilot
Say a pilot site reports that 80% of patients completed a six-week program, up from 55% before you added reminder texts. That's your investor line, clean and quotable as it stands.
The clinician version comes from what's underneath it. Maybe the 55% baseline included patients who dropped off because the reminder landed at 7am, before their shift started, and the fix wasn't a smarter algorithm. It was letting each patient choose their own reminder time in week one instead of week four. That detail, one scheduling problem, one specific fix, is what a physical therapist reads and recognizes from their own caseload.
Same pilot. Same underlying work. Two pieces built for two readers who trust completely different things.
What to do this week
Pull your last two pilot updates or investor emails. From each one, take the number that works as a headline stat. Then separately, take one specific account: a patient, a site coordinator, a moment where something didn't work and someone fixed it.
Write the number up as a single line for your deck or your metrics page. Write the account up as 300 to 500 words, with enough operational detail that a clinician in that specialty would recognize the situation from their own week. Publish that second piece somewhere a clinical prospect will actually see it: your site, LinkedIn, an email to a warm clinical list. Not an appendix slide nobody outside your cap table opens.
Do that twice a month and you've built a proof library that works on both readers, instead of one that only works on whichever one you happened to have material for.
Two things to check before you publish either piece: has the site or clinician actually agreed to be described, even without a name attached, and does the number have a boundary around it (setting, sample, timeframe) instead of floating free as a headline stat.
Neither reader is optional
Investors want to see the line go up. Clinicians want to know you were in the room when it didn't, and what you did next. You need both if the plan is to close the next round and sign the next site.
Most founders build the investor version because it's already sitting in a dashboard. The clinician version has to be written down on purpose, closer to when it happened than anyone thinks they have time for.
That gap is cheap to close. It just takes someone deciding, before the next site visit, that the messy detail is worth keeping instead of tidying away.