Derive the stages from a real customer
Pick a recent customer who became a paying client and walk backwards through their journey. They paid you. Before that, they accepted a quote. Before that, they had a discovery call. Before that, they sent an enquiry. Before that, they were just a name on a referral list. That is five stages: name on list, enquiry sent, discovery call, quote sent, paying customer. Those are your stages. They are not generic, they are not aspirational, they are what actually happened. Repeat the exercise with two more customers and you will see the pattern stabilise around three to five stages.
Some businesses have shorter pipelines - a coffee shop's pipeline might be 'walked in, ordered, paid' which barely needs a system at all. Some have longer ones - a building company might have 'enquiry, site visit, quote, deposit, scheduled, in build, completed, paid'. The right number is whatever matches how customers actually move, which is almost always three to five for the kind of business this eBook is written for.
- Three to five stages, no more without a real reason
- Each stage has a clear, observable definition
- Movement between stages is triggered by an event, not a feeling
- Lost is a stage you use, not avoid
- Every stage matches what your customer actually does
Definitions, not feelings
Each stage needs a clear definition of what triggers entry and exit. 'Discovery call' should mean an actual call has happened, not that one has been suggested. 'Quote sent' should mean the customer has received a written quote, not that you have started writing one. 'Paying customer' should mean money has changed hands or the contract is signed, not that they said yes on a call. Without these definitions, the pipeline becomes a soft estimate of how the salesperson is feeling that week, and the stage column stops being useful.
Add 'lost' as an honest stage
Most owners avoid the 'lost' stage because moving a customer there feels like an admission. It is not - it is information. Customers who you marked as lost in the spring might be ready to revisit in the autumn. A pipeline where contacts only move forward and never to lost will quietly fill with stale opportunities, until the whole pipeline becomes unbelievable. Use lost early and often; mark the reason in a notes column, and revisit them in a few months.
When to add a stage and when not to
Add a stage when there is a real action happening that takes meaningful time - 'site visit' if site visits are a substantial step in your business, 'sample sent' if samples are part of the buying decision. Do not add a stage just because you would like to track a small detail; that is what the notes column is for. The rule of thumb: if you cannot say which week of the year you most recently moved someone into a stage, that stage probably should not exist.
Reviewing the stages every six months
Pipelines drift. The stages you set up in January may no longer match how customers buy by July, especially if your offer or your channels have changed. Once every six months, take ten minutes in the weekly review to ask whether the stages still match reality. If they do not, change them. The customer list system is a tool, not a monument. Updating it is a sign of attention, not of failure.
What to do this week
Pick three recent customers who became paying clients. Walk each one backwards through the stages they actually went through. Write the common stages down. Compare them to whatever defaults your spreadsheet or software currently has. Replace the defaults with your real stages this week.
The previous chapter chose the container; this chapter sets out how things move through it. The next chapter Reminders and Follow-Up Dates is the part that turns the pipeline from an observation into a working system. Recurring principle: review results and improve the system.
