Start with the last thing the buyer actually confirmed
The deal looked promising after the demo. Your contact liked the demo, asked for a proposal and said they would take it to the team. Now your messages are going unanswered, and you are trying to write a follow-up that doesn't sound like the last one.
Before changing the wording, look at what you know.
Did the buyer agree that the proposal solved their problem? Did they agree to review it? Or did you send it after a conversation that ended warmly, without finding out what happened next?
Those are different starting points. Treating them as the same can send you looking for a stalled approval when the buyer has never made a decision in the first place.
One seller describes the gap: "At some point I am out of things to provide, and they have to make a decision, and very often I'm not involved in that decision making process".11 Public seller discussion, “So many deals stuck in decision making hell”. A first-person account in the medical market, used to illustrate limited visibility into internal buying discussions. No frequency or causal conclusion is inferred.https://www.reddit.com/r/sales/comments/1ic72ug/so_many_deals_stuck_in_decision_making_hell/
That is a public account from a seller in the medical market. It captures something worth remembering: your contact can stop talking to you while people inside the business continue talking to each other. You may not be invited to those conversations.
You also cannot assume they are happening. A quiet inbox leaves both possibilities open.
Start a short note with two separate lines: what the buyer last confirmed, and what you currently think it means. Include when they said it. A concern raised three weeks ago is the last known concern, not proof that it is still the obstacle today.
For example, a buyer agreeing to show the proposal to finance is evidence of an intended review. It is not evidence that finance has received it, agreed the spend or started approving a purchase.
That distinction gives your next message a job. You need to establish what happened to the review before sending another argument for the product.
Stall Signals names changes worth investigating, including a contact going dark or a priority shift.55 PacedRevenue framework registry. Canonical definitions of Capture, Stall Signals, Deal Forensics and The Decision Audit.https://pacedrevenue.com/insights/pipeline-physics/glossary/ Treat each as a prompt for a question, rather than evidence of its own cause.
Find the question that is still open
Imagine you sell a reporting tool. The following situation, replies and estimates are hypothetical examples, not accounts of an actual customer.
Your contact says finance likes the product. Operations is worried about the work of connecting the data. You have already sent a proposal, but nothing has moved since that concern was raised.
The open question is whether implementation is feasible for the buyer. Repeating the reporting benefits leaves that question unanswered. A discount may make the price more attractive while leaving the workload exactly as it was.
A more useful response separates the work your business will do from the work the buyer would need to do. Name the tasks, the people needed and the assumptions you still need checked. Leave estimates open where you do not have enough information.
For this hypothetical reporting tool, the first version could be this small:
| Work to check | Proposed owner | What still needs confirming |
|---|---|---|
| Prepare the import and map the fields | Vendor | Which export formats can the product accept? |
| Provide a sample export without personal data | Buyer’s operations lead | Can they produce it, and when? |
| Check totals against the current report | Buyer’s finance lead, with vendor support | Which report is the reference, and who can review the result? |
These are proposed responsibilities, not tasks the buyer has accepted. Let the buyer correct the split before turning it into a plan.
Suggested wording:
The open question from our last call was how much work operations would need to take on. I've separated the tasks we handle from the ones we'd need from you. Would it help to check that split with your operations lead?
The invitation has a purpose. It also gives the contact a way to correct you. They might explain that implementation is no longer the problem, or that operations has no capacity until another project ends.
If they want the review, agree what it needs to establish. Can the named people do the work? Is a task missing? Does the proposed start date fit their other commitments? You are helping them reach a decision about feasibility.
If they cannot spare the time to meet, offer to take corrections on the task list. The format matters less than answering the question. A buyer should not have to attend your preferred meeting to make progress.
HubSpot opens its guidance on stalled negotiations by describing reluctance to continue negotiating.22 Jay Fuchs, HubSpot, “Stalled Negotiations: Why They Happen & 4 Tactics to Handle Them”. Its opening description frames stalling as reluctance to continue negotiating. Used as a comparison, not an empirical diagnosis of silent prospects.https://blog.hubspot.com/sales/move-stalled-deals-forward That is one possible situation. Your own buyer’s concern still needs to be established before you choose a response.
When several questions remain open, ask which one is stopping the next decision. You may eventually need to answer all of them. Starting with the immediate obstacle gives you a reason for the next piece of work.
When the answer changes, change the help
In this hypothetical reporting-tool purchase, suppose operations confirms that the implementation plan is workable. The budget owner agrees to proceed, subject to security approval.
This is progress. It is also a different situation from the one you were in before the review.
Your contact then says security has not received the questionnaire. Continuing to explain implementation or resending the proposal would leave a known handoff unfinished.
Ask who should receive the material and what they need from you. Work through the route your contact recommends. Bypassing your contact can make it harder for them to get the purchase agreed internally.
Suggested wording:
You mentioned security hasn't received the questionnaire yet. Who should it go to, and is there anything missing from our side before they can review it?
The first useful change is that the right person receives a complete submission. The next is that they review it and tell you whether anything remains unresolved. Record those separately. Sending a document is not the same as passing a review.
MEDDICC describes the Paper Process as the steps between a decision and signature.33 MEDDICC, “Paper Process”. The publisher's account of process, people and timing between decision and signature. A framework description, not a finding that every buying process is linear.https://meddicc.com/what-is-meddpicc/paper-process Mapping the people and steps helps you see work that can remain after your contact has chosen the product.
But take care with the word approval. It can cover very different decisions. Finance might still be deciding whether the project deserves funding. Security might find a requirement you cannot meet. Legal might raise a term neither side can accept.
Those reviews can reopen the purchase. A contact saying the deal is with procurement does not make the remaining work a formality.
Ask what the next person is being asked to approve. Then find out what they need to make that decision. This is more informative than asking when procurement will be finished, especially if your contact doesn't yet know the process.
You do not need a complete map of the organisation before helping. Start with the next missing recipient or decision. Extend the map as the buyer explains what follows.
Check whether the remaining work fits the date
A hopeful close date can survive in the CRM long after the plan behind it has stopped making sense. Let enough of those dates survive and your CRM fills up with stale deals.
Continue the reporting-tool example. Suppose the process owners give you the following estimates once they have complete inputs. These are invented working-day estimates for the example, not standard approval times or promises about when work will finish.
| Remaining step | What must happen first | Assumed time |
|---|---|---|
| Security review | Complete questionnaire received | 5 working days |
| Contract review | Security clears the proposed setup | 3 working days |
| Signature | Contract terms agreed | 2 working days |
| Sequential plan | Each step waits for the one above | 10 working days |
If there are six working days left before your hoped-for close date, this plan runs four days beyond it. That gap exists even if every estimate proves right and no new work appears.
The useful conversation is about the dependencies. Can contract review start while security reviews the setup, or does it genuinely need security's result? Ask the people who own the work. Don't assume their answer because overlapping the tasks would suit your quarter.
If they confirm that the first two reviews can run together, the longer review takes five working days. Signature then adds two. The revised plan needs seven working days, which still exceeds the available six by one.
Queues, missing information and rework could add more time. This calculation is a planning check, not a guaranteed earliest signature date. Its value is making the assumption visible while there is still time to discuss it.
You could send:
Based on the steps we've listed, the current timing runs beyond the date we had in mind. Can we check which reviews depend on each other and agree a date that reflects the remaining work?
Your buyer may have a genuine deadline of their own. Understanding it helps both sides decide whether a different scope or sequence is possible. Any change needs to work for the people doing the work, including those responsible for the review.
Offering money off does not itself complete a questionnaire, remove a review or create someone's availability. Before changing the price, establish whether price is the question anyone is currently trying to answer.
If the project has changed, make room for an honest answer
Sometimes there is no useful way to move the deal forward now.
Suppose the reporting buyer tells you a merger has taken priority and the project is paused. That is a new fact. Sending another product comparison would ask them to revisit a decision they have just told you they are not making.
Acknowledge the change and find out whether there is a real reason to return later.
Understood. I'll pause the proposal work. If the reporting project is still planned after the merger work, what would make it useful to pick this up again?
They might name a planning meeting or the completion of a particular project. They might not know. Record that answer instead of supplying a date because the CRM requires one.
A restart condition is useful when it comes from the buyer's situation. Your own quarter-end is not evidence that their priorities will change. Keep any required internal date clearly labelled as an assumption, following your team's reporting rules.
This also protects the relationship. You can remember the person's needs without behaving as though every conversation must become a purchase this month.
If they tell you they have chosen another supplier, acknowledge the decision. Ask for feedback only if they are willing. If they ask you to stop contacting them, stop. A closing sequence is not a reason to override a clear answer.
The difficult case is when there is no answer at all. You still need to choose how much attention to give the opportunity, but you do not have enough information to explain the buyer's behaviour.
When the cause is unknown, ask a smaller question
Imagine the buyer agreed to review the scope last Tuesday. Two messages have gone unanswered. You have no current information about budget, security, competitors or priorities.
The fact is that the review has not been confirmed. The cause is unknown.
Avoid sending a list of everything you think might be wrong. That gives a busy person more to process and can introduce concerns they never raised. Return to the last agreement and make the question easy to answer.
Suggested wording:
We had planned to review the scope last Tuesday. Is that still planned, or should I pause this for now? If something in the scope needs answering first, you can send me that point directly.
Adapt this to the relationship and the agreement you actually made. If no review was agreed, don't write as though the buyer missed a commitment. Ask whether reviewing the proposal would still be useful.
A reply may reveal a concern, a handoff or a changed priority. It may simply say they need more time. Ask what would make a later contact useful, where that is reasonable, and respect the way they prefer to communicate.
If there is still no reply, the cause remains unknown. You can pause active pursuit or reduce confidence in the expected timing as an internal decision. You don't need to invent a story about the competitor or blame your contact to justify that choice.
Follow up around an agreed event or relevant new information. There is no fixed number of quiet days that tells you what happened inside every buyer's business. Use your own history to review contact timing, while keeping exceptions visible.
Gong analysed 304,174 emails, looking at calls to action and meetings booked within ten days.44 Devin Reed, Gong Labs, “Surprising cold email CTA that increases meeting bookings”. Analysis of email calls to action, using meeting bookings within ten days as the outcome. The chapter makes no causal or deal-recovery claim.https://www.gong.io/blog/this-surprising-cold-email-cta-will-help-you-book-a-lot-more-meetings That outcome can help assess an email's ability to secure a meeting. It cannot tell you whether a stalled purchase became viable or why a particular buyer went quiet.
Keep the purpose of your follow-up equally clear. A meeting can be helpful, but so can a corrected document or an explicit decision to pause. Judge the response by what it lets you understand or do next.
Give one stalled deal a clear next step
Use the evidence you have to complete a short review. The examples here are hypothetical and show different responses to different information; they are not a scoring system for identifying serious buyers.
| Last buyer-confirmed fact | Question still open | Useful response | What would count as progress |
|---|---|---|---|
| Operations raised migration workload concerns | Can the buyer do the work required? | Send the task split and offer a focused feasibility review | Operations confirms what is workable or identifies what must change |
| Purchase is conditional on security; questionnaire not received | Who needs which input before review can begin? | Confirm recipient and complete the submission through the agreed route | Receipt confirmed, then review completed or a specific issue returned |
| Merger work has displaced the reporting project | Is there a real restart condition? | Acknowledge the pause and ask whether a later event would make contact useful | A restart condition is confirmed, or uncertainty is recorded honestly |
| Agreed scope review is unconfirmed; messages unanswered | Is the review still wanted? | Recap the agreement and ask one short status question | Buyer clarifies the situation; no reply leaves the cause unknown |
Bring the stalled deal and your last exchange to founder-led sales coaching if you'd like help deciding what to ask next.
For your own deal, add the date of the last confirmed fact, the person responsible for the next step and any input they need. Mark a proposed action as proposed until the buyer agrees to it. An owner you have guessed is still an unknown.
This sits within Capture on the PACED map: getting from interest through a purchase. Knowing which part has stopped helps you choose where to intervene. Adding leads cannot complete a missing approval inside an existing opportunity.
Keep the note in your pipeline review. Use your sales-stage exit criteria to check whether the new evidence supports advancing the deal. A friendly reply alone does not settle that question.
After a win or loss, use Deal Forensics to revisit what happened. The Decision Audit asks whether your decisions were justified by the evidence available at the time.55 PacedRevenue framework registry. Canonical definitions of Capture, Stall Signals, Deal Forensics and The Decision Audit.https://pacedrevenue.com/insights/pipeline-physics/glossary/ Find one question you would ask earlier next time, using the original notes to check your memory.
For the separate decision about how much custom work an opportunity deserves, use pipeline hygiene. If you need to locate a wider problem in the revenue process, the free PACED diagnostic provides a starting point.
Start with one quiet deal. Write the last confirmed fact and the question you still need answered. Make your next message serve that question.
