Decide Whether a Quiet Opportunity Is Lost or Dormant
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A buyer stops replying after receiving a proposal. One seller marks the opportunity lost; another leaves it open indefinitely. Both are making a classification without establishing what happened to the purchase.
Use three evidence-based outcomes: confirmed loss means the buying decision ended without your offer being selected; credible dormancy means the same decision is paused for a supported reason; unresolved outcome means neither conclusion is established. Elapsed time can prompt a review, but it is not proof of an outcome.
The method below separates the facts from the interpretation. It covers outcome classification, not follow-up schedules, pipeline stages, or forecast probabilities. All cases and example records are fictional and hypothetical.
1. Define the buying decision before classifying it
An opportunity should represent a particular purchase: a defined need, proposed scope, and buyer or buying group. An account name is not enough. The same organisation may reject one proposal, pause another project, and continue evaluating a third.
For example, a hypothetical manufacturer's decision could be whether to replace the scheduling system at its existing production site. A competitor purchase at another site would not necessarily settle that decision.
Write the scope in a sentence before reviewing the evidence. Include the purchase and organisational boundary that matter. This prevents a broad account-level impression from becoming a specific opportunity outcome.
Then check whether the decision is actually inactive. If evidence confirms that evaluation is continuing, keep the appropriate active classification rather than forcing it into one of these three outcomes. This method resolves uncertainty about quiet purchases; it does not replace all operating statuses.
Also distinguish relationship evidence from decision evidence. A friendly contact may confirm a loss. A dissatisfied contact may still be considering a revised offer. Responsiveness, goodwill, and enthusiasm can inform account management without determining whether this purchase ended.
2. Set a minimum evidence threshold for each outcome
Confirmed loss: an ended decision
Suitable evidence includes a responsible buyer confirming that the final offer was rejected, another supplier was selected for the same scope, or the purchase was abandoned. Record the outcome separately from its reason. A decision to buy nothing is not a competitor win.
Test the statement's limits. Rejection of a pricing document may mean a revision is required. Selection of a supplier for a pilot may not settle an organisation-wide purchase. The evidence must establish that consideration of your offer has ended for the decision you are recording.
Credible dormancy: a supported pause
Dormancy requires positive evidence of a continuing need, an identifiable blocker, and a credible condition for reconsideration. That condition should be recognised by someone involved in the decision, rather than supplied by the seller.
A restart date is not essential. Completion of a site review or appointment of a project owner can be a meaningful condition. A general willingness to talk again is weaker: it does not establish that the original purchase remains relevant or explain what would restart it.
Unresolved outcome: insufficient or conflicting evidence
Use unresolved when the available records do not support either threshold. Typical cases include unanswered proposals, second-hand reports, and conflicting accounts that cannot yet be reconciled.
Unresolved does not mean unlimited seller attention. A team can remove a record from current work while preserving uncertainty about its outcome. Operational prioritisation and evidence classification are separate decisions.
3. Compare cases using this filled decision table
Hypothetical decision table: Use these cases as a review reference. Each row includes the limits of the evidence, not just a recommended label.
| Case | Known evidence | Status | Evidence gaps | Review conditions |
|---|---|---|---|---|
| A: Unanswered messages | A proposal was sent. Subsequent messages received no response. No buyer statement establishes what happened to the purchase. | Unresolved outcome. The record establishes an inactive conversation, not an ended or paused decision. | Whether the proposal was considered, the project still exists, another supplier was selected, or the contact still owns the decision. | Reclassify when credible evidence establishes an ended decision, continuing evaluation, or a supported pause. An internal review date prompts inspection; it does not resolve the gaps. |
| B: Confirmed project pause | The sponsor confirms that the requirement remains, evaluation is suspended pending a site-consolidation review, and the sponsor still owns the project. | Credible dormancy. A continuing need, blocker, and reconsideration condition are established. | Whether the review will preserve the original scope and whether funding will remain available afterward. | Reassess when the review finishes, the sponsor changes, or the purpose changes. If a checkpoint passes, check whether the pause evidence remains credible rather than automatically recording a loss. |
| C: Rejected final proposal | The responsible buyer confirms that the final offer was not selected, selection is complete, and no revised offer is under consideration. | Confirmed loss for this decision. | The reason may remain unknown. Price, product fit, and competitor selection must not be assumed. | Correct the record if the statement was misunderstood. A later purchase with materially different scope or authorisation should be distinguished as a new decision. |
| D: Reported competitor purchase | A contact outside procurement reports hearing that another supplier was purchased. The contact's basis for the report is unknown. | Unresolved outcome, with an unverified competitor-selection note. | Whether a purchase occurred, who made it, and whether it covers this scope rather than a pilot or another department. | Confirmed selection for the same scope supports loss. A purchase for another project does not settle this opportunity. Resolve both source reliability and scope before changing the status. |
The table is a classification aid, not a substitute for the underlying record. Preserve enough source detail for another reviewer to understand why the selected row fits.
4. Work through a case and save a reusable decision note
Consider a hypothetical seller reviewing the paused scheduling-system purchase in Case B. The existing record says only that the buyer expects to return later. That summary alone is insufficient for dormancy because it does not identify what is paused or why.
The reviewer finds a dated message from the project sponsor. It establishes that the existing site's scheduling requirement remains, evaluation is suspended during the site-consolidation review, and the sponsor still owns the project. It does not confirm future funding.
The reviewer applies the thresholds in order. There is no evidence of a final rejection or completed selection, so confirmed loss is unsupported. There is a continuing requirement, a named blocker, and a buyer-recognised reconsideration condition, so credible dormancy is supported. Unknown funding is retained as a gap rather than silently converted into either cancellation or an assured restart.
Filled reusable artifact — hypothetical decision note: Copy these field labels and replace the contents when reviewing another opportunity.
- Decision scope
- Replacement of the scheduling system at the buyer's existing production site; excludes systems for other sites.
- Evidence classification
- Credible dormancy.
- Supporting fact
- The sponsor confirmed that the requirement remains and evaluation is suspended pending completion of the site-consolidation review.
- Source and timing
- Project sponsor responsible for the purchase; message recorded on 12 March in this fictional example. The original message is referenced in the opportunity record.
- Interpretation
- The same purchase is paused behind an identified decision dependency. Resumption is possible but not assured.
- Evidence gaps
- Future funding and the effect of consolidation on the original scope are unknown.
- Review conditions
- Completion of the site review, a change in sponsor, or a change in the purchase's purpose or scope.
- Record owner
- Opportunity owner; responsible for maintaining the evidence note and recording unresolved gaps.
These are recommended recordkeeping fields, not claims about a particular product's controls. If your system only permits open and closed labels, preserve the evidence classification separately through an agreed, available method. Check your workspace and current plan before relying on a particular field or workflow. A system-required closure should not become an invented buyer rejection.
5. Reassess stale evidence and conflicting sources
A valid pause explanation can become insufficient. If the sponsor leaves or the underlying initiative changes, ask whether the original evidence still describes the same decision. Continued confirmation of the blocker supports dormancy; uncertainty about both the blocker and continuing need may justify unresolved status.
Use elapsed time to identify evidence that needs checking, not to choose the replacement label. A missed checkpoint tells you that a review is due, not what the buyer decided.
Conflicting accounts need a scope check before a credibility contest. In a hypothetical case, a sponsor reports a pause while procurement reports a supplier selection. Both may be describing different sites or different phases of the purchase.
If the scope matches, assess each source's direct knowledge and when the information was obtained. Seniority alone does not establish accuracy. A newer second-hand rumour does not necessarily outweigh an older direct statement, either.
When the conflict remains unresolved, record both accounts, their dates, and the missing fact needed to distinguish them. Assign an owner to that gap. Do not select the more optimistic account to preserve pipeline or the more pessimistic account to simplify reporting.
6. Repair shortcuts without rewriting history
Each category has a predictable failure mode: confirmed loss can hide unsupported certainty, dormancy can preserve hope, and unresolved can become an unattended holding area. Correct the underlying inference, not just the label.
- Silence recorded as a price rejection: Remove the unsupported reason. Use unresolved unless other evidence establishes loss.
- Vague future interest recorded as dormancy: Look for a continuing purchase, an actual blocker, and a recognised reconsideration condition. Without them, the pause is not established.
- A confirmed loss kept dormant because the relationship is strong: Record the ended decision accurately. The ongoing relationship belongs in account context.
- An old loss reopened for a different purchase: Preserve the earlier outcome and distinguish the new decision. Otherwise, historical loss analysis changes whenever a new opportunity appears.
Keep a brief correction note stating whether the change follows new evidence, clarified scope, or repair of an earlier assumption. This makes revisions understandable without treating every update as seller error.
Do not require a detailed loss reason as the price of recording a confirmed loss. The outcome can be known while the explanation remains unknown. Forcing a reason encourages plausible guesses that later appear to be facts.
7. Test the rules on a bounded review set
Start small enough to inspect the underlying evidence. As a hypothetical exercise, select twelve quiet opportunities spanning unanswered proposals, stated pauses, competitor reports, and recorded losses.
- Write the specific buying decision for each record.
- Have the owner assign an evidence classification and complete the decision note.
- Ask a second reviewer to classify the same evidence without relying on the existing label.
- Compare disagreements: identify whether they arise from scope, missing records, source reliability, or an unclear threshold.
- Record a responsible owner and review condition for dormant and unresolved cases, including inaccessible evidence that could not be checked.
Track agreement before discussion, records with adequate supporting evidence, cases with explicit review conditions, and unsupported loss reasons removed. These are checks on classification quality, not measures of sales performance.
The review target is a set of defensible classifications, not compulsory completeness. Missing records or inaccessible evidence may leave cases unresolved. A useful deliverable documents those gaps, assigns ownership, and states what evidence would justify a change. That makes uncertainty visible without pretending the review has eliminated it.
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