A proposal follow-up workflow should track the version sent, the prospect's decision date, the next responsible person and the conditions that stop reminders. Use automation to surface overdue decisions. Keep negotiation, changes to scope and the choice to close an opportunity with the person responsible for the sale.
- Record the proposalCapture version, recipient, sent date, and conversation owner.
- Set review pointUse buyer's decision date or an internal review date.
- Choose next actionName the outstanding decision and responsible person.
- Apply stop conditionsStop irrelevant reminders after a reply, revision, decline or completed handoff.
A sent proposal is not an accepted project or a buyer decision.
Separate a sent proposal from a decision
Sending a document is one event. A prospect accepting, requesting a change or deciding against it is another. Your workflow needs to distinguish those events so a sent proposal does not quietly become an assumed project.
Record which version was sent, when it was sent, who received it and who owns the conversation. Add any decision date the prospect actually supplied. If no date was agreed, record that fact and choose an internal review date rather than inventing a deadline for the buyer.
Make the next action visible
The record should answer four questions: what is the prospect deciding, what information is still missing, who will act next, and when should someone review the opportunity? A stage such as “proposal sent” is too broad to answer all four.
- Decision date passedReview unless a reply or revised date arrived.
- Clarification requestedSend agreed clarification and update the record.
- Scope changedPrepare a new version and supersede the earlier one.
- Decision completeClose after decline or complete the delivery handoff.
The table is an operating agreement, not a universal contact schedule.
| Current situation | Useful next action | Reminder stop condition |
|---|---|---|
| Buyer agreed to a decision date | Review after that date | Reply or revised date received |
| Buyer requested clarification | Send the agreed clarification | Question answered and record updated |
| Scope changed | Prepare and review a new version | Previous version marked superseded |
| Buyer declined | Record the reason and close | All sales reminders stop |
| Buyer accepted | Verify required commitments | Handoff to delivery completed |
Use the table as an operating agreement. It is not a universal schedule for how often an agency should contact a prospect.
Write a follow-up around the outstanding decision
A useful follow-up names the issue the buyer is resolving. If the buyer was comparing a smaller scope with a full engagement, ask which route makes sense or what information is still needed. If a stakeholder had to review the proposal, ask whether that review happened.
Avoid pretending that a message is personal when it is assembled from an incomplete record. A reminder to the sales owner is often safer than sending directly from a timer. The owner can review the thread, check for a response elsewhere and decide whether to contact the buyer.
For example, a prospect might reply by text while the proposal system still shows an unanswered document. Your process should let the owner record that reply and stop an automated email. The tool status is an input, not the final authority on the relationship.
Keep version changes explicit
When scope or terms change, mark the earlier proposal as superseded and identify the current version. A follow-up that links to the wrong document can create a decision your delivery team cannot interpret.
- Earlier versionMark it superseded when scope or terms change.
- Current versionIdentify the proposal currently under review.
- Accepted older versionCompare it with the latest proposed scope.
- Resolve discrepancyPause handoff until the responsible person resolves it.
File names alone do not establish which agreement applies.
Record the reason for the revision and any agreement that changed. Avoid relying on the file name alone. If a buyer accepts an earlier version while a new one is being prepared, pause the handoff and resolve the discrepancy with the responsible person.
Define the acceptance handoff
Your agency may require a signature, an internal approval, an initial payment or another documented commitment before delivery begins. State those requirements in the workflow. A verbal yes should trigger a check, rather than automatically notifying the team that work can start.
The completion record should show the accepted scope, current agreement, commercial owner and delivery owner. Link to the kickoff handoff guide when the sale is ready to move into delivery.
Check the workflow after a small trial
Review a small set of proposals manually. Look for messages sent after a reply, opportunities with no next action, superseded links and accepted work without a delivery owner. Fix those failures before adding more stages or messages.
- Reply after reminderFind messages sent after a prospect already replied.
- Missing next actionFind opportunities with no named follow-up.
- Superseded linkFind records linking to an outdated proposal.
- Incomplete acceptanceFind accepted work without a delivery owner.
Fix observed failures before adding stages or direct automated messages.
Measure the share of open proposals with a clear next action and the number requiring manual rescue. Conversion outcomes matter, but they depend on fit, offer and the buyer's circumstances as well as follow-up.
Questions and answers
How often should an agency follow up on a proposal?
Use the buyer’s agreed decision date and the outstanding question to choose the next action. If no date was agreed, choose an internal review point. There is no evidence here for one schedule that works for every agency or prospect.
Should proposal follow-up emails send automatically?
They can in a clearly defined situation with reliable stop conditions. Start with owner reminders if replies arrive through several channels or negotiation is common. Test declines, scope changes and late replies before sending messages directly from a timer.
What if the prospect accepts an old version?
Pause the delivery handoff and reconcile which agreement applies. Identify the version the prospect accepted, compare it with the latest proposed scope, and have the responsible commercial owner resolve the difference before a project is opened.