Do I mention NRR or seats in the post-demo email?

Mention the number they used. If they talked tickets, don't switch to NRR to sound senior. If they talked time-to-first-value, don't switch to AI. Repeat their metric in their unit. Inventing a 3-point retention lift they didn't ask about is how you lose the room after they watched you.

How do I handle a demo that hit SSO or sandbox problems?

Name it in one line. Offer a 6-minute replay or a still of the screen they cared about. Don't pretend the demo was clean. They were there. Don't send a 30-minute encore as an apology. Fix the one workflow that failed. Then ask the same live-toil question you'd ask after a clean demo.

Who else on the SaaS team should see the follow-up?

Only people they named or who sat in. Surprise-adding a VP on demo day is pressure. If they said leadership has to see it, ask whether to send a 6-bullet forwardable or wait for their intro. Security only gets copied if they said the rollout needs IdP. Don't assume a stack from a logo.

What if they said they need VP sign-off after the demo?

Believe them. Ask if a 6-bullet version would help that conversation. Don't add the VP to CC unless they invite it. Hold the date they gave you. Don't drip during the wait. If the date passes by 3 business days, one check that names the VP gate is enough.

How many days until a second bump if the department head stays quiet?

Three business days after the recap, and only if you already sent the promised bullets. Don't bump during a named GA. If they stay quiet, one archive question is the cap. Teams remember vendors who nag through a launch week. Your name will come back on a slower Tuesday.

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

SaaS · Department Head · After Demo

Follow-Up Email After a Demo with a SaaS Department Head

A post-demo follow-up to a SaaS department head recaps the workflow they leaned in on, the toil number they named, and a next step that isn't a same-day close. It should sound like an implementation note, not a feature tour. They already gave you 25 minutes between a standup and a ticket pile.

Copy-ready template

Subject

After today's demo: [Workflow] tickets vs. [Metric]

Body

Hi [First Name],

You leaned in on the [Workflow] queue and you pushed back on anything that sounded like AI that runs itself. I'll stay in that lane.

I can send a 6-bullet version for [Workflow] and a separate note for [VP / Security / Team lead] if those are different owners. If the live calendar is the [GA / Freeze] set, tell me the date and I'll hold the thread.

Which of those two is the live toil this week at [Company Name]?

[Your Name]
[Your Title]

Why this follow-up works

It splits workflow and leadership so they don't have to educate you again.
You respected their allergy to magic-product scripts from the pitch deck.
Security and GA calendars are treated as real, not as objections to crush.
The ask is which toil is live, a question they can answer between standups.
No locking this rate energy in a software thread they just watched.

When should I send this to a SaaS Department Head?

Same day with the recap, after lunch or before 16:00, not at 19:00 during an incident. A value bump 3 business days later if they went quiet. Don't send the bump on GA morning unless they asked. If they said after security or after the VP meeting, put that date on the calendar and mean it. After the bump, one archive question is the ceiling. Daily drips are how SaaS inboxes learned to ignore vendors. If the company is in a launch they named, wait until the Tuesday after. Your clever Sunday note will sit under 80 vendor emails and a ticket list.

What this Department Head actually cares about

A department head is protecting service levels and a pile of tickets. They read email between a standup and a skip-level. The first two lines have to be a workflow they recognize. Asking how they liked the demo is how you get ignored. They'll spend 8 seconds deciding if you create work for a team that's already covering the last vendor. Show the number, name two possible owners, then stop. Don't CC the VP to apply heat on demo day. Don't joke about their stack. Be exact. Wrong workflow names are a professional insult on a busy day. If your note would look silly pasted into a leadership Slack, rewrite it. They live in 15-minute blocks. Respect the block.

How SaaS changes the note

SaaS department heads have watched too many demos that ignored implementation. Unsold activation, a CS queue that still pages people, and an IdP review that parks the project are the classic holes. Time-to-first-value, seat waste, and ticket volume are the numbers. A team whose last tool demoed well and died in week three already knows the pattern. Your recap should help them sell the change internally without sounding like a seminar. Quiet after a demo often means they have to catch a VP between 10:00 and 11:00, or they're in a Sev thread at 16:30. Don't fill that with a second feature tour. Recap the workflow. Ask which toil is live. If you only talk product experience, they'll assume you've never sat through a go-live.

Customization tips

If the demo was CS, name the queue. If it was onboarding, name the day-14 drop.
If SSO failed in the sandbox, acknowledge it in one line and offer a 6-minute replay.
Don't quote NRR as a weapon.
Don't CC a VP to pressure a department head on demo day.
Timestamps on the recording beat a raw 40-minute link.

Common mistakes

Fake urgency about this quarter when you're the vendor, not the on-call.
Relitigating features they skipped on a small laptop screen.
Sending a 19-page deck as the recap.
Talking to a multi-product lead like a single-feature closer.

How this scenario compares

Dimension	For this template
Best send window	Same day after lunch, then 3 days if silent
Ideal length	Under 110 words plus optional bullets
Primary ask	Workflow leak or leadership leak this week?
Unlike a meeting-only recap	They saw the product. Speak to the workflow they watched.
Unlike an after-proposal note	Pricing may not be on paper. Don't jump to ready to sign.

Questions people ask before they hit send

Same day, after lunch or before 16:00. Avoid 19:00 incident hours and GA morning. Waiting two days makes the recap feel optional. They already have a VP walk and a ticket hole. Write while the workflow is still in their head. Then send the 6 bullets you promised.

Related templates

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