Require only the pipeline fields needed for the current stage
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
An opportunity record demands a final amount, a decision-maker, and a purchase date after the first conversation. None is known, so the salesperson enters plausible answers. Later, those placeholders look like confirmed facts.
Making everything optional creates the opposite problem: advanced deals lack evidence that the buyer is evaluating an offer or has a decision process.
The practical alternative is to require information when it becomes decision-relevant. Allow explicit uncertainty earlier, define evidence for later stages, and block unsupported advancement rather than honest record creation. A stage-by-field matrix makes those rules consistent across sellers and managers.
1. Define the decision each requirement protects
Start with what a stage claims, not a list of empty fields. For each proposed requirement, complete this sentence: Without this information, we cannot responsibly decide whether to... Possible endings include prepare a defined offer, treat an offer as actively under consideration, or record an opportunity as won.
If there is no clear ending, the field may be useful reporting detail rather than an advancement requirement.
Separate three moments:
- Creation: Identify the opportunity, assign responsibility, and establish a next action.
- Stage entry: Establish evidence for the state being claimed.
- Maintenance: Check that evidence remains current while the opportunity stays in that state.
A buyer can change scope or timing after a stage-entry check passes. Requirements therefore need review rules, not just one-time completion checks. This exercise supports existing stage definitions; it need not become a redesign of the entire qualification process.
2. Distinguish unknown from missing and estimated
A blank does not show whether anyone asked the question. Use explicit states:
- Missing: No usable answer or explanation exists.
- Unknown: The answer is unresolved; record the question, investigation owner, and follow-up date.
- Estimated: A working value exists with a stated basis, but is not buyer-confirmed.
- Confirmed: A relevant source supports the value, with a reviewable reference.
- Not applicable: The requirement does not apply, with an assessable reason.
These states are not interchangeable. An unknown decision target can be acceptable during exploration but insufficient for a stage that claims an established decision timetable. An estimate must remain labelled even when a reporting view needs a single number.
Do not let unknown become a permanent escape hatch. Wherever the matrix permits it, require an owner and dated follow-up. Where it does not, retain the earlier stage instead of manufacturing certainty.
3. Use this filled stage-by-field matrix
Hypothetical reusable artifact: All companies, people, amounts, dates, and events below are fictional examples, not Alactic customer results. The fictional stages are Open, Exploration, Proposal, Decision, and Won. Proposal means a defined offer is ready for buyer evaluation; Decision means the buyer is actively resolving it; Won requires the team's defined acceptance evidence.
Reading rule: Every cell states its status. Required means the stated evidence must exist. Unknown allowed always includes an owner and dated follow-up. Retained means preserve the existing value and evidence rather than replacing them with a different fact.
| Field | Open | Exploration | Proposal | Decision | Won |
|---|---|---|---|---|---|
| Identity and owner | Required: Cedar Works — scheduling project; owner Maya. | Required: retain identity and current owner. | Required: retain identity and current owner. | Required: retain identity and current owner. | Required: retain identity and accountable record owner. |
| Buyer context and outcome | Required, provisional allowed: scheduling requests span separate inboxes; impact unverified. | Required, buyer-sourced: Priya wants an agreed assignment process. | Required: outcome aligned with offered scope. | Required: current outcome; explain changed priorities. | Required: retain outcome associated with accepted scope. |
| Contacts and evaluation roles | Required: named contact or identified route to a buyer conversation. | Required: Priya, operations manager, engaged in evaluation. | Required: engaged evaluation coordinator, known evaluator roles, and a source identifying who will assess the offer. Unknown final approval authority allowed with follow-up. | Required: relevant approval role and route to decision, supported by buyer evidence. | Required: acceptance source and relevant accepting role. |
| Amount and basis | Unknown allowed with follow-up. | Unknown allowed with follow-up; estimate allowed with basis. Example: 12,000–18,000 currency units from preliminary scope. | Required: offered amount 15,000 currency units; proposal B reference. | Required: current offered amount; identify unresolved changes. | Required: accepted amount 14,500 currency units; retain prior offer references. |
| Target decision date and evidence | Unknown allowed with follow-up. | Unknown allowed with follow-up; estimate allowed only with stated basis. | Required timing status: buyer target, labelled seller estimate, or unresolved. Unknown date allowed with follow-up. | Required: buyer target 18 September, subject to finance review; buyer meeting note dated 6 September. | Retained: final target 18 September and its evidence. No longer an advancement gate after closure. |
| Actual acceptance date | Not required; leave unset. | Not required; leave unset. | Not required; leave unset. | Not required; leave unset. | Required: 22 September, supported by acceptance reference. Separate from target decision date. |
| Scope and offer evidence | Unknown boundaries allowed with follow-up. | Incomplete scope allowed with follow-up on unresolved boundaries. | Required: two scheduling teams; proposal B shared with Priya; retrievable reference. | Required: current offer reference and open scope changes. | Required: accepted scope and version reference. |
| Decision process and dependencies | Not required. | Unknown allowed with follow-up. | Required: known steps and explicit gaps. Operations review known; finance sequence unknown, Maya to investigate on 9 September. | Required: current sequence, responsible buyer roles, and open dependencies consistent with active evaluation. | Required: evidence of completed acceptance steps; preserve process history. |
| Next action and closure evidence | Required: Maya to arrange discovery on 3 September. | Required: Maya to clarify scope on 6 September. | Required: Maya to confirm finance reviewer on 9 September. | Required: Maya to confirm review outcome on 18 September. | Required: acceptance reference and named handoff owner; sales follow-up gate ends. |
For the Proposal contact gate, a title alone is insufficient. Minimum evidence is a buyer interaction or communication identifying the engaged coordinator and the known roles assessing the offer. In this example, Priya confirms that she coordinates evaluation and operations will assess workflow fit. Final approval authority may remain unknown, but must have a follow-up. If nobody has established who will evaluate the offer, the gate fails.
Unacceptable substitutes: an unassigned owner; “needs our product” as buyer context; a senior title assumed to prove authority; zero meaning unknown amount; quarter-end presented as buyer timing; an unshared draft presented as an active offer; “standard procurement” without investigated steps; and “follow up” without an owner and date. Internal optimism is not acceptance evidence.
4. Walk one opportunity through the gates
Hypothetical worked example: Maya requests Proposal entry for Cedar Works. Proposal B covers two scheduling teams at 15,000 currency units. Priya has confirmed she coordinates evaluation and operations will assess workflow fit. Finance approval authority remains unknown. The record assigns Maya to clarify that role on 9 September.
The opportunity passes Proposal: a defined offer, evaluation roles, and explicit process gaps exist. The unknown approval authority is permitted here. Its decision date is also unresolved, with follow-up, rather than filled with the seller's preferred month-end.
Maya then requests Decision entry without updating approval evidence. That request fails: Proposal permitted the unknown, but Decision requires a supported approval role and route. The recovery action is to ask Priya who approves and what review remains—not to guess a finance contact.
Later, Priya identifies the finance reviewer and sequence, with an 18 September decision target subject to finance review. Decision entry now passes. Acceptance arrives on 22 September for 14,500 currency units after a documented scope adjustment.
The closed record retains the final 18 September target and supporting note, records 22 September separately as actual acceptance, and references the accepted amount and scope. The target was missed by four calendar days in this hypothetical example. Replacing it with the acceptance date would erase that distinction.
If the buyer revises a target before closure, preserve the previous target and change evidence as well as the current value. At Won, timing evidence becomes historical context rather than a continuing advancement gate. A missed target does not invalidate otherwise sufficient acceptance evidence.
5. Keep evidence compact but reviewable
Require enough context to establish a claim and find its support, not a dossier. A useful evidence entry records source, date, substance, and reference.
For the fictional timing example: Priya; buyer meeting on 6 September; decision expected on 18 September after finance review; linked meeting note. This is more informative than an unexplained September date without requiring a transcript.
Match evidence to the claim. An internal estimate can support a working amount, not buyer acceptance. A shared proposal establishes what was offered, not what was agreed. Preserve those distinctions even if reporting eventually displays only the accepted amount.
Use concise summaries and references accessible to authorised reviewers. When evidence cannot be reviewed, resolve access or reference problems rather than repeatedly copying entire conversations into fields.
6. Make failures and exceptions actionable
Apply the gate when someone requests stage entry. A useful failure explains the unsupported claim and recovery action: approval route unknown; identify the relevant buyer role or remain in Proposal. “Required fields incomplete” gives little help.
Distinguish unresolved commercial issues from missing evidence of evaluation. An actively considered price change can fit Decision when the issue, owner, and resolution step are visible. No evidence that the buyer is reviewing the offer undermines the stage itself.
For a legitimate exception, record the missing requirement, reason, approving owner, review date, and reporting treatment. Approval of an exception does not make an unknown fact confirmed.
Recheck maintenance requirements when scope, buyer roles, or timing change. If evidence no longer supports the stage, use a visible correction or time-bound exception rather than silently preserving the old claim.
7. Repair existing records without rewarding guesses
Do not demand instant completeness across the historical pipeline. That recreates the incentive to invent answers. Review advanced opportunities first and separate absent evidence from information known to be wrong.
- Replace placeholder amounts and dates with explicit unknowns or labelled estimates.
- Check whether the current stage still meets its requirements.
- Move unsupported opportunities back or document an approved, time-bound exception.
- Assign the next buyer question or verification task with an owner and date.
Treat honest stage regression as correction of the shared picture, not automatically as poor performance. Otherwise, sellers have an incentive to protect unsupported entries.
Keep the matrix small. Add requirements only when they affect stage meaning, resource allocation, forecast interpretation, or handoff. Use reasoned not-applicable states for genuinely conditional requirements, not fabricated values.
This is an operating design, not a claim about an Alactic control. Check your workspace and current plan for available implementation options; a documented review process can establish the rule before automated enforcement is considered.
8. Pilot for honesty, not just completeness
Start with one stage boundary and a declared sample of opportunities. A hypothetical two-week pilot could track:
- Unsupported advancement: reviewed stage entries lacking required evidence.
- False completeness: filled fields containing placeholders or stale claims.
- Gate friction: blocks exposing real gaps versus premature demands.
- Unknown resolution: follow-ups reaching their date without an update.
- Early-record friction: opportunities recorded late because creation requirements are excessive.
Record counts alongside the number reviewed. More explicit unknowns and backward corrections can initially indicate a more honest pipeline. Remove requirements that do not change the stage decision, and tighten evidence rules where completed fields still fail to establish 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