Use buyer milestones, not internal activity labels.
“Email sent” describes an activity. “Discovery agreed” describes a change in the buying conversation. A stage should help the team understand the status without opening every message. Different services may need different journeys, but adding stages is not a substitute for clarifying the process.
A starting model might include new enquiry, fit confirmed, discovery completed, proposal under review and decision. This is an illustrative model, not a prescription: use only stages that reflect the way your customers actually buy.
Write one operating rule for every stage.
Create a short stage worksheet before configuring the CRM. If two stages have the same owner, evidence and next action, consider combining them. If a stage means different things to different people, rename it before automating it.
- Entry evidence: what must be true before a record arrives here?
- Owner: who is accountable for moving the conversation forward?
- Next action: what should happen, and by when?
- Exit evidence: what proves the next stage has been reached?
- Exception: where does the record go if the buyer pauses or declines?
Make pauses and losses visible.
Do not leave inactive opportunities in an active stage indefinitely. Agree how to record a pause, an unsuitable enquiry and a lost opportunity. A small, clear set of reasons is more useful than a long list that the team cannot apply consistently.
Record a follow-up date only when a future action is justified. Distinguish a buyer who requested contact later from a prospect who has not agreed to continued follow-up. That difference matters when messages are automated.
Review the pipeline as a working system.
Inspect a handful of real records with the team. Can everyone explain their current state, owner and next action? Check for opportunities that moved backwards, skipped a stage or never received a task. These examples reveal where the rules need adjustment.
Measure response time, stage age and qualified progression alongside activity counts. More records in a CRM do not necessarily mean more useful sales conversations. Once the team trusts the stages, introduce automation one handoff at a time and test the exception paths.
Questions before you start
Questions before you start
How many stages should we use?
Use the fewest that distinguish meaningful buyer milestones. There is no universal correct number. Every stage should have a clear entry rule and next action.
Should every salesperson have a different pipeline?
Not by default. Separate pipelines when the underlying buying journeys differ materially. Personal preferences are usually better handled through views or task ownership.
When should a proposal be marked as won?
Agree the evidence with your business before configuration—for example, an accepted agreement under your sales process. Sending a proposal alone should not count as a win.