Follow-Up Email Template for Education CEO: After Demo

Why does this follow-up work for a Education CEO?

• Swap a meeting ask for a smaller yes when they went quiet.
• Speaks to tools bought in spring that nobody trained on by fall instead of a generic "value prop."
• Fits how a CEO actually reads: Keep the whole note under 70 words unless they asked for detail.
• Replay the two moments they leaned in, and the one concern they named.
• Restate the original reason in one line so they don't hunt the thread.

When should I send this to a Education CEO?

Give it 3 to 5 business days after the last note before you ping again. 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 CEO, Keep the whole note under 70 words unless they asked for detail.

What this CEO actually cares about

A CEO in Education is protecting time, reputation, and optionality. They skim on a phone between meetings. If the first two lines don't name a business outcome, the rest never gets read. The hook that earns a look is a P&L, risk, or competitive issue they already feel. The ask should stay at this size: one decision or a 10-minute yes, not a workshop. Delete trigger: A long origin story or a request to 'pick your brain.' If your note would embarrass them in a team channel, rewrite it. They protect time, reputation, and optionality, so keep the ask at "one decision or a 10-minute yes, not a workshop."

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. A thread that ignores tools bought in spring that nobody trained on by fall reads like every other vendor bump. Purchasing often follows the academic year, not your quarter. 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 direct, adult, light on process jargon.
• Change the subject if the original thread looks dead in their inbox.
• 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?

• The fastest way to get ignored is stacking three asks into one nudge.
• 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.
• A long origin story or a request to 'pick your brain.'

How does this after demo scenario compare?

Questions people ask before they hit send