Proposal Follow-Up: Keep Service Deals Moving
Build a proposal follow-up process around review meetings, decision conditions, and clear dispositions instead of repeatedly asking whether the buyer has read it.
A proposal follow-up process works when the proposal enters a defined decision path. A sent document is not a buying milestone by itself. Before delivery, agree on who will review it, what they need to decide, and when the next conversation should happen.
Confirm the review process before sending
Ask who needs to see the scope, how investment is approved, and whether procurement or another internal step exists. If you cannot identify a review owner, sending the proposal may simply move uncertainty into an inbox. Keep the document aligned with the discovery evidence rather than adding unrequested features to make it look substantial.
Follow up on a decision condition
A useful follow-up refers to something specific: a scope question, an approval meeting, a missing input, or a scheduled review. ‘Did you read it?’ can establish receipt, but it rarely advances the decision. Try: ‘You mentioned that the operations lead needed to confirm implementation access. Has that review happened, or should we walk through the requirements together?’
Use a proposal decision tracker
| Field | What to record |
|---|---|
| Review owner | Person responsible for internal circulation |
| Open question | Specific uncertainty that blocks approval |
| Decision event | Review meeting or approval step |
| Next action | Owner and agreed date |
| Disposition | Proceed, revise, defer, or decline |
In an illustrative service deal, the proposal arrives Friday but the buyer’s approval meeting is the following Wednesday. Daily reminders before that meeting add little. A confirmation of the open scope question and a Thursday review are better aligned with the process.
Revise scope deliberately
If the buyer requests changes, show the impact on deliverables, timing, responsibility, and investment. Do not quietly remove important work while leaving the promised outcome intact. A revised proposal needs a new version and a clear explanation of what changed.
End stalled proposal loops
If the decision process disappears, ask whether the project remains active and offer an honest defer or decline path. Record the answer. A proposal can be correctly closed without damaging the relationship. Leaving it in a near-term forecast for months creates a reporting problem.
Frequently asked questions
Should proposals have an expiration date?
Use one when pricing, capacity, or terms actually have a time limit. Explain the real reason. An invented deadline does not replace a buyer’s decision process.
How many follow-ups should you send?
Build a bounded plan around agreed events and channel preferences. The right number depends on the buying cycle; repeated messages without new information are a weak default.
Put this into practice
Add the decision tracker to every open proposal. For the oldest five, confirm the actual review path and either schedule a useful next action or update the disposition.
For the wider operating context, start with Educo’s service business approach. To discuss the constraint in your own business, talk to Educo.
