Should I break out implementation fees in the follow-up?

Yes if that line is the likely stall. CEOs will champion seats and still flinch at a 12-week implementation. Separate product from services in one sentence. Offer a phased start. Don't hide professional services in a footnote and hope they missed it.

Can I call the CEO when the proposal sits?

Only if they already take your calls. A voicemail that says circling back on the proposal is a chase. Stay in writing with a gate question. If they want a live review, they will propose a clock. Paper first. Voice second.

How do I involve the CFO without going around the CEO?

Ask the CEO who should get the 1-page cover. Don't email the CFO from a thread they aren't on. Permission is cheaper than a political mess. A CEO who wants the deal will make the intro. One who doesn't will say archive.

Is a 14-day paid pilot a downgrade of the proposal?

It's a smaller decision, not a downgrade. Many SaaS CEOs can say yes to a bounded test and cannot say yes to an annual. Put the pilot price and the success metric in the same sentence. Don't pretend the pilot is free if it isn't.

What belongs in the subject line of a proposal bump?

Version, company, and the word gate or review. Subjects that say following up disappear. File labels get searched. If you have a proposal ID, use it. The CEO's assistant may be the actual reader. Write for search, not for charm.

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

SaaS · CEO · After Proposal

Follow-Up Email After Sending a Proposal to a SaaS CEO

A proposal follow-up to a SaaS CEO isolates the stuck layer: price, a security packet, a board line, or a missing owner. Asking any thoughts on the proposal invites silence. They have been burned by vendors who over-promised time-to-value. Name the document version, list what is still open, and ask which gate is blocking a yes they may already want.

Copy-ready template

Subject

Proposal [Version] at [Company Name]: which gate?

Body

Hi [First Name],

Proposal [Version] from [Date] is still sitting on [Gate: price / SOC 2 / owner] unless I'm wrong. I won't bounce the same packet back.

Which layer is stuck at [Company Name]: scope, price, timing, or people? I can cut this to one team for 14 days and $ [Amount] so you have a thinner decision. If the packet should go to [CFO / CTO] instead, tell me who and I'll send a 1-page cover they can use.

[Your Name]
[Your Title]
[Your Company]

Why this follow-up works

The subject is a file label, not a hopeful bump.
Four gates let them answer in one word without a meeting.
A thinner 14-day start is a smaller commercial decision.
You refuse to resend the PDF, which is what every other vendor does.
Cover-note language helps them brief finance without extra work.

When should I send this to a SaaS CEO?

On the review date you set in the proposal email. If you didn't set one, five business days. Don't bump at 48 hours. If they said after the board, land the morning after that board if the date is public, not during. A second quiet gets one archive-or-later note. Do not weekly-drip a live proposal. That is how discounts get expected. If a security review is the named gate, ask for the questionnaire due date and put it on your calendar. Showing up early on a security gate reads as you don't understand SaaS buying.

What this CEO actually cares about

The CEO may want the yes and still not be the person who can move the file. Give them a paragraph they can forward. Direct, adult, light on process jargon. Talk like a peer who did the homework. Don't lecture them about urgency. Don't ask for a workshop to review a document they already have. Ask which layer is stuck. Then offer a thinner version. Their reputation is on the line if they champion a tool that dies in week three. Protect that. Price talk belongs in the open. Burying commercial facts to seem polite wastes this seat.

How SaaS changes the note

SaaS proposals die in layers the seller never sees: a CFO wants payback in 90 days, a CTO wants the questionnaire, a CEO wants one owner. Silence after a PDF is a process problem before it is a no. Tools that demo well and then eat implementation weeks made buyers cautious. Your follow-up has to be explicit about decision mechanics without sounding like collections. They don't owe you money yet. Offer to cut scope, split phases, or walk a second stakeholder through one page. If you get nothing after a breakup note, archive it. Endless bumps after a proposal train them to wait for a discount. Evaluation can close in two weeks for a point tool or drag a quarter when security is involved. Write for the slower machine unless they gave you a clock.

Customization tips

Use the real version number and date from the proposal footer.
If you quoted seats plus implementation, separate those lines in the email.
Don't add a surprise discount. Quiet isn't a negotiation opener.
If legal asked for a DPA, say whether that packet is already in their inbox.
CC only the person they named as commercial owner.

Common mistakes

Resending the PDF with just bumping this in the subject.
Adding a discount because they went quiet for a week.
Sounding like collections when they don't owe you yet.
Asking any thoughts, which is an essay prompt they will ignore.

How this scenario compares

Dimension	For this template
Best send window	The review date you set, else day 5
Ideal length	Under 90 words, four gates, one thinner option
Primary ask	Which gate is stuck, or cut to 14 days
Unlike an after-demo note	The commercial conversation has started
Unlike an invoice reminder	No money is due. Don't collect.

Questions people ask before they hit send

Assume a process problem before you assume a no. Ask which layer is stuck and offer a thinner version. If you get nothing after a breakup note, archive it. Endless bumps after a proposal train them to wait for a discount you shouldn't offer.

Related templates

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