Should I mention a mutual connection in a cold email?

Only if the connection would be comfortable with it. Name-dropping someone who barely knows you can backfire. If you do mention them, say exactly how you know them in one clause and move on. 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 cold 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. 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 Media cold email?

Don't promise a viral moment. Promise a clean flight. 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 Media inboxes and they all read as "this was templated."

How do I follow up on a stalled media proposal?

Talk about dates, delivery risk, and what happens if they miss the flight. Ask whether brand safety, budget, or creative is the hold. Kit adjectives won't restart a paused IO. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Media · CTO · After Invoice

Cold Email Template for Media CTO: After Invoice

The query is practical: what should a cold email to a Media CTO say for after an invoice? Start with a direct answer, add one proof point about flights that stall, brand-safety scares, and follow-up that reads like leftover kit copy, and close with ask if it's in the next run, or what document is missing.

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 cold email work for a Media CTO?

Lead with an observed trigger, not a compliment about their About page.
Speaks to flights that stall, brand-safety scares, and follow-up that reads like leftover kit copy 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.
Show you understand their bottleneck in their language.

When should I send this to a Media CTO?

Don't follow a cold email the next morning. Give it 4 business days. 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 upfronts and flight dates create urgency. random tuesdays don't. If you're emailing a CTO, 90 words is plenty if the substance is real. Don't pad. Tuesday through Thursday mid-morning local time is a safe default.

What this CTO actually cares about

A CTO in Media 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. 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.

How Media changes the note

Media buyers are sales leads and operators selling attention in a market that keeps changing the rules. They can smell leftover media-kit language. Bring delivery math or a sharp audience observation. A credible proof point in this vertical sounds like: rescued two paused IOs by sending a delivery diagnosis instead of another one-pager. Watch the language. Words that land here include IO, flight, brand safety, CPM, makegood, inventory. A thread that ignores flights that stall, brand-safety scares, and follow-up that reads like leftover kit copy reads like every other vendor bump. Upfronts and flight dates create urgency. Random Tuesdays don't.

How should I customize this template before I send it?

Replace the pain line with a publisher whose advertiser follow-up still leads with 'unique storytelling'.
Keep the tone precise.
Write the subject after the body so it matches the actual hook.
Time it for 3 days after due date. A polite reminder a few days after due, then a firmer operational note.
Don't promise a viral moment. Promise a clean flight.

What mistakes should I avoid with this after invoice note?

Opening with your company story is how cold email dies.
Don't threaten, guilt, or bury the amount.
Don't promise a viral moment. Promise a clean flight.
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	CPM, fill, and campaign delivery against IO
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

[First Name] / [similar company] question

Body

Hi [First Name],

I'll be direct: I help [role peers] cut [pain] without adding another bloated tool.

The version of this that matters for sales leads and operators selling attention in a market that keeps changing the rules is rescued two paused IOs by sending a delivery diagnosis instead of another one-pager. Most [industry] teams I talk to aren't short on tools. They're short on [specific bottleneck]. That's the slice we handle.

Restate number, due date, invoice ID, and pay path in the first screen.

Wrong person? Point me to whoever owns [pain].

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

Questions people ask before they hit send

Don't follow a cold email the next morning. Give it 4 business days. 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.

Related templates

Want a custom draft instead? Try the email generator.