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.

What if they go silent after receiving the proposal?

Assume a process problem before you assume a no. Ask which layer is stuck and offer a thinner version. If you get nothing after a breakup note, archive it. Endless bumps after a proposal train them to wait for a discount.

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.

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 resend the PDF with 'just bumping this.' 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 Proposal

Referral Request for Media CTO: After Proposal

A referral request email for a Media CTO (after a proposal) is a short message that reopens the thread without making them do extra work. A referral request email asks someone to make an intro by doing the work for them: who, why, and a forwardable blurb. In this setting, that means speaking to flights that stall, brand-safety scares, and

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?

Ask for a specific profile, not 'anyone in your network.'
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.
Offer to cut scope, split phases, or walk a second stakeholder through one page.
Give them cover to decline.

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. On the review date you set. If you didn't set one, five business days. For this combo, treat "5 business days, or the agreed 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.

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. Words that work: 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.

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.
Keep the ask to one person or one tightly defined role.
Time it for 5 business days, or the agreed date. On the review date you set. If you didn't set one, five business days.
Don't promise a viral moment. Promise a clean flight.

What mistakes should I avoid with this after proposal note?

Asking 'who do you know?' is lazy and gets no names.
Don't resend the PDF with 'just bumping this.'
Don't promise a viral moment. Promise a clean flight.
Calling it 'AI-powered' with no description of the system.

How does this after proposal scenario compare?

Dimension	For this template
Best send window	5 business days, or the agreed 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 after demo	The commercial conversation has started. Be explicit about decision mechanics.
Unlike invoice reminder	They don't owe you money yet. Don't sound like collections.

What should I copy and send?

Copy-ready template

Subject

Could you intro me to [role] at [Company]?

Body

Hi [First Name],

This is an ask. I tried to make it easy to say no.

In Media, that usually shows up as flights that stall, brand-safety scares, and follow-up that reads like leftover kit copy. Blurb you can paste: '[Your Name] helps [audience] with rescued two paused IOs by sending a delivery diagnosis instead of another one-pager. They asked if you'd be open to a short intro about [topic].'

Find the stuck layer and offer a smaller decision.

Thanks either way. I know intros cost you something.

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

Questions people ask before they hit send

Ask after you've given them a reason to want to help, not after the first coffee. On the review date you set. If you didn't set one, five business days. 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.