What if they asked when the sandbox starts billing?

Put the rule in one sentence in the recap: what counts as a billable seat, when unused licenses still bill, and who can freeze expansion. Don't attach a full order form unless they asked. Procurement forwards simple billing rules. They delete quote PDFs that look like a close.

Is a smaller seat start a real next step or a stall?

It's a real next step if legal can own the trial terms. A fat exhibit is what dies in the portal. Offer the thin start as the default, not as a consolation prize, especially around the vendor freeze and the workspace walkthrough. If they wanted the whole seat count in, they'll say so. Warmth is making a yes survive true-up.

How do I mention unused licenses without dunking on their last buy?

Talk about dark seats as a cost they already feel, not as proof they bought badly. You can name a class of waste without roasting the vendors they already own. Officers notice when you mock last year's purchase. Stay on their side of the exhibit.

Should the business owner be on the recap?

Not unless they were in the demo. Surprise-adding a VP turns a working recap into politics, especially around the vendor freeze and the workspace walkthrough. If procurement wants cover, they will forward your note. Write it so that's easy. That's the job. Stay off the CC line until you're invited onto it.

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

SaaS · Procurement Officer · After Demo

Follow-Up Email After a Demo With a SaaS Procurement Officer

Q: When should I send the three-day bump?

On the morning of the third business day if they haven't replied to the recap, especially around the vendor freeze and the workspace walkthrough. Answer the open especially around the vendor freeze and the workspace walkthrough. That's a scold. One new fact, then an archive option if they still need time, especially around the vendor freeze and the workspace walkthrough.

A post-demo follow-up to a SaaS procurement officer replays the two commercial moments they leaned in and the one concern they named. Send it the same day. Don't relitigate features they skipped. Seat counts, when billing starts on a sandbox, and who owns unused licenses are the language. Make forwarding easy. Warmth is remembering the exhibit they actually asked for.

Copy-ready template

Subject

Demo recap: seats, sandbox billing start, unused licenses

Body

Hello [First Name],

Thank you for going through the workspace today. You lingered on seat count and asked when a sandbox starts billing if it isn't fully activated before [Freeze Date].

I'm sending a one-page commercial recap with those two timestamps. If it's easier to start at [Smaller Seat Count] instead of the full exhibit, say so. Happy to hold until legal names an owner for the trial terms.

[Your Name]
[Your Title]

Why this follow-up works

The subject matches the demo they sat through, so it forwards cleanly to legal.
You name the lean-in moment, which proves you watched them, not your script, especially around the vendor freeze and the workspace walkthrough.
A thinner seat count respects the unused-license fear they actually voiced.
Hold language makes a pause cheaper than ghosting the recap, especially around the vendor freeze and the workspace walkthrough.
No feature dump, so it doesn't look like the deck they already survived, especially around the vendor freeze and the workspace walkthrough.

When should I send this to a SaaS Procurement Officer?

Send the recap the same day. A value bump three business days later is allowed if they went quiet, and it should answer the billing-start or seat question, not restack the demo. Do not bump the next morning. They haven't had time to ask legal. If they named a freeze, write the morning after that date. Avoid RFx-week Fridays. If the recording failed, say so in one line and still send the one-pager, especially around the vendor freeze and the workspace walkthrough. Silence plus a mystery link is worse than a short recap, especially around the vendor freeze and the workspace walkthrough. After the bump, the next touch is archive-or-later, not a third tour of the same sandbox, especially around the vendor freeze and the workspace walkthrough.

What this Procurement Officer actually cares about

This officer is already imagining legal complaining that another tool landed without a clean exhibit. The recap has to protect them. Put seat counts and billing start in writing. They read on a phone between portal queues. The first two lines have to match the live session, especially around the vendor freeze and the workspace walkthrough. Don't CC the business owner as momentum. Don't send a clip reel of features they skipped. Don't convert curiosity about unused licenses into a hard close. Policy is the product. Protect it. Then stop. A kind offer to hold until legal names an owner is how you stay useful without becoming a second meeting they didn't book.

How SaaS changes the note

SaaS demos for procurement are evaluations of commercial risk, not theater. They are asking whether a sandbox starts billing, whether unused seats still count, and whether the exhibit will survive legal. Your follow-up has to sound like you noticed where they leaned in, especially around the vendor freeze and the workspace walkthrough. If you recap every module, you tell them you weren't listening, especially around the vendor freeze and the workspace walkthrough. Quiet after a demo is often a legal question they now have to ask internally. They are not ignoring you. They are finding out who would own the trial terms. Write as if that conversation is already happening, especially around the vendor freeze and the workspace walkthrough. Offer a smaller seat start if the full exhibit felt heavy. Offer to hold if they said legal is slammed. Warmth is reducing the blast radius of a yes. Feature catalogs increase it. Vendors that demoed well and then surprised finance at true-up trained this inbox to flinch. Your recap should make internal forwarding easy, not make them defend a forty-minute recording to a VP who wasn't there, especially around the vendor freeze and the workspace walkthrough.

Customization tips

Use the real seat number and the exact billing-start question from the call.
Timestamp only the two moments they cared about, usually seats and the exhibit.
If finance joined, add one line on unused licenses, not a full quote.
Offer the thinner start as the default, not a discount trick.
Send within two hours while the recording is still processing, not the next week, especially around the vendor freeze and the workspace walkthrough.

Common mistakes

Relitigating features they skipped in a nineteen-page deck.
Opening with how exciting the demo was and no timestamps.
Asking them to pick a forty-five minute next step as the only CTA.
Ignoring the billing-start question they asked live.

How this scenario compares

Dimension	For this template
Best send window	Same day recap, then a three-day bump if silent
Ideal length	Under 110 words, two moments plus one concern
Primary ask	Thinner seat start, legal owner, or hold
Unlike an after-meeting note	They have product context now. Speak to commercial what they saw.
Unlike an after-proposal note	A full quote may not be on paper. Don't jump to ready to sign.

Questions people ask before they hit send

If you recorded it and they agreed, yes, plus timestamps for seats and billing start. A raw forty-minute link with no map is homework. Add the three bullets they'd need to brief legal. If they declined recording, the one-pager is enough and warmer than a surprise file, especially around the vendor freeze and the workspace walkthrough.

Related templates

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