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

Send it after the third unanswered touch, not after the first silence. 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.

Is a breakup email the same as an unsubscribe?

No. A breakup email closes one thread. If they asked not to be contacted, honor that and remove them. Don't dress a suppression request as a cute last-chance campaign. Tie the note to one metric or stall they already own, and keep the ask answerable in a single sentence.

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 breakup email 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. Tie the note to one metric or stall they already own, and keep the ask answerable in a single sentence.

What should I never say in a Consulting breakup email?

Don't call yourself a thought leader. Let the email be useful instead. 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 Consulting inboxes and they all read as "this was templated."

Consulting · CTO · After Invoice

Breakup Email Template for Consulting CTO: After Invoice

Use this breakup email template when you're emailing a CTO in Consulting (after an invoice). Money is on the table. The relationship is real. Your job is to make payment simple and keep dignity on both sides. Keep the note aligned with Precise. No slogans. It's fine to be a little dry.

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

Copy-ready template

Subject

Should I close the loop on this?

Body

Hi [First Name],

I don't want to keep landing in your inbox if this isn't useful.

In Consulting, that usually shows up as proposals that stall in procurement and relationships that go quiet between projects. In case it's useful later, here's the one-pager on moved three stalled proposals to signature by isolating the real blocker in one email. No need to respond.

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

Okay to close this?

Best,
[Your Name]
[Your Title]
[Your Company]

Why this breakup email works

Ask permission to archive. It feels respectful and it creates a tiny action.
Speaks to proposals that stall in procurement and relationships that go quiet between projects 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.
Take the pressure off. People reply to breakup emails because they're allowed to say no.

When should I send this to a Consulting CTO?

Send it after the third unanswered touch, not after the first silence. 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 a small diagnostic can start in a week. a transformation waits on a sponsor. 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 Consulting 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. 90 words is plenty if the substance is real. Don't pad.

How Consulting changes the note

Consulting buyers are partners and delivery leads selling expertise while protecting utilization. They've written prettier decks than yours. Compete on diagnosis and next step, not on adjectives. A credible proof point in this vertical sounds like: moved three stalled proposals to signature by isolating the real blocker in one email. Watch the language. Words that land here include SOW, utilization, workstream, sponsor, retainer, change request. A small diagnostic can start in a week. A transformation waits on a sponsor. Don't call yourself a thought leader. Let the email be useful instead.

Customization tips

Replace the pain line with a boutique firm whose last project ended well and then nobody asked for the next phase.
Keep the tone precise.
Keep the tone adult. No 'I guess you're not interested' sulk.
Time it for 3 days after due date. A polite reminder a few days after due, then a firmer operational note.
Don't call yourself a thought leader. Let the email be useful instead.

Common mistakes

Sarcastic breakup emails feel clever to you and cheap to them.
Don't threaten, guilt, or bury the amount.
Don't call yourself a thought leader. Let the email be useful instead.
Calling it 'AI-powered' with no description of the system.

How this scenario compares

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	utilization, proposal win rate, and time to SOW
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.

Questions people ask before they hit send

Name the situation and the business object, not your excitement. Something like "Should I close the loop on this?" 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.