Back to all articlesSales pipeline design

Define stalled deals using stage context rather than one universal timeout

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A deal waiting for a scheduled procurement review can be healthy despite weeks of silence. Another can receive daily seller attention while the buyer has stopped moving toward a decision. A universal inactivity threshold treats the first as a problem and may overlook the second.

To identify stalled deals, combine time in stage, the next buyer milestone, evidence freshness, and documented waiting periods. Use elapsed time to trigger inspection, not to declare every old opportunity stalled.

The goal is a classification another reviewer can defend: progressing, waiting with evidence, stalled, or insufficient evidence. Crucially, an unrecorded outcome is not necessarily a missed milestone. The review may have happened without its result reaching the seller.

1. Define a stall as a broken path to buyer progress

Activity records what people did. Progress records what changed in the buyer’s decision process. Sending a proposal, logging a call, or editing a close date can create recent activity without establishing a new buyer commitment.

A useful definition is: a deal is stalled when evidence establishes that an expected buyer milestone was missed or blocked, with no supported continuation or revised plan. Knowing why progress stopped does not make the deal healthy. A required test owner withdrawing explains a blockage; it does not resolve it.

Use four classifications:

  • Progressing: Current evidence supports movement toward the next buyer milestone.
  • Waiting with evidence: Progress is paused for a specific dependency or scheduled event, with a responsible owner, a supported route to resumption, and a review checkpoint.
  • Stalled: Evidence establishes a missed or blocked milestone, and no supported continuation exists.
  • Insufficient evidence: The available record cannot establish progress, a supported wait, or a stall.

A supported wait connects the delay to a credible next event. Missing information is different: it requires investigation but does not, by itself, prove buyer disengagement. A deal can move from waiting with evidence to insufficient evidence when its checkpoint passes and the outcome remains unknown.

2. Give each stage an observable buyer milestone

Before setting time thresholds, describe what must happen for each stage to be complete. Prefer a buyer action or verified change in the decision process over a seller task.

For discovery, the milestone might be confirmation of the problem and agreement on evaluation participants. For evaluation, it might be completion of agreed tests. For commercial review, it might be confirmation of the approval route and unresolved terms.

Write milestones so another person can inspect their evidence. “Buyer remains interested” is difficult to test. “Buyer confirmed the evaluation criteria and named the person reviewing results” is observable.

Keep these fields together:

  • Current stage and stage-entry date.
  • Next buyer milestone, its owner, and expected date.
  • Whether that date is buyer-confirmed or a seller estimate.
  • Latest supporting evidence, its date, and what it establishes.
  • Any waiting reason, route to resumption, and review checkpoint.
  • Any separate buyer commitment to report an outcome.

That last distinction matters. Completing a review and telling the seller its result are different milestones. A seller’s internal inspection date is not automatically a buyer commitment to provide an update.

A seller estimate can trigger inspection, but should not be presented as a broken buyer commitment. If a stage contains different types of work, give its rules separate branches rather than forcing every deal through the same timing assumption.

3. Read four signals together

Time in stage

Stage age identifies deals worth examining; it does not explain why they are old. Retain the original entry date during a legitimate wait so the pause does not conceal the opportunity’s total age.

Expected buyer milestone

A verified missed buyer-agreed date can justify review before the stage-age threshold. A younger deal can also be stalled when a required dependency fails, even if its planned completion date has not arrived. If completion is merely unknown, investigate rather than infer failure from silence.

Evidence freshness

Evidence is fresh when it still supports the current classification. Confirmation that a committee meeting remains scheduled can support a wait. An older statement praising a demonstration may not support a claim that approval is advancing.

Do not refresh buyer evidence merely because a seller sends a message or edits a field. A review date and an evidence date are separate: inspecting an old note does not make its contents current.

Supported waiting periods

A valid wait needs a specific reason, responsible party, bounded expectation, and checkpoint. “Procurement takes time” is not enough. Confirmation that a complete submission is scheduled for review provides a stronger basis.

When that checkpoint arrives, reassess the classification. The existing wait cannot continue indefinitely on its original evidence. But its expiry establishes only that the wait needs renewed support—not that the buyer missed the underlying milestone.

4. Reuse this filled stage-rule worksheet

All organizations, thresholds, dates, and deal details below are hypothetical. These fictional worked examples are recommended operating rules, not benchmarks or Alactic customer results. Day counts mean business days. Timing thresholds prompt inspection; they do not automatically determine classification.

Discovery: Alder Services

  • Milestone: Buyer confirms the problem and agrees who should participate in evaluation.
  • Review triggers: After 6 days in stage, when a buyer-agreed milestone is 2 days overdue, or after 4 days without supporting buyer evidence.
  • Filled record: Day 8 in stage. Buyer agreed to confirm participants on day 5. On day 7, the buyer confirmed that participants remain undecided, with no owner or revised plan. A seller sent material yesterday. The problem-confirmation field is incomplete.
  • Classification: Stalled. The buyer’s update establishes the missed milestone and unsupported continuation. Seller activity does not repair it.
  • Counterexample: If the record contains only the planned date and unanswered seller messages, with no evidence establishing whether participants were confirmed, classify as insufficient evidence.
  • Why this timing: This fictional stage expects prompt agreement on the buying problem and who should examine it.

Evaluation: Beacon Works

  • Milestone: Buyer completes agreed tests and confirms which acceptance criteria were met.
  • Review triggers: After 15 days in stage, when a test checkpoint is 2 days past due, or after 7 days without confirmation that testing follows the plan. Inspect a confirmed blocked prerequisite immediately.
  • Filled record: Day 12 in stage. Buyer confirmed 3 days ago that testing is underway, with results expected on day 16.
  • Classification: Progressing. Recent evidence supports work toward a milestone that is not yet due.
  • Counterexample: A separate evaluation is only 5 days old, but its required test owner withdrew. No replacement or revised test plan exists. Classify as stalled because the prerequisite is demonstrably blocked.
  • Why this timing: Evaluation allows time for agreed work while checking whether its dependencies remain intact. An overdue checkpoint with unknown test status requires investigation, not an automatic stall label.

Commercial review: Cedar Supply

  • Milestone: Buyer confirms the approval route, unresolved terms, and next decision checkpoint.
  • Review triggers: After 10 days in stage, when an agreed approval checkpoint passes, or after 5 days without current approval evidence.
  • Filled record: Day 11 in stage. Buyer acknowledged receipt yesterday, but the record identifies neither an approver nor a decision checkpoint.
  • Classification: Insufficient evidence. Receipt alone establishes neither progress nor a missed commitment.
  • Counterexample: If the buyer confirms that a scheduled approval meeting was cancelled and there is no replacement date or supported continuation, classify as stalled. If the meeting date passed but its outcome is unknown, classify as insufficient evidence instead.
  • Why this timing: A recent acknowledgement should not conceal an undefined approval process, but missing documentation must not become proof of a failed approval.

Procurement review: Delta Manufacturing

  • Milestone: Buyer-side reviewer completes the scheduled review or identifies specific outstanding requirements.
  • Review triggers: After 25 days in stage, at the agreed post-review checkpoint, or immediately on evidence of a blockage.
  • Filled record: Day 19 in stage. The buyer-side owner confirmed the submission is complete, with review scheduled on day 23. The seller set an internal inspection checkpoint for day 24. The buyer has not separately committed to report the outcome by that date.
  • Current classification: Waiting with evidence. The scheduled review supports a bounded pause until the checkpoint.
  • Day-24 decision: Expire the existing supported-wait classification and inspect the evidence. A confirmed completed review with an actionable next step supports progressing. A buyer-supported replacement schedule may justify a new bounded wait. A verified missed review or blocking requirement with no supported continuation establishes stalled. If it is unknown whether the review happened, classify as insufficient evidence.
  • Counterexample: A procurement deal only 9 days old has a returned requirement blocking review, with no responsible owner or recovery plan. Classify as stalled despite knowing the reason.
  • Why this timing: Scheduled external review supports a longer age threshold, but never overrides an earlier verified blockage.

5. Work the procurement checkpoint through to a decision

Use Delta’s filled record as a reusable checkpoint note. The hypothetical day-24 inspection finds no review result in the seller’s record and no new buyer message.

  • Prior classification: Waiting with evidence.
  • Checkpoint reached: Day 24; original wait support has expired.
  • Known facts: Submission was confirmed complete; review was scheduled for day 23.
  • Unknown fact: Whether the review occurred and what it concluded.
  • Reporting commitment: None recorded; day 24 was an internal inspection date.
  • New classification: Insufficient evidence.
  • Reason: The record cannot establish either continued progress or a missed review.
  • Evidence needed: Confirmation of review completion, a revised schedule, or a specific blocker.
  • Accountable reviewer: Opportunity owner; retain the original evidence date and stage-entry date.

This decision avoids two errors: continuing a wait after its support expires and treating seller uncertainty as buyer failure. If subsequent confirmation establishes that the review was cancelled with no replacement plan, the classification becomes stalled.

If the buyer had explicitly agreed to provide the outcome by day 24, verified non-receipt could establish a missed reporting milestone. Record it as such—not as proof that the review itself failed to occur. Check for a supported continuation before classifying the deal as stalled.

6. Apply evidence precedence, not field-completion precedence

Use a consistent review sequence:

  1. Identify the milestone. Separate buyer commitments, seller estimates, internal inspections, and reporting commitments.
  2. Establish what happened. Distinguish completed work, verified misses, confirmed blockers, and unknown outcomes.
  3. Test continuation. Look for an owner, supporting evidence, expected resumption, and checkpoint.
  4. Assess freshness and age. Expired evidence prompts inspection; it does not substitute for facts.
  5. Record the classification and reason. Note remaining uncertainty separately.

A missing field does not automatically require insufficient evidence. Alder’s buyer-confirmed missed commitment establishes a stall despite incomplete problem documentation. Conversely, a complete record of old notes may still leave the current outcome unknown.

Keep exceptions bounded and visible. Preserve stage history so moving a deal between stages does not erase delay. Keep seller activity separate from buyer evidence. Do not extend waiting dates merely because the seller remains optimistic. A revised plan needs support that addresses the original dependency.

Finally, stalled does not mean lost. It describes the current path to progress, not an automatic decision to close the opportunity.

7. Calibrate with reviewed cases before expanding

Start with provisional rules and compare their classifications with human review. In a hypothetical pilot, inspect 20 opportunities across 2 weekly reviews, including flagged and unflagged deals. Reviewing only alerts cannot expose stalls the rules missed.

Count confirmed stalls, supported waits, unknown outcomes, and stalls found among unflagged deals. Check whether reviewers reach the same conclusion from the same evidence. Pay particular attention to cases where “no update” was incorrectly interpreted as “milestone missed.”

If scheduled evaluations generate false alarms, refine their waiting criteria. If missed stalls involve broken commitments, strengthen milestone checks. If disagreement comes from missing information, improve evidence requirements before changing timing thresholds.

Implement one disputed stage first. Copy the worksheet fields into your review process; if using a CRM, check the workspace and current plan for available recording options rather than assuming a particular control exists. The first observable outcome is a set of defensible classifications and explicit evidence gaps—not a claimed reduction in stalled deals.

Sales pipeline designDeal reviewsCRM operating practices

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