How many times should I follow up with a CTO (long time no contact)?

Send it the same day. Thanks that arrive a week later feel like a task. Send when you have a real trigger: news, a useful artifact, a role change, a season. 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.

How soon should I send a thank-you after a meeting?

Same day, ideally within a few hours. Waiting until the next morning is fine if the meeting ran late. Waiting until Friday for a Monday meeting makes it look like a chore. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Is it weird to email someone after six months of silence?

Not if you have a new reason and you don't pretend the old thread is still warm. Lead with the trigger, remind them who you are in one line, and make the ask optional. Nostalgia without news is just another cold email with extra steps.

Is it okay to send this thank you 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 thank you?

Don't promise a viral moment. Promise a clean flight. Calling it 'AI-powered' with no description of the system. Don't open with 'it's been a while' and then paste the old pitch. Those three mistakes show up constantly in Media inboxes and they all read as "this was templated."

Media · CTO · Long Time No Contact

Thank You Email Template for Media CTO: Long Time No Contact

A thank-you email names the specific thing someone did and, when it's natural, points to one next step without turning gratitude into a pitch. For Media teams, the version that works for long time no contact 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

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 thank you work for a Media CTO?

Separate thanks from selling. If you must include a next step, keep it optional.
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.
Bring a new observation about their world, then offer a small, optional next step.
Name the exact help they gave so it doesn't sound templated.

When should I send this to a Media CTO?

Send it the same day. Thanks that arrive a week later feel like a task. Send when you have a real trigger: news, a useful artifact, a role change, a season. For this combo, treat "Only when you have a trigger" 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. If your note would embarrass them in a team channel, rewrite it.

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.
Handwritten notes still stand out for in-person meetings.
Time it for Only when you have a trigger. Send when you have a real trigger: news, a useful artifact, a role change, a season.
Don't promise a viral moment. Promise a clean flight.

What mistakes should I avoid with this long time no contact note?

A generic 'thanks for your time' is forgettable.
Don't open with 'it's been a while' and then paste the old pitch.
Don't promise a viral moment. Promise a clean flight.
Calling it 'AI-powered' with no description of the system.

How does this long time no contact scenario compare?

Dimension	For this template
Best send window	Only when you have a trigger
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 no response	This isn't a 4-day bump. It's a re-introduction with a new reason.
Unlike breakup	You're opening a door, not closing one. Still keep it easy to ignore.

What should I copy and send?

Copy-ready template

Subject

Appreciate you making time for [topic]

Body

Hi [First Name],

I appreciated how direct you were about [topic] today.

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. No need to reply. I just wanted this on the record.

Given this is long time no contact, ask if the old problem still exists, or if you should leave it archived.

If I can return the favor, say the word.

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

Questions people ask before they hit send

Name the situation and the business object, not your excitement. Something like "Appreciate you making time for [topic]" outperforms "Just checking in" because a CTO can decide from the preview text whether it's worth opening. Keep it under 50 characters when you can.

Related templates

Want a custom draft instead? Try the email generator.