Last updated 2026-09-02 · Reviewed by Sales Email Template editors
SaaS · Sales VP · After Proposal
Follow-Up Email After a Proposal to a SaaS Sales VP
A follow-up after a proposal to a SaaS sales VP should find the stuck layer and offer a smaller decision. Don't resend the PDF. Silence here is usually seats versus AE headcount, a billing true-up they haven't explained, or CS who won't staff the sandbox. Stay commercial and calm. Warmth is cutting scope, not chasing a signature.
Copy-ready template
Subject
Proposal: cut seats, or wait on CS staffing?
Body
Hi [First Name], I won't resend the PDF. After [Proposal Date], quiet in a SaaS sales org usually means unused seats don't match the quote, billing wants a true-up rule, or CS hasn't agreed to staff the sandbox. Would a thinner version at [Smaller Seat Count] help, or should I hold until after [QBR / Cutover]? Happy to walk RevOps through one page if that's the layer. [Your Name] [Your Title]
Why this follow-up works
- The subject names two real commercial stalls, so it isn't a vague bump, especially around SKO and the quote.
- You refuse to resend the PDF, which is the move they already learned to ignore, especially around SKO and the quote.
- A thinner seat count is a decision they can take without a CRO meeting.
- Hold language respects a CS or billing queue they may not want to admit, especially around SKO and the quote.
- Calm tone keeps you in partner mode instead of discount theater, especially around SKO and the quote.
When should I send this to a SaaS Sales VP?
Write on the review date you set together. If you never set one, five business days after they received the document, especially around SKO and the quote. Do not bump the next morning. They haven't taken it to RevOps yet. If they named a QBR or a billing cutover, wait until the morning after. After this note, the next touch is archive-or-later, not a second PDF, especially around SKO and the quote. Endless bumps after a proposal train them to wait for a discount, especially around SKO and the quote. If they ask for a thinner version, send it within one business day and stop, especially around SKO and the quote. Avoid close-week Fridays. A Tuesday morning commercial question is more likely to get a layer named out loud, especially around SKO and the quote.
What this Sales VP actually cares about
This VP has to defend the seat count in a forecast packet. If your quote is fatter than the pod they can activate, they will go quiet rather than argue with you. Help them. Put a thinner number in writing. They read between a slipped deal and a finance ping about unused licenses they already own. The first two lines have to name the commercial fork, especially around SKO and the quote. Don't CC the CRO to force a decision. Don't joke about legal. Don't convert silence into a limited-time offer. Their credibility is the product. Protect it. Then stop. A kind offer to cut seats or wait on CS is how proposals actually move in SaaS.
How SaaS changes the note
SaaS proposals stall in boring places. Unused seats don't match AE headcount. Billing wants to know whether dark licenses still bill at true-up. CS will not staff a sandbox the quote assumed was free. Your follow-up has to sound like you have been in those fights, not like you are waiting for a signature, especially around SKO and the quote. Resending the PDF trains them to wait for a discount, especially around SKO and the quote. Asking which layer is stuck is adult. Offer to cut seats. Offer to phase activation. Offer to hold until after QBR. Warmth is making a smaller yes possible without making them look reckless to the CRO. Quiet after a proposal is a process problem before it is a no, especially around SKO and the quote. Assume that. Write to the stuck layer. If you cannot name seats, billing, or CS, you are guessing at personality, and this inbox will feel it. Commercial calm is the whole product in this thread, especially around SKO and the quote.
Customization tips
- Put the real seat count from the quote, then the thinner alternative, especially around SKO and the quote.
- If they asked for monthly instead of annual, offer that in one line, not a new deck, especially around SKO and the quote.
- Name RevOps or CS only if they were in the proposal thread.
- Don't add a surprise discount. Ask which layer is stuck first.
- Send on the date you promised in the proposal email, not three days early, especially around SKO and the quote.
Common mistakes
- Resending the same PDF with just bumping this in the subject.
- Dropping an unsolicited discount that makes them look like they stalled for price.
- Sounding like collections before a PO exists.
- Ignoring CS staffing as if activation were free.
How this scenario compares
| Dimension | For this template |
|---|---|
| Best send window | The review date you set, or five business days |
| Ideal length | Under 100 words, one commercial fork |
| Primary ask | Thinner seat count, hold, or RevOps one-pager |
| Unlike an after-demo note | The commercial conversation has started. Be explicit. |
| Unlike an invoice reminder | They don't owe you money yet. Don't sound like AP. |
Questions people ask before they hit send
Assume a process problem before you assume a no. Ask which layer is stuck: seats, billing, timing, or CS. Offer a thinner version. If you get nothing a breakup note, archive it, especially around SKO and the quote. Endless bumps after a proposal train them to wait for a discount they didn't ask for, especially around SKO and the quote.
Related templates
Want a custom draft instead? Try the email generator. Word count on this page: 1254.