Follow Up on a Proposal That Has Gone Quiet
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
You sent the proposal, asked whether the buyer had reviewed it, and then asked again. Neither message established whether the document was unread, blocked by an internal decision, unsuitable, or no longer relevant.
A useful follow-up tests one plausible explanation using evidence from the proposal or the conversation that preceded it. It gives the buyer a manageable question and gives you a reason for the next action.
The goal is not a more persuasive version of “any update?” It is to discover whether to clarify, revise, defer, or close the discussion without treating silence as evidence of a particular objection. The approach below addresses that diagnosis, not a universal contact schedule.
1. Separate evidence from interpretation
Before writing, review the issued proposal and the last substantive buyer conversation. Look for information that changes the question you should ask:
- Desired outcome: What did the buyer say needed to improve?
- Scope: Which elements were requested, and which did you add?
- Review process: Who needed to assess the offer, and what did they need to understand?
- Dependencies: Did the work depend on staffing, another project, or an internal decision?
- Unresolved requests: Did you omit a requested format, explanation, or option?
Keep the evidence narrow. “The buyer asked about phasing” is a fact from the conversation. “The buyer cannot afford the project” is an interpretation. Confusing the two can turn a reasonable question about project structure into an unnecessary discount.
Also separate access from suitability and consideration. Sending a file does not establish that the intended reviewer received it. An indication that someone opened it does not establish that they understood the scope. And possession of a PDF does not resolve a request for an editable version.
If you already know you missed a reasonable request, correct that mismatch before asking the buyer to diagnose it for you. They should not have to confirm that the document they previously requested would still be useful.
2. Choose one blocker worth testing
Choose a hypothesis supported by the record, not the explanation that feels most comfortable. A stakeholder-review problem may be easier to discuss than a weak offer, but that does not make it the right starting point.
Use three tests:
- Evidence: Can you point to a buyer statement or an unresolved proposal detail?
- Answerability: Can this recipient answer without rereading the entire proposal or consulting several colleagues?
- Consequence: Would the answer change what you do next?
For example, if the buyer previously mentioned an operations review, a question about staff workload has a basis. If nobody mentioned that review, asking whether operations is holding things up invents a process you do not know exists.
Before sending, complete this sentence: “If the buyer answers this, I will know whether to…” A useful ending might be “explain the workload” or “scope an independent first phase.” If the only ending is “follow up again,” the question probably needs work.
Where there is no specific evidence of a blocker, check whether the original need remains active. That is more honest than presenting a list of possible objections for the buyer to sort through.
3. Use a filled decision table
Fictional worked example: A consultancy has proposed a support-team onboarding project comprising process mapping, a manager workshop, and a pilot. A general request for feedback received no answer. Every situation, message, and outcome described below is hypothetical, not an Alactic customer result.
This table is a reusable decision aid. Select the row supported by the actual record; the rows are alternatives, not a sequence of messages to send.
| Known evidence | Possible blocker | Message brief | Response-to-action branches |
|---|---|---|---|
| A. Format mismatch. The buyer requested an editable proposal; only a PDF was supplied. | The document is unsuitable for the intended internal review. | Supply the requested editable version where appropriate. Identify its version and confirm whether its content differs from the PDF. Then ask whether any review obstacle remains. | Format resolved: retain the current scope. Another obstacle named: address it. Need ended: record closure. Silent: record the correction, but leave review status unknown. |
| B. Reviewer workload. Operations needs to assess staff involvement, but responsibilities are scattered through the proposal. | The reviewer cannot easily judge the internal workload. | Refer to the operations review and offer a concise responsibilities summary consistent with the proposal. | Summary wanted: provide it. Different concern: address that instead. Reviewer involvement requested: agree an introduction with the buyer. Silent: keep the blocker unconfirmed. |
| C. Scope breadth. The buyer prioritised supervisor onboarding; the proposal also includes broader process mapping. | The offer includes more work than the immediate need warrants. | Ask whether process mapping belongs in the current decision or whether an onboarding-only option would be more relevant. | Narrower option: confirm required outcomes before revising. Full scope needed: retain it. Neither fits: revisit the outcome. Silent: do not issue an unsolicited replacement. |
| D. Project structure. The buyer asked about phases but received one combined offer. | A smaller initial commitment or different allocation of work is needed. | Ask whether a separately scoped first phase remains important to the decision. | Yes: define a viable first-phase outcome. Total price concern: discuss scope and constraints. No: retain the combined structure. Silent: do not infer that a discount is needed. |
| E. Unresolved dependency. The pilot assumed a team lead would be appointed; that appointment was unresolved. | The work remains relevant but cannot proceed yet. | Ask whether the appointment is still the trigger for reviewing the proposal. | Yes: agree how to reconnect around that event. Lead appointed: recheck assumptions. Dependency changed: reassess delivery. Silent: do not record an agreed deferral. |
| F. Internal alternative. The buyer mentioned handling the work internally; no external decision process was agreed. | External support may no longer be needed. | Ask whether external support remains under consideration, making closure an acceptable answer. | Still relevant: establish what outside help must add. Handled internally: close as confirmed. Revisit later: identify the relevant event. Silent: any stop-pursuit decision remains internal. |
For Row A, supplying an editable document may require checking what can appropriately be shared. If there is a genuine restriction, explain it and offer a workable alternative rather than silently sending the wrong format again. Clearly distinguish a format correction from a commercial revision so reviewers know which content is current.
For Row B, a responsibilities summary should expose existing assumptions, not quietly add obligations. For Row D, a phase should have a useful outcome of its own; dividing the price without changing dependencies may leave the buyer with an unusable first stage.
4. Work through one row from message to action
Continue the hypothetical example using Row C. The proposal owner checks the conversation and confirms that supervisor onboarding was the buyer’s immediate priority. Broader process mapping was the seller’s addition. This supports a scope question, but it does not prove the wider scope caused the silence.
The owner sends:
Hi Morgan — following up on the support-team onboarding proposal. You identified supervisor onboarding as the immediate priority, while my proposal also includes broader process mapping.
Is that broader work useful now, or would an onboarding-only option be more relevant? If the need has changed entirely, let me know and I can close this proposal on my side.
This message identifies the offer, explains why the question matters, and allows a different explanation. It does not ask Morgan to complete a full review before replying.
Hypothetical response: Morgan says the onboarding-only option is relevant, but it must still include a manager handover. Process mapping can wait.
The next step is not immediately to remove a section and resend. The proposal owner confirms that the revised outcome is supervisor onboarding plus manager handover, then checks whether the pilot can work without the broader mapping exercise. If it cannot, the owner explains the dependency and proposes a bounded alternative rather than offering an unworkable reduction.
Only after that check does the owner prepare a revision. The observable result is a defined revision brief: retain the handover, remove or bound the wider mapping work, and reassess delivery assumptions. This is progress in decision quality, not evidence that a sale will follow.
5. Keep a compact record of the decision
The following filled record continues the same hypothetical example. Reuse its fields in a CRM or working document. It is a recommended operating design, not a claim that any particular product supplies these fields or actions.
- Proposal and current version
- Support-team onboarding proposal, version B; revision not yet issued.
- Confirmed buyer need
- Supervisor onboarding with a manager handover.
- Evidence before follow-up
- Buyer prioritised onboarding; seller included broader process mapping.
- Hypothesis tested
- The broader scope may exceed the immediate need.
- Buyer-confirmed explanation
- Onboarding-only option is relevant; broader mapping can wait.
- Agreed revision boundary
- Preserve manager handover. Check pilot dependencies before removing mapping.
- Next action and owner
- Proposal owner to assess feasibility and return a defined revised scope.
- Still unknown
- Whether the revised offer will meet the buyer’s approval requirements.
Record what changed, not merely that a reply arrived. Here, the scope preference is confirmed, but approval is not. Keeping those separate prevents an encouraging exchange from becoming an overstated pipeline status.
6. Recover when the diagnosis is wrong or silence continues
A diagnostic question must be easy to correct. If Morgan instead says that scope is fine but staff availability is the issue, acknowledge that information without defending the original theory.
Hypothetical recovery: “Thanks for clarifying. I’ll leave the scope intact and check the staff-workload assumptions before suggesting a different delivery approach.”
A proposed remedy can also be too burdensome. A buyer who needs one responsibility clarified may not benefit from another attachment or a meeting. Answer the specific uncertainty first; expand only where the task requires it.
If there is still no reply, inspect the question rather than simply increasing activity. Could this person answer it? Did you present an assumption as fact? Did your request require a complete review? Did you offer something relevant to the stated problem?
New, concrete evidence can justify a different question. Without it, rotating through scope, budget, and timing guesses risks creating activity without learning anything. Decide whether the proposal still merits active attention under your operating criteria, while leaving the buyer’s reason unknown.
7. Use a short response-handling checklist
- Clarification: Answer the unresolved point. Change the proposal only if the offer itself changes.
- Revision: Confirm the intended outcome, what stays, and what changes before producing another version.
- Deferral: Record the buyer-confirmed trigger and agreed next action. An internal reminder is not an agreed buyer commitment.
- Buyer-confirmed closure: Record the stated reason accurately, without arguing against the decision.
- Internal stop-pursuit decision: Record that you stopped active follow-up and that the reason for silence remains unknown.
- Recordkeeping: Retain the current version, evidence, hypothesis, buyer explanation, next action, and owner.
Assess the follow-up by whether it produced a better-supported action: a clarification, a defined revision, a confirmed deferral, an explicit closure, or an honest record of continued uncertainty. A reply alone is not the outcome; knowing what it warrants is.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications