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 send a 19-page deck that relitigates features they skipped. 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. Tie the note to one metric or stall they already own, and keep the ask answerable in a single sentence.

How should a cold email to a Media CTO change for after a demo?

Helpful and specific to what they clicked and asked. They can smell leftover media-kit language. Bring delivery math or a sharp audience observation. The CTO is guarding reliability, security, and engineering time, so the ask should stay at "a technical working session or a written teardown, not a 'vision call'." If you copy a generic template and only swap the

What metric should I mention to a Media CTO?

Lead with CPM, fill, and campaign delivery against IO. That's the language this buyer already reports. If you can't connect your email to flights that stall, brand-safety scares, and follow-up that reads like leftover kit copy, you're asking them to do the translation work. They won't.

Do cold emails still work in 2026?

Yes, when they're specific. Generic sequences got crushed by filters and fatigue. Short emails that cite a real trigger and ask a real question still get replies. Volume without relevance just trains spam systems. Tie the note to one metric or stall they already own, and keep the ask answerable in a single sentence.

Media · CTO · After Demo

Cold Email Template for Media CTO: After Demo

A cold email is a first-touch message to someone who didn't ask for it, so relevance has to show up before the pitch does. For Media teams, the version that works for after a demo has to respect They can smell leftover media-kit language. Write to the CTO like they already have a full calendar and a reason to be

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

[Company Name] / CPM

Body

Hi [First Name],

Saw [trigger] and figured this might be on your plate.

In Media, that usually shows up as flights that stall, brand-safety scares, and follow-up that reads like leftover kit copy. Teams like [peer example] use [Your Product] to rescued two paused IOs by sending a delivery diagnosis instead of another one-pager in [timeframe]. The fit depends on whether flights that stall, brand-safety scares, and follow-up that reads like leftover kit copy is actually costing you CPM.

Replay the two moments they leaned in, and the one concern they named.

If I sent a 1-page sketch, would you glance at it?

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

Why this cold email works

Show you understand their bottleneck in their language.
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.
Replay the two moments they leaned in, and the one concern they named.
Lead with an observed trigger, not a compliment about their About page.

When should I send this to a Media CTO?

Don't follow a cold email the next morning. Give it 4 business days. Same day with the recap. A value bump 3 days later if they went quiet. For this combo, treat "Same day, then 3 days if silent" 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.

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. 90 words is plenty if the substance is real. Don't pad.

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. Upfronts and flight dates create urgency. Random Tuesdays don't. Don't promise a viral moment. Promise a clean flight.

Customization tips

Replace the pain line with a publisher whose advertiser follow-up still leads with 'unique storytelling'.
Keep the tone precise.
Send from a real name. Role accounts get filtered.
Time it for Same day, then 3 days if silent. Same day with the recap. A value bump 3 days later if they went quiet.
Don't promise a viral moment. Promise a clean flight.

Common mistakes

Opening with your company story is how cold email dies.
Don't send a 19-page deck that relitigates features they skipped.
Don't promise a viral moment. Promise a clean flight.
Calling it 'AI-powered' with no description of the system.

How this scenario compares

Dimension	For this template
Best send window	Same day, then 3 days if silent
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 after meeting	They have product context now. Speak to what they saw, not to a generic intro.
Unlike after proposal	Pricing may not be on paper yet. Don't jump to 'ready to sign.'

Questions people ask before they hit send

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.

Related templates

Want a custom draft instead? Try the email generator.