Sales EmailTemplate

Finance · Department Head · After Demo

Referral Request for Finance Department Head: After Demo

A referral request email for a Finance Department Head (after a demo) is a short message that reopens the thread without making them do extra work. A referral request email asks someone to make an intro by doing the work for them: who, why, and a forwardable blurb. In this setting, that means speaking to month-end drag, messy reconciliations, and

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 Finance Department Head?

  • Give them cover to decline.
  • Speaks to month-end drag, messy reconciliations, and tools that fail audit questions 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 Finance 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 a point solution can land fast. anything touching the ledger gets a longer review. 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 Finance 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 Finance changes the note

Finance buyers are controllers, advisors, and operators who get paid to reduce risk, not collect slogans. Don't promise returns, 'guaranteed savings,' or anything that sounds like unlicensed advice. Precision beats charisma. A credible proof point in this vertical sounds like: cut close from 12 days to 7 for a 180-person firm without adding headcount. Watch the language. Words that land here include close, recon, controls, audit trail, materiality, fiduciary. Words that work: close, recon, controls, audit trail, materiality, fiduciary. A thread that ignores month-end drag, messy reconciliations, and tools that fail audit questions reads like every other vendor bump.

How should I customize this template before I send it?

  • Replace the pain line with a mid-market finance team still exporting CSVs to glue two systems together.
  • 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 use casino metaphors. It's not cute in this inbox.

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 use casino metaphors. It's not cute in this inbox.
  • Going over their head in the same thread.

How does this after demo scenario compare?

DimensionFor this template
Best send windowSame day, then 3 days if silent
Ideal lengthGive enough context that they can forward the email upward.
Primary aska working review they can invite a deputy to
Industry metric to citeclose time, error rate, and cost of exceptions
ToneRespectful of internal politics without being coy.
Unlike after meetingThey have product context now. Speak to what they saw, not to a generic intro.
Unlike after proposalPricing 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],

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

The version of this that matters for controllers, advisors, and operators who get paid to reduce risk, not collect slogans is cut close from 12 days to 7 for a 180-person firm without adding headcount. If now is a bad time, don't spend political capital on this.

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

Comfortable making that intro, or should I find another path?

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.