Sales Operations
A simpler pipeline: choosing stages that reflect real progress
Choose pipeline stages that distinguish buyer progress from team activity, with clear evidence for each move and useful treatment of stalled opportunities.
A pipeline with columns for “Called,” “Emailed,” and “Left voicemail” tells you what the team did. It tells you much less about what the buyer decided. If a manager needs to open every record to understand whether an opportunity is moving forward, the columns are doing too little work.
Start your redesign with a practical question: what changed for the buyer? A useful stage makes that change visible. Tasks and activity history can carry the details of how the team helped it happen.
Distinguish effort from evidence
Sending three messages is effort. A buyer confirming that they want to visit a community is evidence of a next step. Both matter, but they answer different questions.
HighLevel describes pipelines as a way to organize opportunities through defined stages. Its guidance calls for clear rules about when an opportunity moves. The work for your team is deciding which evidence deserves that move.
For each proposed column, finish this sentence: “We know an opportunity belongs here because…” If the answer depends on a salesperson's optimism, rewrite the definition. “Very interested” may mean different things to different people; “Visit completed” can be checked against a specific event.
Give similar milestones different meanings
Consider an illustrative homebuilder process: inquiry received, conversation established, visit booked, visit completed, and purchase discussion underway. These are starting points for discussion, not a universal template.
A booked visit and a completed visit deserve separate treatment when the team needs to understand attendance. If nobody uses that distinction to make a decision, a visit outcome field may be enough. Every extra column creates another judgment the team must make consistently.
For an agent, a property showing may be only one step in a longer search. For a mortgage team, agreeing to a consultation is different from completing an application. Choose milestones for the particular process you manage. Avoid a shared label such as “Approved” when different teams would read different promises into it.
Keep tomorrow's task out of today's stage
A buyer can remain at “Visit completed” while the next task is to send a floor-plan comparison. Changing the stage to “Send comparison” would erase the useful milestone and replace it with an unfinished chore.
Keep an owner, next action, and due date alongside the stage. When reviewing an opportunity, the team should be able to distinguish what has happened from what someone still needs to do.
Also decide how to represent a genuine pause. A buyer waiting for their current home to sell needs a recorded reason and review date. A catch-all “Follow up” column can hide that context alongside unanswered inquiries and active negotiations.
Try the definitions before changing the board
Give two colleagues the same small set of records and ask them to assign stages independently. Compare disagreements. Those differences reveal ambiguous definitions, missing evidence, or milestones that do not fit actual buyer journeys.
Resolve those issues before moving existing records or changing reminders tied to stages. Write down where each old category belongs and inspect exceptions individually. A cleaner-looking board is useful only if the opportunities still mean what the team thinks they mean.