How many times should I follow up with a Department Head (after a demo)?

If a mutual offered the intro, send it while their permission is fresh. Same day with the recap. A value bump 3 days later if they went quiet. After that, send a breakup note and archive it. A department head who wants it will answer a clean close more often than a fifth bump.

How do I introduce myself without sounding stiff?

Use one sentence for who you help and one sentence for why now. Skip the origin story. If a mutual is involved, put their name near the top so the email has a human reason to exist. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Should I include a recording in the demo follow-up?

If you recorded it and they agreed, yes, plus timestamps for the two parts they cared about. A raw 40-minute link with no map is homework. Add the three bullets they'd need to brief a colleague. 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 introduction on LinkedIn instead of email?

Yes if this department head 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 introduction?

Don't say 'patients are customers' unless you know that language flies there. Going over their head in the same thread. Don't send a 19-page deck that relitigates features they skipped. Those three mistakes show up constantly in Healthcare inboxes and they all read as "this was templated."

Healthcare · Department Head · After Demo

Introduction for Healthcare Department Head: After Demo

Use this introduction template when you're emailing a Department Head in Healthcare (after a demo). They saw the product. Now they're comparing, forwarding, or quietly deciding it wasn't for them. Keep the note aligned with Respectful of internal politics without being coy.

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 introduction work for a Healthcare Department Head?

Lead with the overlap, not your résumé.
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 department head actually reads: Give enough context that they can forward the email upward.
Replay the two moments they leaned in, and the one concern they named.
Make it easy to decline.

When should I send this to a Healthcare Department Head?

If a mutual offered the intro, send it while their permission is fresh. Same day with the recap. A value bump 3 days later if they went quiet. For this combo, treat "Same day, then 3 days if silent" as the default, then adjust around budget and credentialing can stretch a simple yes into a quarter. If you're emailing a department head, Give enough context that they can forward the email upward.

What this Department Head actually cares about

A department head in Healthcare is protecting their team's load and their standing with leadership. They sit between strategy and the people doing the work. They need cover to say yes and a way to not look reckless. The hook that earns a look is a department KPI, a staffing bind, or a tool the team already hates. The ask should stay at this size: a working review they can invite a deputy to. Delete trigger: Going over their head in the same thread. They sit between strategy and the people doing the work. They need cover to say yes and a way to not look reckless.

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. Words that work: EHR, prior auth, panel, throughput, credentialing, HIPAA. A thread that ignores staffing gaps, prior-auth delays, and tools that create more clicks in the EHR reads like every other vendor bump.

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 respectful of internal politics without being coy.
Keep titles accurate. Inflating your role gets checked.
Time it for Same day, then 3 days if silent. Same day with the recap. A value bump 3 days later if they went quiet.
Don't say 'patients are customers' unless you know that language flies there.

What mistakes should I avoid with this after demo note?

Giant bios make intros feel like homework.
Don't send a 19-page deck that relitigates features they skipped.
Don't say 'patients are customers' unless you know that language flies there.
Going over their head in the same thread.

How does this after demo scenario compare?

Dimension	For this template
Best send window	Same day, then 3 days if silent
Ideal length	Give enough context that they can forward the email upward.
Primary ask	a working review they can invite a deputy to
Industry metric to cite	no-show rate, door-to-provider time, and denial rate
Tone	Respectful of internal politics without being coy.
Unlike after meeting	They have product context now. Speak to what they saw, not to a generic intro.
Unlike after proposal	Pricing may not be on paper yet. Don't jump to 'ready to sign.'

What should I copy and send?

Copy-ready template

Subject

Quick intro on [shared problem]

Body

Hi [First Name],

I'm reaching out because [specific overlap], not because I collect new LinkedIn contacts.

In Healthcare, that usually shows up as staffing gaps, prior-auth delays, and tools that create more clicks in the EHR. Happy to send a 5-line brief before any call so you know what you'd be walking into.

Given this is after a demo, ask who else needs to see it, or whether a narrower use case is the better start.

Open to a short intro chat, or should I leave this with [Mutual]?

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

Questions people ask before they hit send

Name the situation and the business object, not your excitement. Something like "Quick intro on [shared problem]" outperforms "Just checking in" because a department head can decide from the preview text whether it's worth opening. Keep it under 50 characters when you can.

Related templates

Want a custom draft instead? Try the email generator.