What if they only cared about one workflow?

Cut the recap to that workflow. Offer a narrower start: one team, 14 days, one success metric. Expanding scope in the follow-up is how demos die. They can always add seats later. They cannot unread a bloated recap. That's the working rule here.

Do I put pricing in the same-day recap?

Only if they asked for it live. Otherwise offer to send a one-line commercial range when they want it. Surprise list prices in a recap feel like a close. CEOs punish that. Let them ask. Then be exact. That's the working rule here.

How do I handle a security objection from the demo?

Put it in writing in the recap and attach the packet they asked for, labeled. Don't argue that security is easy. Don't claim certifications you don't have. The CEO is often carrying that objection for a CTO. Help them carry it cleanly.

Should the AE and the SE both email?

One recap from the person who ran the room. The SE can send a technical addendum if the CEO asked a stack question. Two competing recaps confuse the forward. Pick an owner. Put their name on the promise. That's the working rule here.

What if the CEO left 20 minutes early?

Recap only what they saw. Don't pretend they watched the rest. Offer the timestamps for the missed part as optional. Writing as if they sat through a full tour they skipped is how you lose trust in one email. That's the working rule here.

Last updated 2026-09-02 · Reviewed by Sales Email Template editors

SaaS · CEO · After Demo

Follow-Up Email After a Demo with a SaaS CEO

A post-demo follow-up to a SaaS CEO should replay the two screens they leaned on, the stall they named, and a next step that isn't a same-week close. They already saw the product. Your note is a briefing they can forward to a CFO or CTO. Skip the feature dump they skipped live. Answer the objection. Then stop.

Copy-ready template

Subject

Two screens from today's [Company Name] demo

Body

Hi [First Name],

You leaned in at [Moment 1: unused-seat view / day-14 chart] and at [Moment 2]. You also named [Stall: SOC 2 / payback / who implements] as the reason this dies internally at [Company Name].

I'll send a 1-page board brief with clocks at [Time 1] and [Time 2] on the recording. Who else needs that page before you decide: [CFO], [CTO], or neither yet? If a one-team, 14-day start is cleaner, say cut and I'll shrink it.

[Your Name]
[Your Title]

Why this follow-up works

It proves you watched them, not your own demo script.
The stall is their language, which they can paste into Slack.
Timestamps turn a 40-minute recording into an 8-minute brief.
A narrower start is an easy yes that still respects budget risk.
You don't jump to ready to sign after a first look.

When should I send this to a SaaS CEO?

Same day with the recap. If you demoed at 16:00, still send before you leave the desk. A value bump 3 days later if they went quiet, with one new proof point, not a restack. Don't send the bump during their product launch week. If they asked for a security packet, send that on the clock you promised and don't mix it with a sales bump. After the day-3 note, one archive question at day 10. Four emails after a demo is how you become a story. They already paid with an hour. Earn the next hour with paper.

What this CEO actually cares about

They sat through the screens. Don't thank them for 12 sentences. Brief them. A CEO needs cover to say yes and a way to not look reckless. Give them a paragraph a CFO could understand without a briefing. That's often the real audience even when their name is on the To line. Don't tell them how to sell their own product. Don't replay features they skipped. If they looked bored at the AI slide, leave it out of the recap. Precision is respect in this seat. The next step should be who else needs the brief, or a thinner use case, not a calendar ambush.

How SaaS changes the note

SaaS demos are theater until someone writes down what actually mattered. CEOs compare you to a stack that already exists and to a graveyard of tools that looked fine in a browser and then created ticket load. Your follow-up has to speak to what they saw, not to a generic intro. Time-to-first-value, who implements, and whether this shows up as a line the board will question are the objects. Pricing may not be on paper yet. Don't jump to signature language. If they went quiet after the demo, they are probably forwarding internally or deciding it wasn't for them. Help the forward. Don't punish the silence with a second tour.

Customization tips

Use the labels on their screen, not your marketing names.
If they asked about SSO, put SSO in line two, not in a P.S.
Don't attach a 19-page deck that relitigates features they skipped.
Offer a sandbox login only if they asked during the demo.
If legal was on the call, send the DPA link labeled, not buried.

Common mistakes

Sending a 19-page deck that relitigates skipped features.
Writing as if they already agreed to a rollout.
Dropping a contract in the same email as the recap.
Thanking them for their time for three paragraphs.

How this scenario compares

Dimension	For this template
Best send window	Same day recap, day-3 bump if silent
Ideal length	Under 110 words plus optional timestamps
Primary ask	Who else needs the 1-page brief
Unlike an after-meeting note	They have product context. Speak to screens.
Unlike an after-proposal note	Money may not be on paper. Don't collect.

Questions people ask before they hit send

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. CEOs will forward bullets. They will not assign a movie.

Related templates

Want a custom draft instead? Try the email generator. Word count on this page: 1031.