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.

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 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 Education referral request?

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

Referral Request for Education CTO: After Demo

A referral request email asks someone to make an intro by doing the work for them: who, why, and a forwardable blurb. For Education teams, the version that works for after a demo has to respect Don't sell during finals week. 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 referral request work for a Education CTO?

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

When should I send this to a Education 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 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. If your note would embarrass them in a team channel, rewrite it.

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. Proof that lands: got 1,200 faculty through a new workflow before census date. Proof that lands: got 1,200 faculty through a new workflow before census date. Proof that lands: got 1,200 faculty through a new workflow before census date.

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.
Never send a referral ask from a brand-new relationship.
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?

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

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.

I'm writing because a semester start, a grant window, or a failed LMS migration. Ideal person: [role] at a [company type] dealing with tools bought in spring that nobody trained on by fall. Not trying to spray this across your whole book.

Answer the real objection and make internal forwarding easy.

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