What subject line works for Marketing referral request emails (after an invoice)?

Name the situation and the business object, not your excitement. Something like "CTO question on after invoice" 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.

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

Ask after you've given them a reason to want to help, not after the first coffee. 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 I offer a referral fee in the email?

Only if that's already how you work and it won't make them look mercenary. Many operators prefer a clean intro. If you do mention a fee, keep it secondary to why the intro helps the other person. 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 referral request 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.

Marketing · CTO · After Invoice

Referral Request for Marketing CTO: After Invoice

A referral request email asks someone to make an intro by doing the work for them: who, why, and a forwardable blurb. For Marketing teams, the version that works for after an invoice has to respect They can detect recycled 'growth hacking' copy in one glance. Write to the CTO like they already have a full calendar and a reason

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 referral request work for a Marketing CTO?

Include a forwardable paragraph.
Speaks to attribution arguments, creative fatigue, and a stack of tools that don't share data 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.
Explain why they'd look good for making the intro.

When should I send this to a Marketing CTO?

Ask after you've given them a reason to want to help, not after the first coffee. 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 tactical buys can happen this month. brand platforms wait on planning cycles. 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 Marketing 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 Marketing changes the note

Marketing buyers are managers and directors measured on pipeline, not on how clever the campaign felt. They can detect recycled 'growth hacking' copy in one glance. Bring a sharp observation or don't send. A credible proof point in this vertical sounds like: recovered 19% of paid pipeline after a landing-page follow-up overhaul. Watch the language. Words that land here include campaign, attribution, creative, CAC, MQL, incrementality. Proof that lands: recovered 19% of paid pipeline after a landing-page follow-up overhaul. Proof that lands: recovered 19% of paid pipeline after a landing-page follow-up overhaul. If you cannot name a budget cut, a rebrand, or a channel that stopped converting, wait until you can.

How should I customize this template before I send it?

Replace the pain line with a demand-gen team whose webinar follow-up still looks like 2019 nurture.
Keep the tone precise.
Don't attach a commission offer unless that's already your model.
Time it for 3 days after due date. A polite reminder a few days after due, then a firmer operational note.
Don't promise virality. It's a tell.

What mistakes should I avoid with this after invoice note?

Asking 'who do you know?' is lazy and gets no names.
Don't threaten, guilt, or bury the amount.
Don't promise virality. It's a tell.
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	CAC, pipeline contribution, and paid-to-organic mix
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

CTO question on after invoice

Body

Hi [First Name],

I'm looking for a warm intro to [specific role] who owns [pain], and you came to mind because [reason].

I'm writing because a budget cut, a rebrand, or a channel that stopped converting. If now is a bad time, don't spend political capital on this.

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

Comfortable making that intro, or should I find another path?

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

Questions people ask before they hit send

Evidence you understand their stack constraints and won't waste engineering time. Mention a real integration, a failure mode, or a security question you already answered. Demo theater is how you get routed to /dev/null. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Related templates

Want a custom draft instead? Try the email generator.