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 referral request 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 SaaS referral request?

Don't promise 'AI that runs itself.' They hear that weekly. 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 SaaS inboxes and they all read as "this was templated."

What do SaaS buyers actually reply to in email?

A specific bottleneck they already feel: activation, seat waste, a painful integration, or a renewal that's going to get questioned. Vague 'growth' language gets archived. Tie your note to a metric they report to a board or a boss. 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 SaaS Department Head change for after a demo?

Helpful and specific to what they clicked and asked. They've been burned by tools that demo well and then die in implementation. Lead with integration and time-to-value, not feature lists. The department head is guarding their team's load and their standing with leadership, so the ask should stay at "a working review they can invite a deputy to." If you

SaaS · Department Head · After Demo

Referral Request for SaaS Department Head: After Demo

Use this referral request template when you're emailing a Department Head in SaaS (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 referral request work for a SaaS Department Head?

Give them cover to decline.
Speaks to time-to-value that slips past the first 14 days and quietly becomes churn 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.
Ask for a specific profile, not 'anyone in your network.'

When should I send this to a SaaS Department Head?

Ask after you've given them a reason to want to help, not after the first coffee. 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 evaluation can close in two weeks for a point tool or drag a quarter when security is involved. 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 SaaS 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. Tone: Respectful of internal politics without being coy.

How SaaS changes the note

SaaS buyers are software teams juggling seat growth, churn, and a stack that's already too loud. They've been burned by tools that demo well and then die in implementation. Lead with integration and time-to-value, not feature lists. A credible proof point in this vertical sounds like: cut onboarding from 19 days to 6 for a 40-person customer success team. Watch the language. Words that land here include activation, seats, SSO, sandbox, expansion, churn. Evaluation can close in two weeks for a point tool or drag a quarter when security is involved. Words that work: activation, seats, SSO, sandbox, expansion, churn.

How should I customize this template before I send it?

Replace the pain line with a B2B SaaS company adding usage-based billing on top of a messy seat model.
Keep the tone respectful of internal politics without being coy.
If they intro you, report back after the meeting.
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 promise 'AI that runs itself.' They hear that weekly.

What mistakes should I avoid with this after demo note?

Asking 'who do you know?' is lazy and gets no names.
Don't send a 19-page deck that relitigates features they skipped.
Don't promise 'AI that runs itself.' They hear that weekly.
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	net revenue retention, time-to-first-value, and expansion inside existing accounts
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

Department Head question on after demo

Body

Hi [First Name],

If you're willing, I wrote a blurb you can forward as-is.

I'm writing because a new product launch, a failed implementation, or a security questionnaire stall. Blurb you can paste: '[Your Name] helps [audience] with cut onboarding from 19 days to 6 for a 40-person customer success team. They asked if you'd be open to a short intro about [topic].'

Replay the two moments they leaned in, and the one concern they named.

Thanks either way. I know intros cost you something.

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.