Sales Proposal Follow-Up and Close Plan

Most deals stall at least once. Forrester's State of Business Buying 2024 report found that 86% of B2B purchases stall during the buying process¹. Your best protection is to agree on what happens next while you still have the buyer's attention.

Book the review call before the proposal goes out, and ask how the decision gets made. Three questions do most of the work, and each has a short, factual answer:

• When does the group that approves this next meet?
• What has to be submitted before that meeting, and by when?
• When does your current contract end, and how much notice does it need?

Once both sides agree on the dates, put them in a mutual action plan that you and the buyer can both see.

The day you sent the proposal says nothing about when the buyer will decide. Their calendar does. Collect every date they've mentioned, with who said it and where, since the important ones can come up in passing on a call and never get written down.

When the buyer is replacing a vendor, the notice date matters most. By default, Salesforce's standard agreement renews subscriptions for another year unless either side gives written notice at least 30 days before the term ends². For a customer who wants to leave, that notice date is the deadline, and missing it pushes the switch back a year.

Empty reasons stop working when the ask is big. In a 1978 experiment by the psychologist Ellen Langer and colleagues, a stranger asked people about to use a copier if they could go first. When the favor was small, "because I have to make copies" worked almost as well as "because I'm in a rush": 93% said yes, against 94%.

When it was big, the empty reason did no better than no reason at all³: 24% each, against 42% for the real one. Approving a contract is a big favor, and "just checking in" is the sales version of "because I have to make copies."

Real reasons are things the buyer can use:

• A written answer to a question or objection someone raised
• A document they need, such as a completed security questionnaire
• A revised price or option, such as an updated quote and order form
• A booked call with a customer like them
• A specific question about a date, such as when submissions close

Your contact is rarely the only person deciding. Forrester's State of Business Buying 2026 report found that the typical buying decision includes 13 internal stakeholders⁴, and procurement professionals are decision-makers in 53% of buying cycles. A plan aimed at one contact leaves the rest of the committee with nothing new.

Send each message to the person who needs what it carries: the security questionnaire to the security reviewer, the pricing change to procurement, the reference call to the skeptical executive. Copy your main contact so nothing surprises them.

Track absences person by person, not for the whole account. A reviewer's leave matters only to the message the reviewer has to act on. If you don't know who's involved yet, sketch a stakeholder and champion map first.

Lead with what you're delivering, tie it to one of their dates, and make one ask. Skip the apology for writing again and any line about how long it's been. Leave your quarter and quota out of it; real urgency lives on the buyer's calendar.

Short doesn't mean a one-liner, though. Boomerang, which makes an email reminder tool, analyzed its users' emails to see which got replies. In 2016 it reported that messages of 50 to 125 words drew response rates above 50%⁵. A 25-word email did about as well as a 2,000-word one, at 44%.

Know when to stop. If the only meeting that could approve the deal before the notice date has passed, say so and plan for the next cycle. Chasing a closed window spends goodwill you'll need next time.

To skip the date work, paste your proposal and notes into the tool at the top of this page. It finds the real deadline, builds the timeline and drafts each message for you to edit.