Many pipelines grow out of the sales team’s to-do list: call, demo, send quote, follow up. That feels natural, but it means a deal moves forward whenever the salesperson does something, even if the customer has not moved at all. Ten quotes in “quote sent” can be ten buyers who are ready to sign or ten who never opened the email. Pomio CRM recommends naming stages after what the customer has done or confirmed, because that is the part a manager, a forecast and a colleague who takes over the deal can actually rely on.
Activity stages measure effort, customer stages measure progress
A stage named after a sales activity is always reachable: you can send a quote to anyone. A stage named after a customer step needs something from the buyer: a meeting they accepted, a need they confirmed, a budget they named, a proposal they said they want to move forward with. That difference is exactly what makes the stage meaningful. When stages reflect customer steps, the share of deals in later stages says something about real buying interest, and a probability that follows the stage becomes believable instead of optimistic.
Write down the evidence for each stage
A good stage name is short, so it needs one sentence behind it describing what has to be true. “Need confirmed: the customer has described the problem and agreed it is worth solving this year.” “Proposal accepted in principle: the decision-maker has said yes to scope and price, pending paperwork.” Those sentences become the exit criteria for each stage, and they only work if sales and management read them the same way, as described in why sales and management need shared stage definitions.
Keep activities as tasks, not stages
The things a salesperson does still matter, but they belong in tasks and activities rather than in the pipeline. “Send quote” is a task with a due date; the stage changes when the customer responds to it. This also keeps the pipeline short. Most SMEs manage with five or six stages, and a maximum number of stages helps prevent every internal step from becoming a column on the board.
What to do when the customer moves backwards
Customer-based stages make it visible when a buyer steps back, for example when a confirmed budget is suddenly withdrawn. That is useful information, not a failure of the pipeline. Agree whether a deal may move back a stage in that case, and whether skipping a stage requires approval when a customer jumps straight from first contact to a signed order. Both rules are easier to apply when every stage describes something the customer did.