Customer journey stages are the named phases a buyer passes through, from first noticing you to buying and buying again, each with a clear line where one stage ends and the next begins. Get the lines right and every report you run afterwards is trustworthy. Get them wrong and stage counts mean something different to every person who reads them. This article answers where to draw those lines, how many stages a firm of 10 to 250 people needs, and how to turn them into pipeline stages in the levelpartner.ai platform.
A working set of stages
There is no universal list, but most service businesses land on something close to this:
- Aware: they know you exist.
- Enquired: they have contacted you or submitted a form.
- Qualified: they meet your criteria for budget, need and timing.
- Proposal: they have received a price or a quote.
- Client: they have paid or signed.
- Retained: they have renewed, bought again or referred someone.
Agencies and consultants often split proposal into proposal and negotiation. Mortgage brokers usually add application and offer between proposal and client. Real estate firms tend to separate viewing from offer.
Customer journey map stages versus pipeline stages
Customer journey map stages describe the buyer's experience, including stages before they ever contact you. Pipeline stages describe what you can record. Aware cannot be a pipeline stage, because you do not yet have a contact record. Everything from enquired onwards can.
Keep the names identical where the two overlap. When the map says "qualified" and the pipeline says "SQL", people assume they are different things.
Before you start
- A list of the last 30 deals, won and lost, with a rough note of what happened in each.
- Agreement from sales and marketing on who owns which stage.
- Access to Opportunities to create or edit a pipeline.
How to set it up
- Read through the last 30 deals and note each point where the buyer made a decision.
- Group those decision points into four to seven stages.
- Write an entry rule for each stage that names a record, such as a booking, a form or a payment.
- Drop the awareness stage from the pipeline list, since it has no contact record.
- In Opportunities > Pipelines, click Create new pipeline and add stages in order.
- Skip won and lost, which the platform creates automatically.
- Move every open opportunity into the stage that matches its entry rule today.
- Add Customer Booked Appointment and Payment Received workflows that update opportunities.
- Add a Stages Distribution widget and check the counts look plausible.
Say the consultancy has nine pipeline stages, and three of them, "warm", "very warm" and "hot", have no entry rule, so salespeople move cards between them by feel. Collapsing those three into one qualified stage with a rule, discovery call held and budget recorded, would leave six stages. The forecast should then stop swinging week to week, because a card could only move when something checkable happened. The scenario is hypothetical.
What stages are for in a stalled business
When growth has stopped, you need to know whether the problem is volume at the top or conversion in the middle. Clean stages answer that within one report. Without them, every conversation about growth turns into a debate about lead quality.
Stages also give each team a number to own. Marketing owns enquired, sales owns qualified to client, delivery and account management own retained.
Testing a stage boundary
Take five open opportunities at random and ask two colleagues, separately, which stage each belongs in. If they disagree on any of them, the boundary between those stages is still vague. Tighten the entry rule until both would give the same answer every time.
Time it takes
Drafting stages from past deals takes a morning. Building the pipeline and the movement workflows takes a day. After that, stages need almost no weekly time; review the definitions once a year.
The mistake most people make
Naming stages after temperature or mood. "Hot", "warm" and "cold" depend on who is looking. Name stages after something the buyer did, and you will get the same count no matter who runs the report.
When not to add a stage
Add a stage only if a buyer can genuinely be stuck there and someone will act on it. A stage that every contact passes through in an hour adds clicks and no information. Put that level of detail into customer journey steps instead, which tracks actions inside a stage.
Troubleshooting
Most opportunities sit in the first stage
Nobody moves them. Add workflows that move cards on bookings and form submissions, and close old ones as lost.
Counts drop to zero in one stage
The entry rule depends on a field nobody fills in. Make the field required on the relevant form or change the rule.
Two pipelines use different stage names
They grew separately. Rename them to a shared set, and record any genuine differences in your customer journey framework.
Frequently asked questions
How many stages should we have?
Four to seven in the pipeline. Fewer hides problems; more creates stages nobody maintains.
Should lost be a stage?
No. Treat lost as an outcome with a reason field. That lets you report on why deals were lost at each stage.
Do stages change by industry?
The middle stages do. Agencies, consultants, mortgage brokers and real estate firms each have one or two industry-specific stages. The first and last stages are usually the same. For how those stages fit a wider plan, see customer journey strategy, and to show them as a chart, see customer journey visualization.