Should I lower the price in the follow-up?

Not as an opening move. Ask what's blocking the decision first. If budget is the issue, trim scope or phase the work. Discounting before you know the objection trains them to wait you out. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What should I say in a follow-up email after an interview?

Thank them for a specific part of the conversation, add one example you didn't get to, and restate interest in the actual work. Keep it under 150 words. Then stop. Daily pings after interviews read as panic, not enthusiasm. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Is it okay to send this proposal follow-up 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 proposal follow-up?

Don't promise a viral moment. Promise a clean flight. Calling it 'AI-powered' with no description of the system. Don't recap your whole résumé. They were in the room. 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 Interview

Proposal Follow-Up for Media CTO: After Interview

A proposal follow-up email helps a stalled decision move without pretending the document didn't land. For Media teams, the version that works for after an interview 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 cautious.

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 proposal follow-up work for a Media CTO?

Diagnose the stall instead of asking if they 'had a chance to review.'
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.
Reference a real moment from the conversation and connect it to how you'd do the work.
Name the decision owner out loud.

When should I send this to a Media CTO?

Wait until the review window you agreed on. If none was set, five business days. Within 24 hours. Same day is better. For this combo, treat "Within 24 hours" 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. If they named a board week or a freeze, believe it and leave a reopen date.

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. an incident class, a security gap, or a cost line they already hate

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.
Set a decision date in the original proposal so this email has a hook.
Time it for Within 24 hours. Within 24 hours. Same day is better.
Don't promise a viral moment. Promise a clean flight.

What mistakes should I avoid with this after interview note?

Asking 'any thoughts?' after a 12-page proposal invites silence.
Don't recap your whole résumé. They were in the room.
Don't promise a viral moment. Promise a clean flight.
Calling it 'AI-powered' with no description of the system.

How does this after interview scenario compare?

Dimension	For this template
Best send window	Within 24 hours
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 thank you	A thank-you is part of it. The rest should show you understood the role.
Unlike after meeting	The power dynamic is different. Don't 'check in on next steps' like a vendor chasing a PO.

What should I copy and send?

Copy-ready template

Subject

Need a decision owner for [scope]

Body

Hi [First Name],

I sent the proposal last [day] and wanted to make the review easier.

I'm writing because an RFP, a missed flight, or a new show / property launch. I left [optional module] as optional on purpose. We can ship [core] first and keep [nice-to-have] for later.

Reference a real moment from the conversation and connect it to how you'd do the work.

Want a 10-minute walkthrough for whoever else needs to see it?

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

Questions people ask before they hit send

Wait until the review window you agreed on. If none was set, five business days. Within 24 hours. Same day is better. 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.