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

Give it 3 to 5 business days after the last note before you ping again. A polite reminder a few days after due, then a firmer operational note. After that, send a breakup note and archive it. A CTO who wants it will answer a clean close more often than a fifth bump.

Should a follow-up repeat the original pitch?

No. Repeat the reason you're relevant in one sentence, then add something new: a proof point, a tighter ask, or a way out. Replaying the first email makes you look automated. 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 follow-up on LinkedIn instead of email?

Yes if this CTO 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 follow-up?

Don't imply their mission is inefficient. Help them tell it better. Calling it 'AI-powered' with no description of the system. Don't threaten, guilt, or bury the amount. Those three mistakes show up constantly in Non-Profit inboxes and they all read as "this was templated."

Non-Profit · CTO · After Invoice

Follow-Up Email Template for Non-Profit CTO: After Invoice

A follow-up email is a short, context-rich message that reconnects after an earlier touch without restating the whole pitch. For Non-Profit teams, the version that works for after an invoice has to respect Don't pitch like a VC. Write to the CTO like they already have a full calendar and a reason to be cautious.

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 follow-up work for a Non-Profit CTO?

Offer an exit so the email doesn't feel like a trap.
Speaks to donor follow-up that feels automated and grant calendars that punish delay instead of a generic "value prop."
Fits how a CTO actually reads: 90 words is plenty if the substance is real. Don't pad.
Restate number, due date, invoice ID, and pay path in the first screen.
Name a specific pain instead of 'circling back' with no payload.

When should I send this to a Non-Profit CTO?

Give it 3 to 5 business days after the last note before you ping again. 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 boards and grant windows set the pace. ignore that and you'll look amateur. If you're emailing a CTO, 90 words is plenty if the substance is real. Don't pad.

What this CTO actually cares about

A CTO in Non-Profit is protecting reliability, security, and engineering time. They look for architecture, failure modes, and whether you'll create toil for their team. Fluff is a ranking signal that you don't know the work. The hook that earns a look is an incident class, a security gap, or a cost line they already hate. The ask should stay at this size: a technical working session or a written teardown, not a 'vision call'. Delete trigger: Calling it 'AI-powered' with no description of the system. an incident class, a security gap, or a cost line they already hate

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 precise.
Match their channel. If they live in Slack, don't keep emailing.
Time it for 3 days after due date. A polite reminder a few days after due, then a firmer operational note.
Don't imply their mission is inefficient. Help them tell it better.

What mistakes should I avoid with this after invoice note?

The fastest way to get ignored is stacking three asks into one nudge.
Don't threaten, guilt, or bury the amount.
Don't imply their mission is inefficient. Help them tell it better.
Calling it 'AI-powered' with no description of the system.

How does this after invoice scenario compare?

Dimension	For this template
Best send window	3 days after due date
Ideal length	90 words is plenty if the substance is real. Don't pad.
Primary ask	a technical working session or a written teardown, not a 'vision call'
Industry metric to cite	donor retention, grant hit rate, and cost per dollar raised
Tone	Precise. No slogans. It's fine to be a little dry.
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

One detail I forgot to mention

Body

Hi [First Name],

Wanted to reconnect while [topic] is still fresh.

I'm writing because a gala, a grant deadline, or a board meeting with a gap in the packet. I sent a note on donor follow-up that feels automated and grant calendars that punish delay and didn't want it to die in the pile. Here's the 15-second version: improved second-gift conversion 17% with thank-you notes that named the program, not the CRM.

Given this is after an invoice, ask if it's in the next run, or what document is missing.

Worth a 10-minute look this week, or should I wait?

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 "One detail I forgot to mention" outperforms "Just checking in" because a CTO 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.