Customer journey stages are the high-level phases a customer moves through during their relationship with your organization. They provide the backbone of every journey map, organizing touchpoints, actions, and emotions into a coherent narrative. Get the stages right and the map becomes a useful diagnostic tool. Get them wrong and the entire structure works against you.
The problem is that most teams don't define their own stages. They copy a marketing funnel model, rename the phases, and call it a customer journey. The stages describe how the company acquires customers, not how customers experience the relationship. The difference matters more than most teams realize.
What customer journey stages actually are
A customer journey stage is a distinct phase of the customer's experience, defined by what the customer is trying to accomplish at that point, not by how the organization is structured internally.
Stages are the scaffolding of a journey map. Each stage contains touchpoints, actions, channels, and emotions. Together they tell the story of the customer's experience from their first awareness of a need through to ongoing engagement or departure. A well-structured set of stages makes the rest of the journey map easier to build, easier to read, and easier to act on.
Most journey maps have 5-7 stages. Fewer than 4 is too abstract to guide specific improvements. More than 8 usually means you're mixing stages with steps, which is the single most common structural mistake in journey mapping.
The standard stage models
Three models dominate the conversation around customer journey stages. Understanding what each one is designed for helps you choose the right starting point, or recognize when you need to move beyond all of them.
| Model | Stages | Best for | Limitation |
|---|---|---|---|
| 3-stage | Pre-service, Service, Post-service | High-level views, early workshops | Too abstract for detailed improvement |
| 5-stage | Awareness, Consideration, Decision, Retention, Advocacy | Acquisition-focused journeys, marketing | Heavily weighted toward pre-purchase |
| 7-stage | Awareness, Interest, Consideration, Intent, Evaluation, Purchase, Loyalty | Complex B2B purchase journeys | Still fundamentally a sales funnel |
The 5-stage model is what most content on this topic covers. It's the marketing funnel repackaged as a customer journey. It works for acquisition-focused analysis, but the customer's actual experience of using the product, getting support, renewing, and potentially leaving gets compressed into a single "retention" stage. For CX practitioners working on service improvement, that compression hides the detail that matters most.
Why most stage models get it wrong
The core problem with standard models is that they describe how the business acquires customers, not how customers experience the relationship. The stages follow your sales pipeline, not the customer's reality.
Here's what the shift from funnel-based to customer-defined stages looks like in practice:
The funnel version has five stages that mirror a CRM pipeline. The customer-defined version has seven stages that reflect what the customer is actually going through. Notice how the post-purchase experience, which the funnel compresses into "retention," expands into four distinct phases: building habits, hitting a wall, getting help, and deciding to stay. That's where most of the real customer experience happens, and it's exactly the part the funnel model hides.
The tell is simple. If your stage names match department names, you've mapped your org chart, not a journey. "Marketing" is not a customer experience stage. "Evaluating whether this solves my problem" is.
How to define stages for your journey map
Defining stages that reflect the customer's experience rather than your internal process takes deliberate effort. Here's a practical approach.
Start with the customer's goal
Every journey has a trigger and an end state. A support journey starts when the customer encounters a problem and ends when it's resolved (or they give up). An onboarding journey starts at signup and ends when the customer has integrated the product into their workflow. The stages between those two points describe the customer's progression toward their goal, named in their language.
"Evaluating options" tells you something about the experience. "Sales pipeline" tells you about your process. Choose the first.
Look for shifts in activity and mindset
Stage boundaries happen where the customer's primary activity or mindset changes. The shift from "researching solutions" to "comparing two specific options" is a stage boundary. The shift from "trying the product for the first time" to "integrating it into daily work" is another. Each stage should represent a distinct phase with its own touchpoints, emotions, and success criteria.
If two adjacent stages have the same touchpoints and the same customer mindset, they're probably one stage.
Validate with evidence
Assumption-based stages are a useful starting point, especially in early workshops where the goal is cross-functional alignment. But they should be tested against real customer behavior. Check against interview data, support tickets, analytics, and survey responses. Where do customers actually spend the most time? Where do they drop off? Where do they get stuck?
The gap between your assumed stages and what the data reveals is where the real insights are. Research-based journey mapping closes that gap by grounding the map in evidence rather than internal assumptions.
Stages vs steps: the confusion that bloats journey maps
The most common structural mistake in customer journey mapping is putting steps where stages should be. A map with twelve stages that reads "Visits website, Reads pricing page, Signs up for trial, Receives welcome email..." isn't a twelve-stage journey. It's a two-stage journey with the steps listed at the wrong level.
Stages are phases. Steps are specific actions within a phase. A stage like "Getting started" might contain steps like create account, complete setup wizard, invite first team member, and create first project. If your map has more than 8 stages, check whether some are actually steps that belong inside a stage.
A useful rule of thumb: if you can't name 3-5 specific actions within a stage, it might be too granular to be a stage. And if a stage contains more than 8 steps, it might need to be split into two stages. The journey map elements that sit inside each stage, including touchpoints, channels, and emotional states, only make sense when the stages themselves are at the right level of abstraction.
How stage structures vary by business model
Stage structures aren't universal. Different business models produce fundamentally different journey shapes.
| Business model | Stage pattern | What's different |
|---|---|---|
| B2B | Longer evaluation, multiple stakeholders, implementation-heavy | 2-3 more pre-purchase stages. Onboarding is a major phase |
| B2C | Shorter consideration, impulse possible, post-purchase critical | Advocacy and community stages carry more weight |
| Subscription | Renewal cycle is as important as acquisition | Post-purchase has more stages than pre-purchase |
| Service-based | Service encounter is the journey center | Recovery stages for when things go wrong are essential |
The standard 5-stage funnel doesn't account for any of this variation. A subscription SaaS journey has more in common with a gym membership than with a retail purchase, yet the same stage model gets applied to all three. Start with your business model and your customer's actual experience, not with a generic framework.
Connecting stages to measurement
Stages become operational when you attach metrics to them. Without measurement, stages are labels. With it, they become diagnostic.
Each stage should carry at least one metric from each of three categories. This connects to the broader practice of tracking journey metrics at the stage level rather than only at the journey level.
| Stage | Perception metric | Outcome metric | Business metric |
|---|---|---|---|
| Researching | Awareness survey | Site visit to signup rate | Cost per lead |
| Evaluating | CES (effort to compare) | Trial activation rate | Pipeline value |
| Getting started | Onboarding CSAT | Time to first value | Onboarding cost |
| Building habits | NPS | Weekly active usage | Expansion revenue |
| Deciding to stay | Renewal intent | Churn rate | Customer lifetime value |
The three-category approach (perception, outcome, business) ensures you're capturing how customers feel, what actually happened, and what it means for the organization. Start with one metric from each category per stage and expand only when you need more diagnostic depth.
Common mistakes when defining stages
Beyond the inside-out naming problem, five other mistakes come up repeatedly:
- Having too many stages. If your map has 10+ stages, you're almost certainly mapping steps at the stage level. Check whether items can be grouped into broader phases.
- Having too few stages. The 5-stage funnel compresses the entire post-purchase experience into "retention." If that's where most of your customer's experience happens, you need more granularity there.
- Using the same structure for every journey. A support journey and an acquisition journey have fundamentally different shapes. Don't force both into the same 5-stage template.
- Defining stages once and never revisiting. Customer experiences change. Products evolve. Stages that made sense a year ago may not reflect reality today. Journey map governance includes periodic review of whether the stage structure still holds.
- Treating assumption-based stages as validated. Workshop-generated stages are hypotheses. They're useful for alignment but they need validation against real customer data before you invest heavily in improvements based on them.
FAQ
How many stages should a customer journey map have?
Most journey maps work best with 5-7 stages. Fewer than 4 is too abstract to guide specific improvements. More than 8 usually means you're mixing stages with steps. If you can't name 3-5 specific actions within each stage, the stages are too granular.
Should journey stages be named from the customer's perspective or the business perspective?
From the customer's perspective. Stages describe what the customer is trying to accomplish, not how your organization is structured. "Evaluating options" is a customer-perspective stage. "Sales pipeline" is an internal process label. If your stage names match department names, you're looking inward.
What's the difference between stages and steps in a journey map?
Stages are high-level phases of the experience (typically 5-7). Steps are specific actions within a stage (typically 3-5 per stage). A stage like "Getting started" contains steps like "create account," "complete setup," and "invite team." Confusing the two is the most common reason journey maps become unwieldy.
Do B2B customer journey stages differ from B2C?
Yes. B2B journeys typically have longer evaluation phases, involve multiple stakeholders, and require more substantial onboarding stages. B2C journeys tend to have shorter consideration phases and more emphasis on post-purchase engagement and advocacy. The stage count may be similar, but the distribution of complexity shifts significantly.
How do you handle non-linear journeys where customers skip or repeat stages?
Not every customer follows stages in sequence, and that's expected. The stages represent the typical progression, not a rigid path. When mapping, note the common loops and skip patterns. If a large percentage of customers skip a stage entirely, it may not be a real stage for that journey. If customers frequently loop between two stages, consider whether the stage boundaries are in the right place.
