Choose the right pipeline correction for a stalled deal
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A proposal has been sitting in the pipeline without progress. One reviewer moves it backward, another leaves it untouched, and a third marks it paused. Each action could be right—but not for the same evidence.
Start a stalled-deal review with what remains true about the buyer’s progress. Retain the stage when its entry criteria still hold. Correct it when those criteria were never met or have been reversed. Record a verified pause when the buyer confirms a genuine waiting period and the underlying stage remains valid.
Time without movement triggers the review; it does not determine the correction. The task is to distinguish achieved progress from an obstacle, a waiting condition or ordinary unfinished work. This review concerns pipeline state, not how to re-engage the buyer.
1. Establish what the current stage claims
Write down what must be true for an opportunity to occupy its current stage. Separate two kinds of criteria:
- Entry criteria: buyer evidence required to place the opportunity in the stage.
- Exit criteria: additional evidence required to move it forward.
A missing exit criterion usually means the deal has not advanced yet. A missing entry criterion calls its current position into question. Treating both as reasons to move backward makes the pipeline unstable; treating both as ordinary blockers leaves unsupported opportunities in advanced stages.
All companies, dates and deal details below are fictional worked examples. Assume this hypothetical pipeline:
- Discovery: the buyer has confirmed a problem and agreed to assess its requirements.
- Evaluation: the buyer has confirmed the requirements and an evaluation process.
- Commercial review: the buyer has accepted solution fit and agreed to review a defined commercial offer.
- Approval: the buyer has accepted commercial terms and identified the remaining internal approval route.
Use your own agreed definitions in practice. Sending a proposal is a seller activity; it does not, by itself, establish that the buyer has entered Commercial review.
2. Assemble a small evidence packet
Before discussing the correction, collect a compact record another reviewer can inspect:
- The current stage and evidence supporting each entry criterion.
- The criterion required for the next transition.
- Any confirmed change, unmet condition or waiting period.
- The source and date of each relevant confirmation.
- The person responsible for resolving missing or conflicting evidence.
Evidence might be a buyer message or a dated meeting note identifying who confirmed what. Separate direct confirmation from interpretation. An owner’s note that procurement is probably busy is not equivalent to the buyer confirming that procurement has suspended reviews.
Earlier evidence also needs context. A previous acceptance may remain reliable, but a newly announced requirement change warrants a check. Silence alone does not prove acceptance has been withdrawn.
If records conflict, preserve the conflict rather than selecting whichever version supports the preferred forecast. Mark the disputed criterion as unverified and assign responsibility for resolving it.
3. Use this filled stall-triage decision tree
The following reusable artifact is filled with hypothetical cases. Replace the names and evidence with your own records, but keep every branch—including the route where no specific blocker exists.
START: A stalled opportunity has been flagged for review. A. Do all current-stage entry criteria still hold? NO → Correct to the latest fully supported stage. Birch: Commercial review → Evaluation. Evidence: Buyer reopened solution-fit assessment after a workflow change; confirmed requirements and evaluation process remain valid. Cedar: Commercial review → Discovery. Evidence: Buyer confirms a problem and agreement to assess requirements. Requirements and an evaluation process were never agreed. UNKNOWN → Record the evidence gap; assign an owner and checkpoint. Elm: Earlier fit acceptance conflicts with an unverified change note. Do not label this a confirmed reversal or verified pause. YES → Continue to B. B. Has the buyer confirmed a waiting period with a release condition or dated checkpoint, without withdrawing the stage criteria? YES → Retain the supported stage; record a verified pause. Dune: Approval retained. Evidence: Accepted terms and approval route remain confirmed. Budget release expected 15 September; checkpoint 16 September. NO → Continue to C. UNKNOWN → Record the possible pause as unverified. Preserve the supported stage; assign an evidence-check owner and date. C. Is a specific unmet condition blocking the next transition? YES → Retain the supported stage; record the blocker. Aster: Commercial review retained. Evidence: Fit accepted and defined offer under review; payment terms remain unresolved. NO → Retain the supported stage. Record that no specific blocker or verified pause has been established. Check whether the stall flag reflects ordinary unfinished work. Fern: Evaluation retained. Evidence: Requirements and evaluation process remain confirmed; the agreed assessment is continuing, with no identified obstruction. UNKNOWN → Retain the supported stage; record the missing diagnosis. Assign a review owner and evidence-check date. Do not invent a blocker to complete the record.
The order matters: check stage validity before considering a pause. A confirmed waiting period cannot preserve an advanced stage whose entry criteria have been withdrawn.
The NO and UNKNOWN routes at the final question are different. NO means the review found no specific blocking condition. UNKNOWN means the available evidence cannot establish whether one exists. Neither justifies manufacturing a blocker from inactivity alone.
4. Retain the stage without inventing a blocker
In the hypothetical Aster case, the buyer has accepted solution fit and agreed to review the defined offer. Those facts support Commercial review. Payment terms remain unresolved, preventing the next transition to Approval.
A useful retained-stage entry contains:
- Stage: Commercial review, unchanged.
- Blocker: buyer acceptance of the payment schedule is missing.
- Evidence: the latest buyer-confirmed review note identifies the disputed schedule and preserves acceptance of fit.
- Clearance evidence: accepted commercial terms and an identified internal approval route.
- Responsibility: the deal owner maintains the evidence; the reviewer checks the stage interpretation.
Moving Aster to Evaluation would incorrectly suggest solution fit needs to be established again. Recording only “deal slow” would conceal the actual missing condition.
Fern illustrates a different outcome. Its requirements and evaluation process remain confirmed, and the agreed assessment is continuing. The review identifies no specific obstruction and no buyer-confirmed waiting period. Retain Evaluation and record that the inactivity flag appears to reflect unfinished assessment work, not an established blocker.
That finding is not a claim that Fern will progress. It simply avoids assigning a diagnosis the evidence does not support. If later evidence reveals an obstacle, update the diagnosis without rewriting what was known during this review.
5. Correct the stage only to a supported destination
Birch and Cedar both need stage corrections, but their histories differ.
Birch: a valid decision was reopened
Birch legitimately reached Commercial review. The buyer subsequently changed a workflow requirement and reopened the solution-fit assessment. The revised requirements and evaluation process are confirmed, but acceptance of fit no longer stands.
Evaluation is therefore supported. Record the move as a correction following a reopened decision, preserve the earlier acceptance in the history and identify the new fit decision required. Do not imply that Commercial review never happened.
Cedar: the original placement was premature
Cedar entered Commercial review because a seller sent a proposal. During the review, the buyer explicitly confirms both an operational problem and agreement to assess its requirements. The buyer also confirms that requirements and an evaluation process have not yet been agreed.
Those facts satisfy both Discovery entry criteria, but not Evaluation or Commercial review. The supported correction is therefore Commercial review to Discovery. Record premature stage assignment as the reason—not a buyer reversal.
This distinction makes the history useful: Birch reflects changed circumstances; Cedar reflects an incorrect stage interpretation. In either case, test every destination entry criterion. Moving backward by one stage is not a substitute for checking evidence.
If Cedar had confirmed only the problem, Discovery would remain unsupported under these definitions. The destination would need to stay unresolved until agreement to assess requirements was established, or the opportunity was handled under the team’s convention for records without a supported stage.
6. Record a pause only when waiting is verified
In the hypothetical Dune case, accepted commercial terms and the internal approval route remain confirmed. The buyer states that approval must wait for a budget release expected on 15 September, with a review checkpoint on 16 September.
Here is a filled review record that can also serve as a reusable structure:
- Opportunity: Dune.
- Previous state: Approval; flagged for inactivity.
- Supported stage: Approval.
- Evidence source and date: buyer finance contact’s meeting confirmation, 2 September.
- Stage evidence: commercial terms remain accepted; internal approval route remains identified.
- Diagnosis: verified waiting period for budget release.
- Correction: retain Approval and record the pause separately.
- Release evidence: buyer confirmation that the budget has been released.
- Checkpoint: 16 September; reassess if release is not confirmed.
- Owner: assigned deal owner.
- Remaining uncertainty: actual release date is not confirmed.
A checkpoint is a date to reassess the record, not proof that progress will resume. If it passes, obtain updated evidence or revise the diagnosis. Do not roll the pause forward automatically.
If your record structure uses a dedicated paused stage, preserve the last supported sales stage separately. This is a recommended record design, not a claim about available CRM fields. Check the workspace and current plan before relying on a particular implementation.
7. Handle ambiguity without disguising it as certainty
Elm has earlier acceptance of solution fit and a later internal note suggesting requirements may have changed. There is no confirmation of a reversal or waiting period.
Under a convention that allows temporary unresolved records, retain the last supported stage but explicitly mark its current validity as unverified. Assign an owner and an evidence-check date. Ensure reporting distinguishes that record from a freshly validated opportunity. If your conventions require another treatment, make the uncertainty equally visible.
Check for these common correction errors:
- Every stall becomes a backward move: restore the supported stage if only an exit criterion was missing.
- Every delay becomes a pause: remove verified status when buyer confirmation is absent.
- A pause hides a reversal: correct the underlying stage before assessing any waiting condition.
- No movement becomes proof of a blocker: distinguish an identified obstruction from unfinished work or missing diagnosis.
Keep the previous state, revised state, evidence, date and reviewer in the correction history. Also check any related forecast or expected-close assumptions; changing a stage does not establish that every associated record has been reviewed.
8. Check whether the review improved the records
For a hypothetical pilot, apply the tree to six already-flagged opportunities. Use one review record per opportunity, following Dune’s filled structure and adapting the diagnosis.
Then count how many records meet these observable checks:
- Every retained or corrected stage has evidence for all entry criteria.
- Every blocker names a specific unmet condition.
- Every verified pause has buyer confirmation and a release condition or checkpoint.
- Every no-blocker finding distinguishes ordinary unfinished work from a verified pause.
- Every unresolved case has an owner and evidence-check date.
- Every correction explains what changed without erasing the earlier history.
These checks measure record quality, not sales improvement. The immediate useful outcome is that another reviewer can understand the pipeline state without relying on the owner’s memory. Where reviewers disagree, identify the exact criterion or evidence interpretation at issue; that is the next definition or recordkeeping practice to improve.
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