A pipeline is useful when its stages describe observable progress. It becomes misleading when each salesperson interprets the labels differently. The goal is not to make every opportunity look active. It is to show what is known, what remains uncertain, and what action could move a genuine opportunity forward.
Define stages through evidence
Start with a small number of stages that match your sales process. For example: new enquiry, qualified, assessment completed, proposal sent, decision pending, and won or lost. For each stage, write one sentence describing the evidence required to enter it. A completed conversation is evidence; feeling optimistic about a prospect is not.
A qualified opportunity might require a confirmed need, an appropriate service area, and an agreed next conversation. Proposal sent should mean that a specific version reached the intended recipient, not that somebody started drafting it. Keep the definitions close to the working pipeline so new team members do not have to learn them through guesswork.
Separate activities from customer progress
Calling a prospect is an activity. Learning that the prospect has approved the scope is progress. If every activity becomes a stage, the pipeline quickly fills with labels such as called once, emailed twice, and waiting again. Keep calls and reminders as tasks or notes, and reserve stages for meaningful changes in the opportunity.
Consider a contractor who sends an estimate and then revises it after a customer requests a different material. The opportunity may remain in proposal or decision pending while the version changes. Record the revision, decision-maker, and next review date instead of moving the deal forward just because another document was sent.
Give stalled opportunities a clear treatment
For each open opportunity, maintain a next action and its due date. Review opportunities with no scheduled action or unusually long time in a stage. The useful question is what information or decision is missing. Sometimes the next step is a clarification call; sometimes the customer has postponed the project and the record should leave the active forecast.
Do not hide indefinitely inactive opportunities inside an apparently healthy pipeline. Agree when to mark a deal lost, move it into a separate nurture process, or schedule a future check-in. Capture a practical reason such as timing, scope mismatch, no response, or another provider selected. Avoid reasons that blame the customer without explaining what happened.
Run a review that produces decisions
A weekly pipeline review should focus on exceptions rather than reading every record aloud. Look at overdue next steps, high-value deals without confirmed decision dates, and proposals that need input from another team. End each discussion with a named owner and a specific action. If the meeting creates no decisions, simplify the agenda.
Keep stage definitions stable long enough to compare results, and document changes when the process genuinely evolves. Otherwise, a better conversion rate may reflect relabelling rather than better selling. Review a small sample of won and lost opportunities each month to check whether the stage criteria still describe reality and whether the records contain enough detail for someone else to understand them.
Put it into practice
- Write an entry rule for every stage.
- Keep activities separate from milestones.
- Record the next action and decision date.
- Review stalled opportunities instead of carrying them indefinitely.
