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

If they agreed in principle, send times the same day while intent is warm. 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.

Is it rude to send a calendar link?

It's rude when the link is the whole email. It's fine when you include an agenda, two suggested times, and a note that they can pick anything else. Give them a way to stay in the thread. 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 meeting 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 Non-Profit meeting request?

Don't imply their mission is inefficient. Help them tell it better. 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 Non-Profit inboxes and they all read as "this was templated."

Non-Profit · Department Head · After Demo

Meeting Request for Non-Profit Department Head: After Demo

A meeting request email asks for time by showing the agenda, the reason it matters now, and how little of their calendar you actually need. For Non-Profit teams, the version that works for after a demo has to respect Don't pitch like a VC. Write to the department head like they already have a full calendar and a reason to

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 meeting request work for a Non-Profit Department Head?

Put the agenda in the email, not behind a booking link.
Speaks to donor follow-up that feels automated and grant calendars that punish delay 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.
State the decision you want out of the meeting.

When should I send this to a Non-Profit Department Head?

If they agreed in principle, send times the same day while intent is warm. 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 boards and grant windows set the pace. ignore that and you'll look amateur. 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 Non-Profit 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. If your note would embarrass them in a team channel, rewrite it.

How Non-Profit changes the note

Non-Profit buyers are ED teams, development leads, and program directors stretching every dollar. Don't pitch like a VC. Mission language has to be specific to their programs, not a generic 'doing good.' A credible proof point in this vertical sounds like: improved second-gift conversion 17% with thank-you notes that named the program, not the CRM. Watch the language. Words that land here include restricted funds, board, grant cycle, stewardship, program officer. Boards and grant windows set the pace. Ignore that and you'll look amateur. Words that work: restricted funds, board, grant cycle, stewardship, program officer.

How should I customize this template before I send it?

Replace the pain line with a development shop whose lapsed-donor emails all start with 'just checking in'.
Keep the tone respectful of internal politics without being coy.
Send a calendar hold as soon as they pick a time.
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 imply their mission is inefficient. Help them tell it better.

What mistakes should I avoid with this after demo note?

Calendly links with no agenda look like a trap.
Don't send a 19-page deck that relitigates features they skipped.
Don't imply their mission is inefficient. Help them tell it better.
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	donor retention, grant hit rate, and cost per dollar raised
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

Two times for a [topic] working session

Body

Hi [First Name],

You mentioned [pain]. A short working session is the fastest way to see if we can help.

I'm writing because a gala, a grant deadline, or a board meeting with a gap in the packet. Agenda: 5 minutes on current [process], 5 on where [Your Product] would sit, 5 on go / no-go. I'll send notes after either way.

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

Which of those two times is less annoying?

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 "Two times for a [topic] working session" 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.