How do I introduce myself without sounding stiff?

Use one sentence for who you help and one sentence for why now. Skip the origin story. If a mutual is involved, put their name near the top so the email has a human reason to exist. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Should I include a recording in the demo follow-up?

If you recorded it and they agreed, yes, plus timestamps for the two parts they cared about. A raw 40-minute link with no map is homework. Add the three bullets they'd need to brief a colleague. 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 introduction 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 Education introduction?

Don't talk to educators like they're late to technology. They aren't. 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 Education inboxes and they all read as "this was templated."

When is the worst time to email an education buyer?

The two weeks around term start, finals, and major reporting deadlines. Your note isn't urgent to them. Aim for planning windows, and keep the ask small enough to survive a committee. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Education · CTO · After Demo

Introduction Email Template for Education CTO: After Demo

Use this introduction template when you're emailing a CTO in Education (after a demo). They saw the product. Now they're comparing, forwarding, or quietly deciding it wasn't for them. Keep the note aligned with Precise. No slogans. It's fine to be a little dry.

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 introduction work for a Education CTO?

Make it easy to decline.
Speaks to tools bought in spring that nobody trained on by fall 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 the overlap, not your résumé.

When should I send this to a Education CTO?

If a mutual offered the intro, send it while their permission is fresh. 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 purchasing often follows the academic year, not your quarter. 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 Education 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 Education changes the note

Education buyers are deans, district ops, and program leads working around calendars and committees. Don't sell during finals week. Don't ignore FERPA. Committees are real; a single champion can't always sign. A credible proof point in this vertical sounds like: got 1,200 faculty through a new workflow before census date. Watch the language. Words that land here include term, FERPA, SIS, LMS, cohort, professional development. Words that work: term, FERPA, SIS, LMS, cohort, professional development. A thread that ignores tools bought in spring that nobody trained on by fall reads like every other vendor bump.

How should I customize this template before I send it?

Replace the pain line with a university department that piloted software with three faculty and then stalled.
Keep the tone precise.
Don't attach your pitch deck to an intro.
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 talk to educators like they're late to technology. They aren't.

What mistakes should I avoid with this after demo note?

Giant bios make intros feel like homework.
Don't send a 19-page deck that relitigates features they skipped.
Don't talk to educators like they're late to technology. They aren't.
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	adoption by week four, attendance, and staff time saved
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

[Mutual] suggested I reach out about [topic]

Body

Hi [First Name],

[Mutual] thought we should talk because you're dealing with [pain] and I spend my week on [adjacent work].

The version of this that matters for deans, district ops, and program leads working around calendars and committees is got 1,200 faculty through a new workflow before census date. Happy to send a 5-line brief before any call so you know what you'd be walking into.

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

No pressure either way. I know unsolicited intros can be noise.

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

Questions people ask before they hit send

If a mutual offered the intro, send it while their permission is fresh. Same day with the recap. A value bump 3 days later if they went quiet. 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.