What a pipeline actually represents
A pipeline is the sequence of stages a lead moves through, from first contact to a final won or lost outcome. Done well, it mirrors the buyer's actual decision journey — not just the internal admin your team does behind the scenes. That distinction matters more than it sounds.
A good stage describes something the buyer did or decided: they replied to a first message, they confirmed they have a real need and a rough budget, they received a formal quote. A weak stage describes something internal to your team instead: "sent to Priya," "waiting on legal," "needs follow-up." Internal admin belongs in a task or a note attached to the deal — not as a pipeline stage everyone has to interpret differently.
Defining realistic stages
A commonly useful starting structure looks like this: New — a lead has come in and has not been contacted yet. Contacted — first outreach has been made and the team is waiting on a response. Qualified — there is a confirmed real need, a plausible budget fit, and some sense of a decision process (this is where the lead scoring covered in Chapter 4 becomes useful). Proposal — a formal quote, plan or pricing has been sent. Won or Lost — the deal has closed either way.
"Lost" deserves particular attention. It is a genuinely useful, active stage — not a place to quietly hide failure. Closing deals out as Lost, with a brief reason attached, keeps the rest of the pipeline honest: everything still showing as open is actually still live, not just abandoned.
Stages should mirror how you actually sell. Deals also branch to Lost at any stage — that is a real outcome, not a missing one.
Why the tool's default pipeline usually needs adjusting
Most CRMs ship with a generic default pipeline, written to fit a generic B2B sales motion: something like Discovery, Demo, Negotiation, Closed. If the business sells a fixed-price service, does not run product demos, or handles most enquiries through a WhatsApp conversation rather than a formal negotiation, forcing leads through that template creates stages nobody interprets the same way twice.
A better approach: sit down and map the last ten to twenty real deals, both won and lost. Note the actual moments each one passed through — not what the process was supposed to look like, but what genuinely happened. Build the pipeline stages around that reality. It will usually look simpler than the default template, and it will actually get used correctly.
Keeping stages honest
Each stage should have a clear entry and exit condition, stated in one sentence, so moving a deal forward is not guesswork. It also helps to periodically review deals that have sat in one stage far longer than typical for that stage — a stalled deal is either genuinely stuck, or a sign that the stage itself is poorly defined. Finally, keep the total number of stages small enough to fit on one screen, usually five to seven. More than that, and the pipeline turns into bureaucracy that nobody keeps updated, which defeats the entire purpose.
- Can you name, in one sentence, what has to happen for a lead to move from each stage to the next?
- Does every stage describe a state the buyer is in, not a task your team still owes them?
- Are there fewer than eight stages in total?
- Is "Lost" an actual stage people use, or does it just quietly pile up inside "New"?
- Would a new hire understand what each stage means without being told?
If a stage does not describe something the buyer did, it is not a real pipeline stage — it is just internal record-keeping.