Follow-up emails after a proposal, for every way a deal can stall

This page is for account executives, founders, agencies and consultants who've sent a proposal or quote and are waiting for an answer. It covers when to follow up, a template for each way a proposal can stall, a worked example with the arithmetic behind a "cost of waiting" email, and the one contract rule worth knowing before you put an expiry date on an offer. If the person has gone completely silent on everything, not just the proposal, the follow-up emails after no response are a better fit.

Set up the follow-up before you send the proposal

The best follow-up is agreed in advance. Before the proposal goes out, ask three questions on your last call:

1. "When do you need to decide by, and what happens on that date?" A decision date tied to an event (a budget meeting, a contract ending, a project start) is real. "End of the quarter" usually isn't.
2. "Who else will read this before it's approved?" Finance, procurement, legal, the owner. Each of them may need something different.
3. "Can we put 20 minutes in the diary to walk through it together?" A review call booked for two or three days after you send the proposal is the single most useful follow-up, because it's already agreed.

If you can't get a review call, you can still write each follow-up around the decision date and the people involved. For longer deals with several approvers, a shared mutual action plan turns those answers into dates that both sides can see.

When to follow up after sending a proposal

Three to five follow-ups over a month is normal for a proposal a buyer asked for. The question isn't how many emails you send but whether each one gives them a reason to reply. For more on cadence across the whole sales cycle, see how many follow-up emails to send.

Follow-up email after proposal templates

Subject: [Company] proposal: [the decision it covers]

Hi [first name],

One question on the proposal I sent [day]: does [the option or scope you recommended] match what you had in mind, or would [the alternative] fit [their goal] better?

Happy to adjust before it goes to [the other approver]. Would [day] at [time] work for 20 minutes to go through it?

[Your name]

Subject: For [day]'s meeting: [company] proposal in three points

Hi [first name],

In case it's useful for [day], here's the proposal in three lines you can forward as is:

1. The problem: [their problem, in their words].
2. What we'd do: [scope in one sentence], starting [date].
3. Cost and return: [price], against [expected saving or gain, and how it was estimated].

The question [finance / the owner / procurement] usually asks is [likely question]. The short answer: [answer].

Good luck on [day]. Let me know what comes up.

Subject: [Company] proposal after [decision meeting or date]

Hi [first name],

[Decision date or meeting] was [day], so I wanted to ask directly: where did the proposal land?

If it's still under review, is there anything I can answer for whoever's deciding? If the plan has changed, that's useful to know too, and I'll stop asking.

Subject: Options for [company] at [their budget]

Hi [first name],

Thanks for being straight about the budget. Rather than cut the price for the same work, here are two ways to bring it closer to [their number]:

Option A: [reduced scope, e.g. phase one only], [price]. You'd still get [the main outcome].
Option B: [same scope, different terms, e.g. spread over two budget years], [price per period].

The full proposal still gives [the extra outcome], if that changes the decision.

Which is closer to what [the budget holder] would approve?

Subject: Anything I can do to help [company]'s review?

Hi [first name],

I know the proposal is with [procurement / legal / IT security] now. To save them time, I can send:

- Our completed [vendor form / W-9 / insurance certificate / security questionnaire]
- Our standard terms in Word, so they can mark up changes
- A call with [our counterpart] to go through any questions directly

Is there a date they're aiming for, so I can make sure nothing's waiting on us?

Subject: What a [month] start means for [company]

Hi [first name],

A quick number in case it helps the discussion. The proposal estimates [saving or gain] of [amount] a [month]. If the start moves from [month] to [month], that's about [amount x months delayed] that [company] doesn't get this year.

That isn't a reason to rush a decision that isn't ready. But if timing is the only open question, it may be worth knowing.

Subject: [Company] proposal: pricing valid to [date]

Hi [first name],

A heads-up that the pricing in the proposal is valid until [date], because [the honest reason, e.g. our supplier's equipment quote expires then / our crew schedule for spring fills up].

After that, [what happens: we re-quote at current prices / the start date moves to X]. If you need more time, tell me and I'll see what I can hold.

Subject: Revised proposal for [company]: [what changed]

Hi [first name],

Attached is the revised proposal. What changed, so you don't have to compare versions:

- [Change 1, e.g. phase two removed; price now X]
- [Change 2, e.g. start moved to March]

Everything else is as before. Does this version work for [the approver]?

Subject: Should I close the file on [company]'s proposal?

Hi [first name],

I haven't heard back on the proposal, so I'll assume the timing or the fit isn't right and close it on my side.

If anything changes, I'm easy to reach, and I'm happy to update the numbers whenever it's useful.

Subject: Thank you, and one question

Hi [first name],

Thanks for letting me know, and for the time your team spent with us.

Would you share the main reason you went another way? Price, scope, timing, or something we missed? A one-line answer helps us get better, and I won't use it to reopen the decision.

The close-the-loop email often gets the reply the other follow-ups didn't, because it's easy to answer and it removes pressure. For more versions, see the breakup email templates.

Worked example: a solar proposal that slipped

Illustrative example. The companies, people and figures are fictional, to show the method.

The seller: Brightfield Solar Builders (brightfield.example), a solar EPC firm. The buyer: Ridgeway Packaging (ridgewaypack.example), a manufacturer with a large flat roof. The proposal: a $1.1 million rooftop system, estimated to cut Ridgeway's electricity bill by $11,500 a month once running. Pricing is valid for 30 days, because Brightfield's module supplier holds its quote for 30 days.

Before sending: the account executive, Lena, learned that Ridgeway's CFO decides at a capital meeting on 12 November, and that the operations director, Tom, will present it. She booked a review call with Tom for 6 November.

The follow-ups:

The cost of waiting, worked out. If construction starts in February instead of November, the system starts producing about three months later. At an estimated $11,500 a month, that's about $34,500 of savings Ridgeway doesn't get, against a project whose price is held only until 4 December. Lena's email gave that number once, said plainly that it wasn't a reason to rush, and asked whether timing was the only open question.

The result: the CFO approved phase one in December at the held price, with phase two in the next budget year: the price-pushback template, used before anyone asked for a discount.

Most proposals stall for reasons the seller never hears. Research helps before the proposal, too: knowing what's happening at the account (a new site, a cost squeeze, a leadership change) gives you the "why now" for the cost-of-waiting email. Bebop researches each account and writes a playbook with that context, the people involved and the objections to expect.

Expiry dates: the contract rule to know

This is general information, not legal advice. In most US states, sales of goods are governed by Article 2 of the Uniform Commercial Code (UCC). Its section 2-205 covers "firm offers": when a merchant makes an offer to buy or sell goods in a signed writing that gives assurance it will be held open, the offer can't be revoked for lack of consideration during the time stated, or a reasonable time if none is stated, and in no case for more than three months. If that assurance is on a form the buyer supplied, the merchant must sign it separately.

What that means for your follow-ups:

• "Valid until" can be a real commitment. If your proposal sells goods and promises to hold the price to a date, plan on honoring it.
• Don't invent urgency. An expiry date you won't enforce teaches the buyer to ignore your dates. Give the real reason, as in the template above.
• Services work differently. Section 2-205 covers goods only. Proposals for services, or for a mix of equipment and installation, fall under other contract rules that vary by state, so check with counsel before relying on an expiry date either way.

Mistakes to avoid

• "Just checking in." It asks them to do the work of explaining where things stand. Ask one specific question instead.
• Discounting before anyone asks. It tells the buyer the first price wasn't real. Offer scope options first.
• Following up only with your contact. If the CFO decides, help your contact brief the CFO.
• Fake deadlines. They work once and cost you credibility for every deal after.
• Sending the same email three times. Each follow-up needs something new: an answer, a number, an option or a close.

Checklist before you hit send

• You know the decision date and who decides, or this email asks.
• The subject line names the proposal and the decision, not "following up".
• There's one specific question or one useful addition.
• Any number in it (savings, cost of waiting) uses the proposal's own estimates.
• Any expiry date is real, and you've given the reason.
• If this is the third or later follow-up, it offers an easy way to say no.

Next step: if the proposal itself is the problem, rebuild it with the sales proposal template, which includes a one-page version for smaller deals.