Define sales stages around buyer progress instead of seller activity
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A salesperson sends a proposal and moves an opportunity to the next stage. Another holds a demonstration and does the same. Neither buyer has confirmed that the offer solves their problem or explained how a decision will happen. The pipeline has moved; the buying process may not have.
To define sales pipeline stages around buyer progress, make each stage describe an observable buyer state, specify the evidence needed to enter it, and identify activities that do not count. Then give different staff the same deal evidence and check whether they assign the same stage.
The aim is not to eliminate judgment. It is to make judgment inspectable. A colleague should be able to understand why an opportunity occupies a stage without relying on the owner's confidence or memory.
1. Separate the buyer state from the work being done
A stage answers: What is now established about this buyer's purchasing process? A task answers: What should the seller do next? Mixing those questions produces stages such as Demo completed, Proposal sent, and Follow-up underway.
Those labels describe real work, but they do not establish what changed for the buyer. A demonstration can end with a confirmed fit, an unresolved requirement, or polite silence. Sending a proposal establishes that the seller sent something, not that the buyer is evaluating it.
A useful stage definition contains three parts:
- Buyer state: a condition that is true of the buying process.
- Entry evidence: something observable that supports that condition.
- Exclusions: activity or sentiment that must not be mistaken for that condition.
Prefer labels such as Problem confirmed or Solution fit confirmed over activity labels. However, a better name alone will not fix the pipeline. If staff can still enter Solution fit confirmed simply because a demonstration happened, only the label has changed.
This design starts with existing opportunities. It does not determine which leads qualify, prescribe task schedules, or assign forecast probabilities.
2. Choose boundaries that change your understanding of the purchase
A stage boundary is useful when crossing it establishes something materially different: the buyer has acknowledged a problem, agreed that a solution fits, begun a defined purchase decision, or accepted the commercial terms.
Do not create a separate stage for every document, meeting, or internal handoff. Conversely, do not compress distinct buyer states into one broad stage such as In progress. That makes an exploratory conversation indistinguishable from a purchase awaiting a final decision.
Write the evidence rule before finalizing the stage name. Ask: What could another person inspect to distinguish this state from the previous one? If the answer is only that the salesperson feels more confident, the boundary needs work.
Evidence need not be a formal document. A buyer email, a written exchange, or a meeting note that records who confirmed what can support classification. Notes should distinguish a buyer's statement from the seller's interpretation. A specific attributed confirmation is more useful than an unqualified entry saying that the meeting went well.
Allow evidence appropriate to the buying process. Requiring a procurement document from a buyer who has no procurement function creates paperwork, not clarity.
3. Use this filled stage-definition worksheet
Hypothetical worked example: The following worksheet describes a fictional supplier selling a business service. Every buyer situation and classification below is fictional. The stage model is a proposed operating design, not a description of any product's built-in controls.
Each entry uses the same fields so staff can compare the boundary, the evidence, and the common false signal. Adapt the states to your actual purchasing process rather than copying the names without review.
Stage: Problem confirmed
- Buyer state: A buyer participant has acknowledged a specific problem or desired change and can explain its consequence.
- Supporting evidence: A dated exchange or attributed meeting note records the problem, its effect, and the participant who confirmed it.
- Misleading activity signals: An introductory meeting occurred; the seller researched the account; a presentation was sent.
- Classification example: A buyer explains that disconnected handoffs cause repeated rework and confirms that reducing it is the purpose of the discussion. Classify as Problem confirmed.
- Boundary example: A contact attends an overview but does not identify a problem or desired change. Attendance alone does not establish this stage. Keep the record in its existing earlier or unconfirmed state rather than inventing confirmation.
Stage: Solution fit confirmed
- Buyer state: The relevant buyer participant has evaluated the proposed approach against the stated needs and confirmed that the important requirements are addressed.
- Supporting evidence: Buyer feedback identifies the requirements reviewed, the fit confirmed, and any remaining questions that do not invalidate that fit.
- Misleading activity signals: A demonstration was completed; a trial was offered; technical material was downloaded.
- Classification example: After reviewing the approach, the buyer confirms it addresses the handoff problem and identifies reporting preferences as a remaining discussion. Classify as Solution fit confirmed if those preferences are not essential requirements.
- Boundary example: The buyer enjoyed the demonstration but still needs to establish whether an essential workflow is supported. Keep the opportunity at Problem confirmed.
Stage: Purchase evaluation defined
- Buyer state: The buyer has described how the purchase decision will be made and confirms that the proposed offer is being considered through that process.
- Supporting evidence: Buyer-confirmed decision participants, decision criteria, unresolved questions, and the expected decision event or condition. An exact date is not required when the buyer cannot provide one.
- Misleading activity signals: A proposal was sent; a senior person copied an email; the seller entered an expected close date.
- Classification example: The buyer confirms that operations will evaluate the offer, finance will review the cost, and a decision will follow their joint review. Classify as Purchase evaluation defined.
- Boundary example: A contact requests pricing but cannot explain whether anyone will evaluate a purchase. A pricing request alone does not establish this stage.
Stage: Commercial agreement confirmed
- Buyer state: The buyer has explicitly accepted the proposed scope and commercial terms, with any remaining completion requirements identified.
- Supporting evidence: Recorded acceptance from the relevant buyer participant, the accepted offer version, and a description of what remains before the purchase is complete.
- Misleading activity signals: A revised quote was issued; a discount was approved internally; the seller believes the deal is effectively done.
- Classification example: The buyer confirms acceptance of the specified scope and price, while an internal purchasing reference remains outstanding. Classify as Commercial agreement confirmed, not Completed.
- Boundary example: The buyer says the price seems reasonable but has not accepted the offer. Keep the opportunity at Purchase evaluation defined if that stage's evidence remains valid.
Terminal states: Completed and Closed without purchase
- Buyer state: Completed means the organization's defined purchase-completion event has occurred. Closed without purchase means the current buying process has ended without a purchase.
- Supporting evidence: For Completed, the recorded completion event under the company's policy. For Closed without purchase, a buyer decision or a documented closure decision with its basis.
- Misleading activity signals: An agreement was sent for acceptance; onboarding was discussed; a buyer stopped replying.
- Classification example: The required completion record exists, so the opportunity is Completed. Separately, a buyer confirms the project has been cancelled, so that opportunity is Closed without purchase.
- Boundary example: Silence alone does not establish rejection. If an inactive opportunity is administratively closed, record that basis rather than presenting it as an explicit buyer decision.
4. Add rules for incomplete, conflicting, and out-of-order evidence
The worksheet needs a classification rule: Assign the furthest stage whose required buyer conditions are supported, including earlier conditions that still matter. Later seller activity cannot substitute for missing buyer evidence.
Buyers do not always progress neatly. In a hypothetical case, a buyer may arrive with a purchase process already defined before confirming solution fit. Record the known process, but do not treat it as proof of fit. If later evidence establishes the missing conditions, the opportunity can move directly to the appropriate stage without ceremonial stops at every intermediate stage.
Conflicting evidence needs interpretation, not a vote count. A supportive contact's confirmation may not settle a requirement that another relevant participant disputes. Record the unresolved issue and classify against the full stage rule.
Distinguish not known from known not to be true. A missing note may mean evidence was never captured. A buyer withdrawing acceptance means the condition has changed. Both require attention, but they are different problems.
5. Let stages move backward when buyer conditions change
A stage should describe the current supported state, not the furthest point the seller once reached. Otherwise a withdrawn agreement or reopened requirement leaves the opportunity overstated.
In a hypothetical case, a buyer accepts the offer, then adds a mandatory requirement that the proposed solution has not been shown to meet. Commercial agreement confirmed is no longer supported. Move the opportunity to the highest stage still supported and record the reason.
Do not move every quiet opportunity backward merely because time has passed. Time without contact may make evidence worth rechecking, but it does not prove that a previously confirmed condition has reversed. Keep inactivity and stage meaning separate.
When correcting an activity-based pipeline, review the evidence rather than mechanically renaming stages. Some opportunities may move backward; others may skip forward because the necessary evidence already exists. Treat this as a classification correction, not evidence of sudden commercial improvement or deterioration.
6. Test whether staff classify the same deal consistently
A definition is not operational until different people can apply it to the same information. Run a blind classification exercise before changing the full pipeline.
Hypothetical test design: Select ten anonymized opportunity snapshots and ask three staff members to classify each independently. Include clear cases, missing evidence, conflicting feedback, and at least one reversed buyer decision. These numbers are illustrative, not a benchmark.
- Give everyone the same worksheet and evidence packet. Remove the current stage and owner commentary that reveals the intended answer.
- Ask each person to select a stage, cite the supporting evidence, and identify anything missing.
- Count how many snapshots received the same classification from everyone.
- Review disagreements by boundary, not by employee. Identify whether the cause was ambiguous wording, absent evidence, or different interpretations of the buying process.
- Revise the relevant rule and test it on fresh snapshots.
For a hypothetical result, full agreement on six of ten snapshots would be 60% agreement. That measures classification consistency in that exercise, not deal quality or future sales performance.
Agreement alone is insufficient: everyone could share the same mistaken shortcut. Check the cited evidence too. If all reviewers advanced a deal because a proposal was sent, the exercise has exposed a shared activity-based rule.
7. Keep evidence requirements useful rather than burdensome
Stricter definitions make stages easier to interpret, but excessive evidence requirements can encourage box-ticking. Require enough information to support the boundary, not a transcript of every interaction.
A practical evidence note records the buyer participant, the confirmation date, what was established, and any unresolved condition relevant to classification. A link to an existing record can avoid duplicating the same explanation in several places.
Choose stage granularity deliberately. A simple purchase may not need separate fit and purchase-evaluation stages. A more involved process may need them because each reveals a different unresolved question. Add a stage only when staff can explain the distinction and classify it reliably.
Keep the stage rule separate from software enforcement. A required field may prove that someone entered text, not that a buyer condition is true. If implementing this design in a CRM, check the workspace and current plan for available fields and controls rather than assuming the proposed workflow is supported.
8. Make the next review an evidence audit
Start with one disputed boundary, such as the move after a proposal is sent. Rewrite it as a buyer condition, fill its evidence and exclusion fields, and test it against a small set of opportunity records.
For that review, record three observable measures: classification agreement, the share of records with evidence sufficient to judge the boundary, and the number of stage changes justified only by seller activity. Set any acceptance threshold locally before the test; there is no universal target established here.
If agreement is low, sharpen the definition. If evidence is missing, improve the evidence note. If staff agree but cite activity instead of buyer progress, revisit the underlying rule. The immediate deliverable is a stage definition that colleagues can apply consistently—not a pipeline that merely looks more advanced.
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