What belongs in a post-meeting follow-up?

Decisions, owners, dates, and anything you promised to send. Keep opinions out unless they asked for a recommendation. A forwardable recap does more for the deal than a paragraph about how 'great it was to connect.' Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Is it okay to send this referral request on LinkedIn instead of email?

Yes if this CTO is actually active there and the thread isn't about long attachments. Keep the LinkedIn version even shorter. Don't paste the full email. One context line and one question is plenty. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What should I never say in a Healthcare referral request?

Don't say 'patients are customers' unless you know that language flies there. Calling it 'AI-powered' with no description of the system. Don't send a pitch deck they didn't ask for as a 'recap.' Those three mistakes show up constantly in Healthcare inboxes and they all read as "this was templated."

Can I mention patient outcomes in a healthcare sales email?

You can talk about operational outcomes like no-shows or throughput. Don't claim clinical results you can't defend, and don't request patient-level data over email. If they want a deeper conversation, take it into their approved channel. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

How should a referral request to a Healthcare CTO change for after a meeting?

Crisp recap energy. They should be able to forward it. Never ask for PHI in email. Don't pretend a consumer app understands clinical workflow. Compliance is not a footnote. The CTO is guarding reliability, security, and engineering time, so the ask should stay at "a technical working session or a written teardown, not a 'vision call'." If you copy a

Healthcare · CTO · After Meeting

Referral Request for Healthcare CTO: After Meeting

When a Healthcare CTO goes quiet (after a meeting), the right referral request email does one job: make a reply cheaper than silence. They look for architecture, failure modes, and whether you'll create toil for their team. Fluff is a ranking signal that you don't know the work. That's why this template leads with no-show rate, door-to-provider time, and denial

Last updated: 2026-09-02 · Reviewed by: Sales Email Template editors

We write templates the way we wrote emails on quota: short, specific, and easy to forward. When we cite research below, it is because the number changes how a buyer reads your note, not to pad the page.

Sources: HubSpot sales email benchmarks; Gong follow-up research

Why does this referral request work for a Healthcare CTO?

Give them cover to decline.
Speaks to staffing gaps, prior-auth delays, and tools that create more clicks in the EHR instead of a generic "value prop."
Fits how a CTO actually reads: 90 words is plenty if the substance is real. Don't pad.
List what you heard, what you promised, and what you need from them, in that order.
Ask for a specific profile, not 'anyone in your network.'

When should I send this to a Healthcare CTO?

Ask after you've given them a reason to want to help, not after the first coffee. Same day, within a few hours. Next morning is the backup, not the plan. For this combo, treat "Same day" as the default, then adjust around budget and credentialing can stretch a simple yes into a quarter. If you're emailing a CTO, 90 words is plenty if the substance is real. Don't pad. After three touches with different value, send a breakup and archive.

What this CTO actually cares about

A CTO in Healthcare is protecting reliability, security, and engineering time. They look for architecture, failure modes, and whether you'll create toil for their team. Fluff is a ranking signal that you don't know the work. The hook that earns a look is an incident class, a security gap, or a cost line they already hate. The ask should stay at this size: a technical working session or a written teardown, not a 'vision call'. Delete trigger: Calling it 'AI-powered' with no description of the system. They look for architecture, failure modes, and whether you'll create toil for their team. Fluff is a ranking signal that you don't know the work.

How Healthcare changes the note

Healthcare buyers are clinic operators, department heads, and vendors who have to respect clinical reality. Never ask for PHI in email. Don't pretend a consumer app understands clinical workflow. Compliance is not a footnote. A credible proof point in this vertical sounds like: dropped no-shows 18% for a four-location clinic without adding front-desk headcount. Watch the language. Words that land here include EHR, prior auth, panel, throughput, credentialing, HIPAA. Budget and credentialing can stretch a simple yes into a quarter. Words that work: EHR, prior auth, panel, throughput, credentialing, HIPAA. Budget and credentialing can stretch a simple yes into a quarter.

How should I customize this template before I send it?

Replace the pain line with an outpatient group drowning in no-shows after a reminder vendor went quiet.
Keep the tone precise.
If they intro you, report back after the meeting.
Time it for Same day. Same day, within a few hours. Next morning is the backup, not the plan.
Don't say 'patients are customers' unless you know that language flies there.

What mistakes should I avoid with this after meeting note?

Asking 'who do you know?' is lazy and gets no names.
Don't send a pitch deck they didn't ask for as a 'recap.'
Don't say 'patients are customers' unless you know that language flies there.
Calling it 'AI-powered' with no description of the system.

How does this after meeting scenario compare?

Dimension	For this template
Best send window	Same day
Ideal length	90 words is plenty if the substance is real. Don't pad.
Primary ask	a technical working session or a written teardown, not a 'vision call'
Industry metric to cite	no-show rate, door-to-provider time, and denial rate
Tone	Precise. No slogans. It's fine to be a little dry.
Unlike after demo	A meeting might have been intro-only. Don't write a product recap they didn't see.
Unlike thank you	Gratitude can live in line one. The rest should be operational.

What should I copy and send?

Copy-ready template

Subject

Forwardable blurb inside, if you're open to an intro

Body

Hi [First Name],

I'm looking for a warm intro to [specific role] who owns [pain], and you came to mind because [reason].

In Healthcare, that usually shows up as staffing gaps, prior-auth delays, and tools that create more clicks in the EHR. Blurb you can paste: '[Your Name] helps [audience] with dropped no-shows 18% for a four-location clinic without adding front-desk headcount. They asked if you'd be open to a short intro about [topic].'

Lock decisions, owners, and dates while memory is still sharp.

If you want changes to the blurb, tell me and I'll rewrite it.

Best,
[Your Name]
[Your Title]
[Your Company]

Questions people ask before they hit send

Only if that's already how you work and it won't make them look mercenary. Many operators prefer a clean intro. If you do mention a fee, keep it secondary to why the intro helps the other person. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Related templates

Want a custom draft instead? Try the email generator.