Should I include a recording of the meeting?

Only if you recorded it and they agreed. A raw forty-minute link is homework. If you send it, timestamp the two moments they cared about, usually seats and the sandbox, especially around SKO and the recap. Better: a one-page recap they can forward. Recordings wait until someone who missed the room asks, especially around SKO and the recap.

What if CS was supposed to send activation numbers after the meeting?

Put that in the recap as their date, not your chase, especially around SKO and the recap. Offer to hold the next live step until the numbers Pinging CS yourself without permission can embarrass the VP. Warmth is waiting on the queue they named and writing the morning after, not the afternoon they promised, especially around SKO and the recap.

Can I attach the sandbox invite in the recap email?

If they asked for it in the room, yes, with the owner named. If they didn't, promise the one-pager first and send the invite after they confirm who should land in the workspace. Surprise sandboxes create CS tickets. Sales VPs notice who creates tickets.

How promotional can the recap itself be?

Almost none. They already sat with you. Flag the open question like a teammate. One defensible number, like unused seats, is plenty, especially around SKO and the recap. Proof decks wait until they ask. If the recap needs a hero image, you've already lost the forward to RevOps.

When should I bump if they don't confirm the recap?

Give it two business days, then one short line asking if an owner is wrong, especially around SKO and the recap. Don't restack the meeting. If they stay quiet, offer to archive until after QBR. Meeting recaps that become sequences teach VPs to stop taking vendor meetings in the first place.

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

SaaS · Sales VP · After Meeting

Follow-Up Email After a Meeting With a SaaS Sales VP

A post-meeting follow-up to a SaaS sales VP is a forwardable recap, not a second pitch. Write the same day. Name who owns the sandbox, which seats you discussed, and the CS question that stayed open. They should be able to drop your note into Slack without editing. Warmth lives in accuracy, not in how great it was to connect.

Copy-ready template

Subject

Sandbox owner, unused seats, and Thursday's CS note

Body

Hi [First Name],

Thank you for the time today. Capturing what I heard so you can forward it: [AE Pod] has unused seats, the sandbox still needs a CS owner, and you wanted activation numbers before the [QBR Date] review.

I'll send the one-page seat map by [Day]. If I missed an owner or a date, one correction is perfect. Happy to hold the live walkthrough until after that CS note lands.

[Your Name]
[Your Title]

Why this follow-up works

The subject is operational, so it survives a forward to RevOps or CS.
You recap their words, which proves you listened instead of running a sequence, especially around SKO and the recap.
You put the promise and the date in writing, which is how deals actually move.
Hold language on the walkthrough respects a CS queue they already named, especially around SKO and the recap.
No deck dump, so the note feels like a teammate, not a vendor afterglow, especially around SKO and the recap.

When should I send this to a SaaS Sales VP?

Send the same day, within a few hours. Next morning is the backup, not the plan. If you met on a Friday afternoon, a Monday 10:00 recap is kinder than a Friday 6:00 dump they will ignore, especially around SKO and the recap. Do not wait three days and then 'circle back.' That is a different email, and it should not pretend to be a recap. If they asked you to wait for a CS note, wait. Ping the morning after that date, not the afternoon they named, especially around SKO and the recap. One recap, then silence unless they reply. A second meeting-request the next morning trains them to dread your name, especially around SKO and the recap. Let the one-pager you promised do the work.

What this Sales VP actually cares about

This VP is already translating your meeting into a forecast risk for the CRO. They need cover. Your email is that cover if it is short, dated, and free of slogans, especially around SKO and the recap. They read it on a phone between a deal desk ping and a ramp complaint. The first two lines have to match the room. If you invent enthusiasm they didn't show, they will not forward it, especially around SKO and the recap. Don't CC their CEO. Don't add three AEs who weren't there. Don't convert a working session into a demo they didn't book, especially around SKO and the recap. Their credibility with the pod is the real product. Protect it. Then stop. A kind recap that asks for one correction is how you stay in the thread without becoming homework, especially around SKO and the recap.

How SaaS changes the note

SaaS meetings with a sales VP are rarely product tours. They are fights about unused seats, who owns activation, and whether CS will staff a sandbox before the next QBR. Your follow-up has to sound like the room you were in, especially around SKO and the recap. If you write a paragraph about how aligned everyone felt, you wasted the calendar, especially around SKO and the recap. A forwardable recap does more for the deal than a slide they didn't ask for. Quiet after a meeting is often a CS queue, not a snub, especially around SKO and the recap. They are waiting on activation numbers, a billing owner, or legal to open the trial workspace. Write as if that is already in motion. Name the date they said. Name the owner they hesitated on. Leave a correction cheaper than a second meeting. Warmth here is making them look precise in Slack. Feature lists make them look like they hosted a vendor, especially around SKO and the recap. They will not forgive that in a close week. If the meeting was intro-only, do not write a product recap they never saw, especially around SKO and the recap. Stick to seats, owners, and the open question.

Customization tips

Use their real pod, region, or segment name from the meeting.
If they named a CS lead, put that person in the recap, not a surprise CC, especially around SKO and the recap.
Attach nothing on the first recap. Link the one-pager after they confirm owners.
Send within three hours, or first thing next morning if you met after 4, especially around SKO and the recap.
If they asked for billing true-up math, put that in a second short paragraph, not a PDF.

Common mistakes

Sending a pitch deck they didn't ask for and calling it a recap.
Opening with how great it was to connect and no owners.
CCing the CRO to 'keep momentum' after a working session.
Forgetting the CS or sandbox owner they named in the room.

How this scenario compares

Dimension	For this template
Best send window	Same day within a few hours, Monday 10:00 if you met Friday late
Ideal length	Under 120 words, owners and dates first
Primary ask	Confirm owners, or one correction on the recap
Unlike an after-demo note	They may not have seen product. Don't write a feature recap.
Unlike a CEO meeting follow-up	Talk seats and CS owners, not NRR theater

Questions people ask before they hit send

Decisions, owners, dates, and anything you promised to send, especially around SKO and the recap. Keep opinions out unless they asked. A forwardable recap does more than paragraph about how great it was to connect, especially around SKO and the recap. Name unused seats and the CS question that stayed open. Then stop so they can drop it in Slack.

Related templates

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