When to use these proposal follow-ups
A proposal follow-up should move the buyer from reading to internal decision. The proposal bundles scope, method, team, price, terms, timing, and risk. The follow-up has to name which part is blocking approval.
A strong follow-up treats the proposal as a decision aid. It helps the buyer explain the tradeoffs to everyone who wasn't in the room.
Use these after sending a proposal, clarifying scope, equipping a champion, naming timing impact, or closing a quiet thread. If the conversation is mainly about a specific number, use the quote follow-up templates or pricing follow-up templates.
Five ways proposal follow-ups fail
Most proposal follow-ups go wrong because the writer reacts to time passed rather than the actual approval problem.
- Restating the proposal: The email says the proposal was sent and asks for thoughts. The buyer already knows that. Name the decision the proposal asks them to make.
- Treating the champion like the signer: Your contact may understand the proposal and still need to sell it internally. Give them a forwardable summary with the business case, tradeoff, timing impact, and decision needed so they don't have to rewrite your proposal for the budget owner, legal reviewer, or implementation owner.
- Reacting to the wrong objection: If the buyer asked about scope, defending price changes the subject. If they flagged timing, walking through package differences misses the block. The last buyer signal should set the subject of the next email.
- Generic silence touches: A quiet proposal thread needs a useful new artifact, a timing reset, or a close-the-file note.
- Timing pressure without calendar weight: Soon isn't a business reason. A timing email needs a visible mechanic: procurement review, implementation lead time, vendor window, fiscal cutoff, or capacity hold.
Which template to send
Pick by what the next email has to carry.
- The buyer has had time to read it: Use the sent proposal follow-up.
- They asked what's in or out: Use the scope question follow-up.
- Your contact needs internal approval: Use the forwardable decision summary.
- A milestone depends on sign-off: Use the timing pressure follow-up.
- The thread went quiet after useful touches: Use the no-reply proposal follow-up.
Sent proposal follow-up
Send this once the buyer has had the proposal long enough to read it and the thread has stalled on the decision, not the document.
Decision on [project]
Hi [Name],
On the [project] proposal, the decision in front of you is [specific decision, e.g., phased rollout versus full implementation].
[One sentence reacting to the last thing the buyer said in the thread.]
I can walk through it [today at 3:30] or [tomorrow at 10].
Best,
[Your Name]
If you can't name the decision in one sentence, the proposal is probably asking for too many decisions at once. Split the follow-up around the first decision only.
Avoid 'wanted to follow up on the proposal' as line 1. The buyer knows you sent it.
Scope question follow-up
A scope question means the buyer is unsure what your proposal includes, excludes, or phases later. Gartner's sense-making research found buyers are often overwhelmed by high-quality but conflicting information. Use the reply to reduce the sorting work by answering the scope question and recommending the path that best matches the priority they named.
Use this when the buyer is unsure what the proposal includes, excludes, or phases later.
Scope answer for [project]
Hi [Name],
[included item] is included in this proposal, and [excluded item] is a separate phase later on.
For [the buyer's stated priority], I recommend [recommended path]. [Alternative path] still works if [specific reason to delay the broader scope].
I can send the revised version by [day].
Best,
[Your Name]
Anchor the recommendation in something they said. 'You said East region go-live matters most' beats 'this is the leaner option.'
Avoid framing scope as a neutral menu when the buyer asked for guidance. Give the recommendation first.
Forwardable decision summary
Your contact forwards the summary when other stakeholders need to validate the decision or build consensus. Gartner's B2B buying journey research describes validation and consensus creation as two buying jobs buyers revisit throughout a non-linear purchase. Build the summary around those two jobs. For validation, show the evidence behind the recommendation and the cost of waiting. For consensus, explain the recommended approach, the tradeoff, and the alternative you ruled out.
Use this when your contact needs to forward the proposal to someone who was not in the meetings.
Summary for the decision maker
Hi [Name],
The [Project] proposal comes to [$X] for [scope], delivered by [date]. Here's what [stakeholder] needs to decide:
- What we're solving: [problem in the buyer's words].
- Recommended approach: [scope] because [constraint that drove the recommendation].
- Alternative we ruled out: [alternative] because [reason].
- Investment: [$X], [payment schedule].
- Timing: [milestone] by [date], assuming sign-off by [decision date].
- Risk of waiting: [concrete thing that gets harder if the decision slips].
If a call would help, I can walk the approval group through the tradeoffs.
I have 20 minutes open [day at 10:30] or [day at 2].
Best,
[Your Name]
Write for someone who was not in the room. They usually want to know why this approach over the alternative before they weigh the price.
Avoid restating the proposal line by line. The proposal carries detail; this email carries buying logic.
Timing pressure follow-up
Use this when timing matters and the buyer needs to understand the practical effect of waiting.
[Milestone] timing on the proposal
Hi [Name],
To deliver [milestone] on the [project] proposal by [target date], I'll need your go-ahead by [decision date] because [calendar mechanic, e.g., procurement review is 10 business days and implementation needs three weeks].
After [decision date], the next realistic [milestone] window is [later date] because [specific constraint].
I can walk through the timing [tomorrow at 2] or [Thursday at 11].
Best,
[Your Name]
Tie timing to a calendar mechanic the buyer can verify, like procurement cycle length or implementation lead time.
Avoid urgency built around your start date. The buyer cares about their milestone.
No-reply proposal follow-up
A quiet proposal thread is usually a stall, not a rejection. Forrester's 2024 State of Business Buying found 86% of B2B purchases stall during the buying process, so treat silence as a blocked approval to diagnose rather than a lost deal.
Use this after two useful touches with no new buyer signal.
Closing the [project] proposal
Hi [Name],
I'll stop following up on the [project] proposal for now.
If you still want to move forward, I can pick it back up on a 15-minute call [day at 10:30] or [day at 3].
Best,
[Your Name]
Lead with the closure itself. It gives the buyer a concrete reason to correct the record.
Avoid sending this earlier than the second unanswered useful touch.
Who owns the decision
A proposal rarely turns on one person's yes, so the follow-up has to fit whoever's reading it. Your champion needs a summary they can forward. The economic buyer needs the business case. Legal, procurement, and implementation owners need to see the risks and handoff details. Ask each person for the part of the decision they control.
Forrester's 2024 State of Business Buying survey found an average of 13 people inside the buyer's organization touch a B2B purchase, with 89% of purchases involving two or more departments. Assume several stakeholders will need to sign off before anyone says yes.
- Champion: Your contact understands the proposal and owns the internal sell, but may not be able to sign. Help them forward the case instead of asking them for a final verdict.
- Economic buyer: The person who owns budget or strategic approval may have never opened the proposal. They need the problem, recommendation, tradeoff, investment, timing, and risk of waiting.
- Veto holders: Procurement, legal, security, finance, or IT may not care about the upside. Their job is to flag risk. Address their concerns before you learn about them late.
Proposal follow-up checklist
Before sending
- 1The first line names the decision the proposal puts in front of the buyer. If you need to reread the proposal to write it, the proposal asks for too many decisions at once.
- 2The email reacts to the last buyer signal in the thread. If their last note was about scope and your email talks about timing, you changed the subject.
- 3The forwardable summary explains why this approach over the alternative. Decision-makers reading a forward ask why this before how much.
- 4Timing pressure cites a calendar mechanic the buyer can verify, the kind named in the timing-pressure failure mode, not a vague 'soon.'
- 5After two unanswered useful touches with no new signal, the next email closes the file. A third reminder in different words is the same reminder.
- 6Nobody on the To line is being asked to make a decision they don't own.
How dreamif.ai helps with proposal follow-up
dreamif.ai drafts proposal follow-ups for the moment after the proposal is out, when the block is the approval chain rather than the document. It works from connected Gmail context, saved contact notes, approved Drive folders, and the proposal details you provide, and you approve every draft before it sends.
- Turns a champion-only thread into a forwardable summary the economic buyer and veto holders can act on without rewriting your proposal
- Reads the last buyer signal and the decision stage, then suggests the next move (forwardable summary, scope clarification, timing note, or close-the-file) and holds the draft in Gmail until you approve