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

If they agreed in principle, send times the same day while intent is warm. A polite reminder a few days after due, then a firmer operational note. 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.

How do I follow up on an unpaid invoice without damaging the relationship?

Assume a process issue first. Put the facts up top, offer to fix coding or PO problems, and keep the tone operational. Escalate to the original buyer only after AP has had a fair chance. Rage emails get paid last.

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

Don't promise 'AI that runs itself.' They hear that weekly. Going over their head in the same thread. Don't threaten, guilt, or bury the amount. Those three mistakes show up constantly in SaaS inboxes and they all read as "this was templated."

SaaS · Department Head · After Invoice

Meeting Request for SaaS Department Head: After Invoice

When a SaaS Department Head goes quiet (after an invoice), the right meeting request email does one job: make a reply cheaper than silence. They sit between strategy and the people doing the work. They need cover to say yes and a way to not look reckless. That's why this template leads with net revenue retention, time-to-first-value, and expansion inside

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

State the decision you want out of the meeting.
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.
Restate number, due date, invoice ID, and pay path in the first screen.
Put the agenda in the email, not behind a booking link.

When should I send this to a SaaS Department Head?

If they agreed in principle, send times the same day while intent is warm. A polite reminder a few days after due, then a firmer operational note. For this combo, treat "3 days after due date" 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. They sit between strategy and the people doing the work. They need cover to say yes and a way to not look reckless.

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.
Mirror their timezone. Guessing wrong looks careless.
Time it for 3 days after due date. A polite reminder a few days after due, then a firmer operational note.
Don't promise 'AI that runs itself.' They hear that weekly.

What mistakes should I avoid with this after invoice note?

Calendly links with no agenda look like a trap.
Don't threaten, guilt, or bury the amount.
Don't promise 'AI that runs itself.' They hear that weekly.
Going over their head in the same thread.

How does this after invoice scenario compare?

Dimension	For this template
Best send window	3 days after due 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	net revenue retention, time-to-first-value, and expansion inside existing accounts
Tone	Respectful of internal politics without being coy.
Unlike proposal follow-up	The commercial terms were already accepted. You're in collections-lite, not sales.
Unlike apology	Only apologize if you invoiced wrong. Don't apologize for asking to be paid.

What should I copy and send?

Copy-ready template

Subject

[Company Name] / net revenue retention

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 new product launch, a failed implementation, or a security questionnaire stall. I can do [Day] at [Time] or [Day] at [Time] in your timezone. If neither works, reply with a window and I'll bend.

Get paid or learn the blocker: PO, coding, approval, or dispute.

Prefer async? I'll send the brief today.

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 "[Company Name] / net revenue retention" 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.