Skip to content
VIVIDSELLING
OS
Menu

Field notesTech Sales · Stalled decisions

When Deals Go Quiet: Find the Missing Decision Work

Review an undefined next step, a case that does not travel and an unclear comparison; use VIVID architecture and The Observer to find what to do next.

Start reading
Key Takeaways
  • Silence does not reveal a universal deal-death deadline. Review the buyer’s process and last agreed action.
  • Three useful review patterns are an undefined next step, missing material for other participants and an unclear comparison.
  • A run card can record confirmed decision work and open questions; it is an article planning aid, not another canonical VIVID layer.
  • Use a specific follow-up tied to the buyer’s criteria, then distinguish confirmed facts, inference and forecast uncertainty.

The meeting felt promising. A proposal was sent. The CRM records views and opens. Then no reply. “Still waiting” becomes the forecast, even though nobody can name what the buyer is waiting to evaluate.

A quiet opportunity may be delayed, lost, deprioritized or still under review. There is no supported universal window in which it becomes dead, and activity tracking does not measure conviction. The useful question is more concrete: what decision work was established, what remains unknown and what next action was actually agreed?

Pattern 1: the next step has no owner or purpose

“Let's speak next week” can leave each person with a different expectation. A useful next step names an action, its owner, the material or question involved and the timing. It also explains what the step is intended to establish.

“I will send the revised implementation outline Thursday. You will review the manager time requirement with operations. On Tuesday we will compare the open questions” is a process both people can recognize. It still depends on their agreement and circumstances. A calendar invitation does not create commitment to purchase.

In VIVID terms, inspect Decision: was there a real choice about the next action, or did you interpret enthusiasm as agreement? Also inspect the upstream phases. If Vision and Identify remain vague, the next meeting may have little priority even when the calendar is clear.

Pattern 2: the case does not travel

The person on the call may understand the value while a colleague sees only price and effort. This is not evidence that the colleague is obstructive or the buyer is incapable. They are evaluating without the context of the conversation.

Use Proxy GP to connect personal conviction with transferable reasoning. Ask what the absent people will need to judge. Give the buyer the mechanism, relevant evidence, investment, implementation responsibilities, risks and unresolved questions. Let them express the case in their own words and correct your summary.

A joint review can be useful when they want one. Do not assume a sponsor can or should reproduce your emotional arc internally. An organizational decision usually needs evidence that can be examined by people who were never on the call.

Pattern 3: the comparison lacks concrete edges

“We improve performance” gives a buyer little to compare. Explain the actual deliverables, how the work operates, what it requires, how progress would be assessed and what is outside scope. Specificity makes the choice inspectable; it does not establish superiority.

Separate deliverables from projected outcomes. “We run four manager workshops and review one call per rep each week” describes work. “You will increase revenue by a stated percentage” is a result claim that needs evidence and conditions. Do not make an unsupported promise merely because a competitor's proposal sounds concrete.

Three review patterns and the missing work
Undefined next step
Clarify action, owner, purpose and timing.
Case does not travel
Prepare relevant reasoning and evidence for other participants.
Unclear comparison
Make scope, mechanism, requirements and unknowns explicit.

These are review prompts for this article, not exhaustive causes of a stalled deal.

A worked conversation before the quiet begins

This fictional example concerns an organizational training decision.

Buyer: This looks strong. Send the proposal and I will get back to you.

Seller: What will you need to evaluate once you have it?

Buyer: I need finance and the sales director to agree.

Seller: What is likely to matter most to each of them?

Buyer: Finance will ask what the full commitment is. The director will ask whether managers can fit it in.

Seller: Then the proposal should separate fees from the team's time requirement. Have you and the director agreed what time could be available?

Buyer: Not yet. That may be the difficult part.

Seller: Would it be useful to test that requirement together before a full proposal review?

Buyer: Yes. I can speak to her Monday. Send the routine and preparation first.

Seller: I will send those Friday. After you speak Monday, would Tuesday be a useful time to review what remains?

Buyer: Tuesday afternoon. If the routine does not fit, we should stop there.

What the architecture exposes: positive language did not establish manager capacity. The seller maps the decision structure, prepares material that can travel and makes the implementation comparison explicit. Tuesday has a purpose: evaluate whether the routine fits. This is stronger evidence for a forecast than “they seemed excited,” while still leaving the result uncertain.

Follow up on the question, not on an invented decay clock

If the agreed update does not arrive, refer to the actual work: “You planned to discuss manager time on Monday. Is that review still in progress, or has the priority changed?” Offer the relevant missing help if appropriate.

A response can clarify the process. No response leaves the reason unknown. Do not use a memory test—asking the buyer to repeat a number from the call—as a measure of whether conviction is alive. Nor should you repeatedly send messages because an arbitrary forty-eight-hour window is supposedly closing.

If the buyer declines, close the loop. If they ask for a later date, record what changes by then. If there is no agreed process and no further response, reflect that uncertainty in the forecast rather than leaving an optimistic stage untouched.

Use a run card to make unknowns visible

A simple run card is a planning aid for this article. It can sit in a CRM note or on paper. It is not a separate named book framework or an automatic early-warning system.

  • Diagnosis: buyer-defined destination, current gap, causal belief, impact inputs and decision participants.
  • Proposal: relevant mechanism and evidence, clear scope, implementation effort, commercial terms and open questions.
  • Next evaluation: action, owner, material, purpose, timing and what would make proceeding inappropriate.

Mark each item confirmed, inferred or unknown. An unknown is a question to prepare, not proof of a failing deal. The card should help a manager ask, “What supports that forecast?” rather than replace uncertainty with a mechanical score.

Connect Architecture with The Observer

Layer 4, VIVID Architecture, structures Vision, Identify, Validate, Impact and Decision. Layer 7, The Observer, helps you notice what happened and learn from it. Review where your presentation outran diagnosis, where another person appeared late or where you treated a polite response as commitment.

Use the Five-Question Audio Debrief to extract one change. A Lost-Deal Autopsy can look across the seven system layers, but do not assign a cause you have no evidence for. Sometimes the offer lost because an alternative genuinely fit better.

Practice a more honest deal review

Choose three quiet opportunities. For each, write the last agreed action and the evidence for the current stage. Name one unknown and one useful question. Where no action was agreed, say so plainly.

Role-play the worked conversation with a buyer who does not want another meeting. Practice offering useful material without forcing a date, then recording the opportunity accurately. In the next forecast review, replace “good call” with the actual destination, requirement and decision work established.

Continue with VIVID call architecture, Consultative and Proxy GP and The Observer.

Common questions

When is a silent deal definitely dead?

Silence alone does not establish that. Use the buyer’s process, explicit decisions and evidence for the stage; reflect uncertainty honestly.

What replaces the forty-eight-hour conviction check?

A useful follow-up tied to the agreed action or unresolved criterion, sent according to the buyer’s process. It is not a test of memory or hidden intent.

What does a run card add to a CRM?

It organizes confirmed decision work, inferences and unknowns. It is a practical planning aid, not a guarantee that a deal will advance.

Put it into practice

Choose a conversation to practise.

Explore the lessons and practice for your selling environment, or try a conversation first.

Practise a reporting request that reveals an approval-rule problem and changes the demonstration.