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

Send it as soon as you know you were wrong. Delay makes it look calculated. On the review date you set. If you didn't set one, five business days. 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 okay to apologize by email instead of a call?

Email is fine for operational misses and creates a record of the fix. If you embarrassed them in front of their team or blew a customer moment, call first and follow with a written recap. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What if they go silent after receiving the proposal?

Assume a process problem before you assume a no. Ask which layer is stuck and offer a thinner version. If you get nothing after a breakup note, archive it. Endless bumps after a proposal train them to wait for a discount.

Is it okay to send this apology 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 apology?

Don't imply their mission is inefficient. Help them tell it better. Going over their head in the same thread. Don't resend the PDF with 'just bumping this.' Those three mistakes show up constantly in Non-Profit inboxes and they all read as "this was templated."

Non-Profit · Department Head · After Proposal

Apology for Non-Profit Department Head: After Proposal

A apology email for a Non-Profit Department Head (after a proposal) is a short message that reopens the thread without making them do extra work. An apology email names the miss, owns it without excuses, states the fix, and tells them what changes so it doesn't happen again. In this setting, that means speaking to donor follow-up that feels automated

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

Ask what repair looks like to them instead of guessing.
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.
Offer to cut scope, split phases, or walk a second stakeholder through one page.
Use 'I' or 'we,' not 'sorry if you were offended.'

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

Send it as soon as you know you were wrong. Delay makes it look calculated. On the review date you set. If you didn't set one, five business days. For this combo, treat "5 business days, or the agreed date" 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. If you cannot name a gala, a grant deadline, or a board meeting with a gap in the packet, wait until you can. If you cannot name a gala, a grant deadline, or a board meeting with a gap in the packet, wait until you can.

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.
Don't CC the world on an apology unless they were affected.
Time it for 5 business days, or the agreed date. On the review date you set. If you didn't set one, five business days.
Don't imply their mission is inefficient. Help them tell it better.

What mistakes should I avoid with this after proposal note?

If you explain more than you apologize, it's not an apology.
Don't resend the PDF with 'just bumping this.'
Don't imply their mission is inefficient. Help them tell it better.
Going over their head in the same thread.

How does this after proposal scenario compare?

Dimension	For this template
Best send window	5 business days, or the agreed date
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 demo	The commercial conversation has started. Be explicit about decision mechanics.
Unlike invoice reminder	They don't owe you money yet. Don't sound like collections.

What should I copy and send?

Copy-ready template

Subject

I'm sorry about [specific miss]

Body

Hi [First Name],

I owe you a direct apology for [incident].

I'm writing because a gala, a grant deadline, or a board meeting with a gap in the packet. We're changing [process] so this can't silently fail again. I'll send proof when that change is live.

Given this is after a proposal, ask whether the hold is scope, price, timing, or people.

I can hop on a call this afternoon if that's faster than email.

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 "I'm sorry about [specific miss]" 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.