A sales pipeline shows how many real opportunities move from initial contact to an order, where they stop and how long each step takes. Stages called “thinking”, “in progress” or “nearly ready” store an adviser's opinion rather than the state of the sale.
A useful stage is supported by an event or data. Another employee should understand what has happened, what must happen next and which condition allows the deal to progress.
Separate enquiries, deals and orders
A new enquiry is not automatically a sales opportunity. First confirm a relevant need, a usable contact, fit with the offer and the ability to continue the conversation. Qualification then creates or confirms a deal.
| Object | Meaning | Main control |
|---|---|---|
| Enquiry | A new relevant contact still requiring qualification | First response and qualification outcome |
| Deal | A confirmed opportunity with a customer, subject and next step | Stages, amount, deadline and closure reason |
| Order | A commitment with exact lines, price and fulfilment | Payment, reservation, dispatch or service delivery |
Mixing them inflates the pipeline and confuses operations. The warehouse should not act on an “interested customer” before an order exists.
Build stages around outcomes
For every stage, answer:
- which fact has been confirmed;
- which fields or documents prove it;
- who owns the current state;
- what the mandatory next action is;
- when it must occur;
- which condition moves the deal forward;
- which reasons allow return or closure.
“Proposal sent” is stronger than “preparing proposal” when the transition records an actual send date and document version.
Example B2B sales pipeline
| Stage | Confirmed outcome | Mandatory next action | Transition criterion |
|---|---|---|---|
| Qualified | Need and fit are confirmed | Clarify scope, timing and decision participants | Minimum requirements captured |
| Requirements defined | Solution scope and criteria recorded | Prepare proposal | Enough data for price and timing |
| Proposal sent | Customer received specific terms | Agree a review date | Response or comments received |
| Negotiation | Specific terms are being discussed | Resolve open issues | Terms accepted or rejected |
| Decision pending | Customer has everything needed to decide | Contact on agreed date | Purchase or rejection confirmed |
| Won | Order, contract or payment exists under company rules | Transfer to fulfilment | Operational document created |
This is too detailed for a fast retail sale, which may need only qualification, selection, order confirmation and outcome.
Do not create a stage for every activity
Calls, emails, meetings and reminders are activities that can occur at several stages. Turning each one into a status makes advisers move cards backwards and forwards while stage conversion loses meaning.
A stage changes when the opportunity state changes. An activity records work within that state.
Require data at important transitions
| Transition | Minimum data | Purpose |
|---|---|---|
| To qualified deal | Contact, need, product or direction, next action | Avoid empty opportunities |
| To proposal | Scope, quantity, price, deadline, document version | Compare the same business state |
| To decision pending | Decision date, customer participant, open risks | Never leave a deal without a control date |
| To won | Order, contract or payment reference | Separate intention from actual result |
| To lost | Verifiable reason and short detail | Analyse losses without deleting deals |
Do not make a field mandatory merely because CRM offers it. Requiring a customer's budget is pointless if it is usually unknown and does not affect a decision.
Set expected time at each stage
A deal may legitimately wait weeks for a decision, but it should never lack a next-contact date. Track time in stage, overdue action, period without contact, backward movement and deals exceeding the normal cycle.
Automatic closure based only on age is risky. Create a control task first, then let the responsible role decide under company rules.
Probability should come from evidence
Manual “80% probability” often represents optimism. Use historic conversion for the same stage and segment. If 28 of 100 proposals become sales, the baseline probability is approximately 28%, not an arbitrary 70%. Large opportunities can then be adjusted for confirmed risks.
When separate pipelines are justified
Use separate pipelines when steps and times genuinely differ: new sale, repeat order, tender, service contract or partner agreement. Do not create one for every adviser or advertising source; those are fields on the deal.
Stage conversion
Stage conversion = Deals moving forward / Deals entering the stage × 100%.
Interpret it with time and segment. Low conversion after proposal may indicate unsuitable pricing, poor discovery, excessive lead time or proposals sent to the wrong prospects.
Common mistakes
- Stages describe mood. There is no verifiable state.
- Too many statuses. Staff spend time maintaining cards.
- Enquiries, deals and orders are mixed. Conversion and fulfilment become distorted.
- No next action exists. The deal is active only on paper.
- Lost deals are deleted. Management sees a convenient version of reality.
- One pipeline serves different processes. Stages fit neither ordinary sales nor tenders.
- Probability is entered manually. Forecasting becomes subjective.
Sales pipelines in Business Reactor
Business Reactor links a deal to the customer, product, proposal, order, payment and next action. A transition can be confirmed by an actual event instead of a manual status selection alone.
The pipeline shows where sales are lost, but improvement requires consistent loss reasons covering price, timing, stock availability, poor fit, competition and process failure.
Conclusion
A good pipeline uses the fewest stages needed. Every stage has a confirmed outcome, transition criterion, owner, deadline and next action. Activities do not replace stages, and lost deals remain available for analysis.
The next step is a loss-reason register that explains not only how many deals were lost but what the business should change. Business Reactor Core.
