Put a Decision Deadline on Every Open Proposal
An open proposal is not proof that a deal is moving. Sometimes it only proves that your document is still sitting in somebody's inbox.
Polite follow-up can keep a dead proposal alive for months
You send a recommendation. The client says they need time. A week later, you ask whether they have questions. Then you check in again. The buyer replies, "Still reviewing," so the opportunity stays in proposal stage.
Nothing has moved. The pipeline says it has.
Small advisory firms do this because closing a proposal feels too final. The relationship still matters. The project could come back. Nobody wants to pressure the client or walk away too early.
I get it. But leaving a proposal open forever does not protect the relationship. It hides the actual decision, weakens your forecast, and keeps the advisor chasing a document instead of helping the client resolve what is blocking it.
Every proposal needs a decision deadline. That is the date when the advisor and client will decide whether to approve the recommendation, revise it, return the opportunity to discovery, move it to a dated nurture track, or close it.
The deadline is not an ultimatum. It is an operating decision.
A proposal expiration date and a decision deadline are different
A supplier quote may expire because pricing, incentives, inventory, or implementation assumptions can change. That commercial date matters, but it does not tell you whether the client is ready to decide.
The decision deadline belongs to the buying process. It should reflect the client's approval path, remaining evidence, internal meetings, contract timing, and business event behind the project.
Record both dates when they differ. If supplier pricing expires on September 10 but the client's budget committee does not meet until September 25, you have a gap to resolve. The answer might be updated pricing, a conditional approval, a different implementation date, or a pause. Hoping the dates work themselves out is not a plan.
Your original proposal process should establish the decision path before the document is sent. Proposal follow-up keeps that path honest after the client sees the recommendation.
Keep the proposal active only when the client is still deciding
An active proposal needs current evidence of a buying decision. Seller activity alone does not count.
Keep it active when the client has confirmed the problem still matters, the right people are involved, the commercial path is possible, and a specific unresolved item stands between the current state and a decision. You also need a dated client action or meeting.
That unresolved item should be concrete. Legal is reviewing a named agreement. Finance asked for a revised cost view. Security needs an answer about one control. An executive sponsor wants both options compared on a different term. Those are real next decisions.
"They are looking at it" is not enough. Neither is a string of unanswered emails.
If you cannot name what the client must do next, who owns it, and when it will happen, challenge the stage during your weekly operating review.
Find the block before you write another follow-up email
Open the deal record and compare what you believed before the proposal with what the client has done since receiving it. You are looking for a changed assumption.
Check the original trigger, decision criteria, stakeholders, proposal review notes, objections, supplier changes, commercial terms, and promised next actions. Then ask the client a direct question about the remaining decision.
You might say, "We agreed that legal review and final budget approval were the two remaining steps. Has either one changed, and what date should we use to decide whether this recommendation still moves forward?"
That is more useful than "Just checking in." It gives the client something specific to correct.
If the answer reveals missing requirements, a new stakeholder, uncertain funding, or a changed business event, stop treating follow-up as the problem. The deal may need more discovery.
Choose one of five proposal decisions
Every open proposal review should end with one treatment. Do not create a sixth category called "keep trying."
Keep it active
Use this when the client confirms the project, remaining decision, owner, and date. Update the opportunity with the evidence. The next action should belong to the person who must act, even if your internal task belongs to the advisor.
Revise the proposal
Revise when the client has changed a requirement, scope, commercial assumption, supplier option, or implementation date and still intends to decide. Record what changed and why. Preserve the prior version so the team can see the decision history.
Do not revise a proposal simply to create motion. A new cover page and another discount will not fix missing authority or weak urgency.
Return to discovery
Move backward when the recommendation no longer matches the client's situation. A merger, leadership change, new security requirement, budget reset, or expanded location count can make the original brief incomplete.
Returning to the discovery process is not failure. Pretending the old proposal still fits is worse.
Move it to dated nurture
Use nurture when the problem is real but the buying event is not active. Name the event that should reopen the deal, such as a budget cycle, contract window, location approval, leadership hire, or supplier milestone. Assign an owner and a review date.
Remove the opportunity from the active forecast. Keep the relationship and future trigger visible through the same discipline you use for trigger-based prospecting.
Close the proposal
Close it when the client selected another path, canceled the project, cannot support the commercial decision, stopped participating after a clear closeout attempt, or no longer has the problem your recommendation addressed.
You can close an opportunity without closing the relationship. Send a direct note that records the current decision and leaves the door open around a named future event. Then use a lost deal review if the opportunity is meaningful enough to teach the firm something.
Set the deadline with the client, not inside your CRM
An internal close date helps with reporting. It does not create a client commitment.
Agree on the decision deadline during the live proposal review. Ask what still needs to happen, who will participate, what evidence remains, and when the recommendation will be approved, changed, or paused. Put the date in the follow-up note and ask the client to correct anything that is wrong.
If the client will not agree to a date, do not invent one and call the deal committed. Decide how long your firm is willing to keep doing active work without a client decision. That boundary may depend on relationship value, supplier effort, commercial exposure, and the reason for delay.
Sometimes the honest answer is that the client wants information, not a buying process. Okay, cool. Help where it makes sense, but do not forecast curiosity as revenue.
Protect the recommendation when facts change
A proposal can age out even when the client still likes it. Supplier pricing changes. Contract dates move. Technical assumptions become stale. The implementation team loses capacity. A product or service no longer matches the original requirement.
Define which changes require revalidation before signature. At minimum, recheck commercial validity, scope, client requirements, implementation timing, and any condition named in the recommendation. Confirm material supplier promises in the documents that govern the purchase.
Do not let a buyer sign an old recommendation because everyone is relieved the deal came back. Reopen the decision, verify the evidence, and issue a current version.
Review proposal aging by evidence, not color
A dashboard that turns proposals red after thirty days can help you find work. It cannot decide whether the deal is healthy.
Review each open proposal by days in stage, last confirmed client action, decision deadline, commercial expiration, unresolved item, next client owner, and next advisor action. Separate internal effort from buyer movement.
Then inspect patterns. If many proposals stall before live review, change the sending process. If legal questions repeatedly appear late, improve discovery and contract preparation. If clients ask for revisions without making decisions, tighten revision boundaries. If a supplier's quote window routinely conflicts with client approvals, address the timing before proposal stage.
The point is not to punish old deals. It is to stop age from becoming the only evidence you have.
Keep proposal decisions in the operating record
Advisor OS CRM connects a visual deal pipeline with client and contact records, activity history, tasks with due dates, suppliers, proposals, reminders, and reporting. That gives a small advisory firm one place to keep the proposal, the client's decision evidence, the owner, and the next date together.
The system cannot make a buyer decide. It can show whether your team has a buying process or a collection of follow-up attempts.
Open every proposal in your pipeline today. For each one, name the remaining client decision, the person who owns it, the commercial expiration, and the date when the proposal will stay active, change, move, or close. If you cannot fill in those fields from confirmed evidence, the stage is already telling you something.
Run the free Advisor OS agency scorecard if proposal follow-up, pipeline stages, and next actions still depend on advisor memory.