What should I never say in a Media referral request?

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. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

How should a referral request 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.

When is it okay to ask for a referral?

After you've created value or at least a real relationship. Right after a first meeting is usually too soon unless they offered. A good test: would they be slightly proud to put you in front of a peer? Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Media · CTO · After Demo

Referral Request Email Template for Media CTO: After Demo

When a Media CTO goes quiet (after a demo), the right referral request email does one job: make a reply cheaper than silence. 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. That's why this template leads with CPM, fill, and campaign delivery against

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 Media CTO?

Include a forwardable paragraph.
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.
Explain why they'd look good for making the intro.

When should I send this to a Media CTO?

Ask after you've given them a reason to want to help, not after the first coffee. 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. Tone: Precise. No slogans. It's fine to be a little dry.

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. Buyers here measure success with CPM, fill, and campaign delivery against IO. Buyers here measure success with CPM, fill, and campaign delivery against IO. Proof that lands: rescued two paused IOs by sending a delivery diagnosis instead of another one-pager.

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.
Don't attach a commission offer unless that's already your model.
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.

What mistakes should I avoid with this after demo note?

Asking 'who do you know?' is lazy and gets no names.
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 does this after demo scenario compare?

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.'

What should I copy and send?

Copy-ready template

Subject

CTO question on after demo

Body

Hi [First Name],

If you're willing, I wrote a blurb you can forward as-is.

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. If now is a bad time, don't spend political capital on this.

Given this is after a demo, ask who else needs to see it, or whether a narrower use case is the better start.

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

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

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. 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.