Build a pipeline that shows movement, not storage.

Stages must represent meaningful progress

A pipeline should answer one simple question: where is each active opportunity in the buying process? Stages should describe evidence of progress, not just the salesperson's activity.

Keep the stages understandable to the team. A smaller set of stages with clear definitions is more useful than a long list that nobody applies consistently. A proposal being prepared and a proposal being reviewed by the customer may represent different situations.

Define what moves an opportunity forward

Agree on the evidence required to enter and leave each stage. Examples include a confirmed requirement, an agreed meeting or a proposal received by the decision maker. Record the next action that will help establish that evidence.

A completed call is not necessarily progress. If the conversation did not change the opportunity's buying position, update the context and next action without advancing the stage.

Stalled is different from active

An opportunity can remain open without making progress. Review the time spent in a stage, recent meaningful activity and whether the next step is clear. Use these signals to find records that need attention.

Some sales genuinely take longer. Review the reason before deciding that age alone means failure. A documented timing hold is different from a record that nobody has touched.

Don't keep everything alive forever

Leaving every opportunity open makes the pipeline difficult to trust. Decide which records should progress, receive another follow-up, enter a later recovery review or close as lost.

Preserve useful context when closing. A reason for loss can help explain future decisions and identify whether a later re-engagement is appropriate. Do not imply every closed lead should be recovered.

Pipeline value needs context

Expected value is not the same as won revenue. Review how values were estimated and whether the opportunity is genuinely active. A large total can conceal stale records, inconsistent currencies or values that have not been updated.

Compare pipeline value with stage movement and actual outcomes. Use the currency and reporting context available in your system rather than simply adding unlike amounts.

Review movement, not just totals

A weekly review should produce decisions. Ask what changed, what is stuck and what the next useful action is. Review owners and commitments alongside the number of opportunities in each stage.

• Aging
• Next actions
• Stage movement
• Ownership
• Expected value

Progress → Follow up → Recover later → Close as lost