A clinician decides whether to trust your app long before anyone on your team gets a meeting with her. By the time your clinical liaison is on a call, the decision is mostly already made. What's left is confirmation, not persuasion.
That gap matters more in digital health than in almost any other software category. A dentist comparing two scheduling tools is picking a workflow. A physician deciding whether to recommend a mental health app to a patient is putting her name behind something that touches a person's care. The stakes are different, and so is the evaluation underneath them.
The quiet audit that happens first
Most digital health founders assume the sales process starts with a discovery call. It doesn't. It starts weeks or months earlier, when a clinician who might champion your product runs her own private audit, alone, with no input from you.
She checks whether you have FDA clearance, or whether you're claiming to be "clinically validated" without saying what that means. She looks for who sits on your clinical advisory board and whether those are real, checkable people or a slide full of logos. She searches your company name alongside a colleague's name, hoping someone she trusts has already used it.
This happens on your website, in your published content, and in whatever comes up when she searches you at 11pm after a long clinic day. Your sales team isn't in the room for any of it.
What she's actually screening for
Four things dominate this private evaluation, and they rarely come up on a sales call, because by the time the call happens, she's already decided.
Liability. If she recommends your app and something goes wrong, is she exposed? Clinicians think about this constantly. Most digital health marketing never addresses it directly, which reads as an omission, not neutrality.
Overselling. Does your content claim more than your evidence supports? A clinician trained to read a trial result can spot inflated language in a blog post as easily as in a paper. One oversold claim, and she assumes the rest of your content is marketing rather than information.
Extra work. Does adopting this tool add more for her to manage: more alerts to triage, more patient questions she has to field without a ready answer? Time is the resource clinicians guard hardest, and they can smell a tool that was designed without that constraint in mind.
Peer signal. Has anyone she actually trusts used this already? A single colleague who says "I checked, it's fine" carries more weight than anything on your website, which is exactly why she goes looking for that person before she ever replies to an email.
Why overselling costs more in health than anywhere else
A practice manager reading exaggerated software marketing rolls her eyes and moves on. A clinician reading exaggerated health claims has a sharper reaction: distrust that spreads to everything else you've published.
Founders coming from a general tech background tend to underestimate this. In most B2B categories, confident marketing language is expected and mostly filtered out. In health, it gets read as a signal about whether you understand the line between a feature and a clinical claim. Cross that line once, publicly, and you've likely lost her.
The instinct to soften a study's actual finding, round up a small effect size, or drop a caveat that makes a result less impressive: all of it registers as a warning sign to exactly the reader you most need to convince.
The same pattern across categories
This shows up almost identically across digital health, even though the products have nothing in common on the surface.
A mental health app asks a psychiatrist to recommend it to patients between sessions. She's not evaluating the interface. She's checking whether the crisis-escalation pathway actually reaches a real person fast enough, and whether the company's content admits that the app isn't a substitute for care when someone is in danger.
A chronic disease management platform asks an endocrinologist to trust its glucose data enough to act on it. She's checking whether the company's published material explains the margin of error, or whether it talks only about accuracy in the abstract.
An AI-assisted diagnostic tool asks a radiologist to trust a second opinion generated by a model. She's checking whether the company is honest, in writing, about the cases where the model underperforms, not just the cases where it shines.
A remote patient monitoring device asks a cardiologist to act on data collected outside her practice, from a device she didn't calibrate herself. She's checking who gets alerted first when a reading crosses a threshold, and whether that workflow is spelled out anywhere she can read it before she agrees to pilot it.
Different specialties, different risks, same underlying question: does this company understand its own limits well enough to say them out loud?
What earns trust before you ever speak to her
The content that moves a skeptical clinician is the content that shows you understand where your product's limits are, not the content built to make it look its best.
That means publishing the caveat next to the claim, not burying it in a footnote. It means naming your clinical advisors with real credentials attached, so someone can verify them in two minutes on a licensing board site. It means writing honestly about where your category falls short, including cases where your type of product isn't the right fit for a patient.
That's uncomfortable for a founder trying to build momentum. It's also the only version of content a clinician trained to spot overselling will actually believe.
Content formats that actually pass this test
Some formats earn clinical trust more reliably than others, because they're structurally harder to oversell in.
A methodology post that walks through exactly how a claim was measured, including the sample and the parts of the result that were unremarkable, reads as credible precisely because it isn't trying to impress. A named advisor bio with a license number or a link to a published paper does more work than a testimonial quote ever will. A guest post genuinely written by a practicing clinician, in her own voice, with her own hedges left in rather than smoothed out by an editor, carries a kind of authority no in-house writer can manufacture. A limitations page that plainly lists the situations the product doesn't yet handle well, on its own page rather than folded into an about page nobody reads, tells a skeptical reader more than any features list.
What doesn't work: patient testimonials framed as clinical evidence, and advisory board sections that list first names and job titles with nothing to verify.
The trust gap most digital health content misses
Felix's instinct, understandably, is to write for two audiences at once: the patients who'll use the product and the clinicians who need to trust it enough to recommend it. Most teams solve this by running two separate content tracks, one simplified for patients and one dense with citations for clinicians.
That split misses the actual problem. A clinician doesn't need denser content. She needs content that states what the evidence shows, names its limits plainly, and lets her draw her own conclusion instead of doing her judgment for her. One well-reasoned piece that does this will earn more trust from a clinical reader than a citation-heavy piece that oversells its own confidence.
A useful test before anything publishes: does this contain a fact a clinician couldn't have guessed without real familiarity with this specific patient population or condition? If not, the piece reads as marketing wearing an expert's coat, and a clinical reader clocks that in the first paragraph.
What this costs you when you get it wrong
The cost of losing a clinical champion rarely shows up on a dashboard. It shows up as a slower sales cycle nobody can quite explain, a pilot that never gets a second site, or a physician who quietly stops mentioning your app to colleagues after one overclaimed headline.
Clinicians talk to each other. A specialty is smaller than it looks from the outside, and a reputation for overselling travels faster inside it than most founders expect. Repair is slow: rebuilding credibility with one skeptical clinician takes 4 or 5 pieces of careful, caveat-honest content, minimum, and only after the first offending claim has been fixed or retracted.
Investors reading your public content during diligence are running a version of the same check, even if they'd never call it that. A due diligence associate who finds an overclaimed headline on your blog asks a harder question in the next meeting, not because the claim itself is fatal, but because it makes her wonder what else got rounded up. The same discipline that earns a clinician's trust earns an investor's, for the same reason: both are checking whether you know the difference between what you hope is true and what you can actually show.
Building this into how you write, not just what you write
Treat this as a standing filter every piece passes through before it goes out, not a one-time content decision.
Before publishing anything aimed at a clinical audience, run it through three checks. Does it state a limitation as clearly as it states a benefit? Does every named credential hold up if someone actually looks it up? Would a clinician reading this at the end of a long shift trust the person who wrote it, or assume it came from someone in marketing who's never sat in an exam room?
A piece that fails any of those isn't ready. Fixing it after publication, once a clinician has already formed an opinion of your company, costs far more than getting it right the first time.
Trust before the first call, or after it
By the time your team is on a call with a clinician who might champion your product, she's typically already run this audit silently and reached a conclusion. Sales conversations at that point mostly confirm a decision already made, or lose one that was still open.
That's the case for treating your published content as the real first meeting, not the marketing that precedes one. Write it as if the clinician reading it is deciding, right now, whether to trust you. She is.