SaaS · Sales VP · After Demo
Proposal Follow-Up for SaaS Sales VP: After Demo
Use this proposal follow-up template when you're emailing a Sales VP in SaaS (after a demo). They saw the product. Now they're comparing, forwarding, or quietly deciding it wasn't for them. Keep the note aligned with Crisp and commercial. They can handle a direct ask.
Last updated: 2026-09-02 · Reviewed by: Sales Email Template editors
We write templates the way we wrote emails on quota: short, specific, and easy to forward. When we cite research below, it is because the number changes how a buyer reads your note, not to pad the page.
Sources: HubSpot sales email benchmarks; Gong follow-up research
Why does this proposal follow-up work for a SaaS Sales VP?
- Give them a clean no so they don't ghost out of politeness.
- Speaks to time-to-value that slips past the first 14 days and quietly becomes churn instead of a generic "value prop."
- Fits how a sales VP actually reads: 70 to 90 words. Lead with the outcome.
- Replay the two moments they leaned in, and the one concern they named.
- Offer a smaller package so budget isn't a binary wall.
When should I send this to a SaaS Sales VP?
Wait until the review window you agreed on. If none was set, five business days. 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 evaluation can close in two weeks for a point tool or drag a quarter when security is involved. If you're emailing a sales VP, 70 to 90 words. Lead with the outcome.
What this Sales VP actually cares about
A sales VP in SaaS is protecting quota, forecast credibility, and rep time. They think in pipeline, ramp, and forecast risk. If you can't map your email to a number they already report, it feels like a hobby. The hook that earns a look is a stage in the funnel that's leaking, a slow follow-up SLA, or a ramp problem. The ask should stay at this size: a 15-minute look at one metric, not a platform tour. Delete trigger: Telling them how to sell. They've heard it. If your note would embarrass them in a team channel, rewrite it.
How SaaS changes the note
SaaS buyers are software teams juggling seat growth, churn, and a stack that's already too loud. They've been burned by tools that demo well and then die in implementation. Lead with integration and time-to-value, not feature lists. A credible proof point in this vertical sounds like: cut onboarding from 19 days to 6 for a 40-person customer success team. Watch the language. Words that land here include activation, seats, SSO, sandbox, expansion, churn. Buyers here measure success with net revenue retention, time-to-first-value, and expansion inside existing accounts. Buyers here measure success with net revenue retention, time-to-first-value, and expansion inside existing accounts.
How should I customize this template before I send it?
- Replace the pain line with a B2B SaaS company adding usage-based billing on top of a messy seat model.
- Keep the tone crisp and commercial.
- Quote the exact option names from the proposal so they don't reopen the PDF.
- 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 promise 'AI that runs itself.' They hear that weekly.
What mistakes should I avoid with this after demo note?
- Asking 'any thoughts?' after a 12-page proposal invites silence.
- Don't send a 19-page deck that relitigates features they skipped.
- Don't promise 'AI that runs itself.' They hear that weekly.
- Telling them how to sell. They've heard it.
How does this after demo scenario compare?
| Dimension | For this template |
|---|---|
| Best send window | Same day, then 3 days if silent |
| Ideal length | 70 to 90 words. Lead with the outcome. |
| Primary ask | a 15-minute look at one metric, not a platform tour |
| Industry metric to cite | net revenue retention, time-to-first-value, and expansion inside existing accounts |
| Tone | Crisp and commercial. They can handle a direct ask. |
| Unlike after meeting | They have product context now. Speak to what they saw, not to a generic intro. |
| Unlike after proposal | Pricing may not be on paper yet. Don't jump to 'ready to sign.' |
What should I copy and send?
Copy-ready template
Subject
SaaS note on time-to-value that slips past the first 14 days
Body
Hi [First Name], I sent the proposal last [day] and wanted to make the review easier. In SaaS, that usually shows up as time-to-value that slips past the first 14 days and quietly becomes churn. Most delays I see are one of four things: scope, price, timing, or who has to sign. Tell me which one and I'll rewrite that section today. Given this is after a demo, ask who else needs to see it, or whether a narrower use case is the better start. Which piece is actually blocking a yes or no? Best, [Your Name] [Your Title] [Your Company]
Questions people ask before they hit send
Show a leak they recognize: slow follow-up, weak stage conversion, messy handoffs. Ask for a short look at that one number. Don't pitch a philosophy of selling. They already have one, and their forecast is louder than your sequence. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.
Related templates
Want a custom draft instead? Try the email generator.