Customer journey phases explained. Five phases, and they loop.

The short answer. Five phases, not three, and they loop.

Most simplified descriptions of the customer journey still borrow the old marketing funnel: awareness, consideration, decision, full stop. McKinsey's consumer decision journey research, published in McKinsey Quarterly in 2009 after studying purchase decisions across roughly 20,000 consumers in multiple markets, made the case for a different shape. Rather than a funnel that narrows to a single purchase and ends, McKinsey described a loop: customers consider options, actively evaluate them, buy, then move into a post-purchase experience that either builds loyalty and advocacy or sends them straight back into evaluation for the next purchase or renewal.

For a founder-led or SaaS business, the practical version of that research is five phases worth naming on your own map: awareness, when someone first recognises a problem you solve; consideration, when they're comparing options, including doing nothing; decision, when they choose, usually involving more back-and-forth than a single moment; onboarding, the period right after the sale that decides whether the purchase was a good one; and loyalty or advocacy, where a satisfied customer renews, expands or refers, or a dissatisfied one quietly starts the evaluation phase again without telling you.

How it works in practice. Naming the handoffs between phases, not just the phases.

The phases themselves matter less than what happens at the boundary between them. Awareness to consideration is usually a content or search problem: does the right person find you when the problem first becomes visible to them. Consideration to decision is usually a trust and clarity problem: can they tell, from what you've shown them, that you solve their specific version of the problem, not a generic one. Decision to onboarding is where B2B journeys in particular tend to lose momentum, because the enthusiasm of the sales process meets the reality of implementation, often with a different team on your side taking over.

Map each boundary with the same questions: what does the customer need to see or feel to move forward, what do they actually experience right now, and where's the gap. Our guide to running a journey mapping workshop covers how to gather this directly from customers and frontline staff rather than guessing at it from inside a meeting room. For B2B journeys specifically, it's worth naming a distinct evaluation or procurement phase between consideration and decision, since multiple stakeholders and a formal buying process often add a step that a simpler B2C map wouldn't need.

What good looks like. A map that keeps going after the sale.

A customer journey map is doing its job when it covers what happens after the purchase with the same level of detail as what happens before it. In practice, most maps I see from teams mapping their own journey for the first time are detailed through decision and thin, sometimes entirely blank, from onboarding onward. That's understandable; marketing and sales usually own the mapping exercise, and their visibility naturally ends roughly where their job does. But for any business where revenue depends on renewal, expansion or referral rather than a single transaction, the post-purchase phases are where the map earns its keep.

A useful test: can your map answer what a customer experiences in their first thirty days, and what specifically would make them re-enter evaluation ahead of a renewal date. If the map goes quiet after "deal closed", it's mapping half a journey. Our customer journey mapping work treats onboarding and loyalty as full phases in their own right, not an afterthought tacked onto the end of a sales-focused diagram.

Pitfalls to avoid. Stopping the map at the sale.

A SaaS client I worked with had a clean, well-regarded journey map covering awareness through to decision, built carefully with input from marketing and sales. What it didn't cover was the ninety days before renewal, when a meaningful share of their customers quietly started evaluating competitors again, well before anyone on the account team noticed anything was wrong. The team had, in effect, mapped a funnel and called it a journey; the loop back into evaluation was happening entirely outside anyone's view, because the map had never been built to look for it. This is an illustrative pattern, not a single named client result, but the decision rule holds broadly: if your map stops at "purchase", you have no way to see the re-evaluation phase that decides whether a customer renews, and you'll keep finding out about churn risk only once it's already decided.

A second pitfall is building one journey map for every customer type, when meaningfully different segments move through the phases differently. A self-serve buyer and an enterprise buyer rarely share the same decision phase, and forcing them onto one map usually means the map is accurate for neither. A third, quieter pitfall is treating the map as a one-off workshop output rather than something revisited as the product, pricing or market changes; a journey mapped accurately two years ago can describe a journey that no longer exists.

Getting started. Name your own phases before borrowing someone else's.

Before adopting a generic five-phase template wholesale, sit with real customers or frontline staff and ask where the actual decision points are in your specific business. For some businesses, awareness and consideration blur into a single phase; for others, decision splits into a distinct procurement step that deserves its own name. The five phases above are a strong starting structure, not a fixed template to apply unexamined.

Once the phases are named, map the boundary between each one with real customer language rather than internal jargon, and make sure at least one phase extends past the point of sale. Our customer journey mapping work usually starts with exactly this exercise, naming the real phases for a specific business before building out the full map and the actions that follow from it.