The Five-Stage Customer Journey Framework
The five-stage customer journey framework divides the full customer experience into Awareness, Consideration, Purchase, Retention, and Advocacy. Each stage represents a distinct set of customer needs, emotions, and decision criteria. Teams use the framework to map touchpoints, identify friction, and design interventions that move people from first contact through loyal advocacy. It applies across B2C and B2B, though real journeys rarely follow a perfectly linear path.
Overview
The customer journey is one of those concepts that seems obvious until you try to act on it. Everyone agrees that a customer moves from not knowing you exist to (hopefully) recommending you to friends and colleagues. But turning that intuition into something a cross-functional team can analyze, measure, and improve requires structure. The five-stage customer journey framework provides that structure by decomposing the entire customer lifecycle into five sequential stages: Awareness, Consideration, Purchase (or Decision), Retention (or Loyalty), and Advocacy.
The framework doesn't trace back to a single inventor. Its roots sit at the intersection of marketing funnel theory, service design, and customer experience (CX) research. The classic marketing funnel, often attributed to Elias St. Elmo Lewis's AIDA model from 1898, described attention, interest, desire, and action. Over the following century, practitioners realized two things. First, the journey doesn't end at purchase. Retention and word-of-mouth matter as much as acquisition, sometimes more. Second, the funnel metaphor implies a passive filtering process, when in reality customers loop back, skip stages, and re-enter at unexpected points. By the early 2010s, thinkers like McKinsey (with their Consumer Decision Journey, published in 2009) and service design firms like Smaply had pushed the field toward lifecycle models that extend well past the point of sale. The five-stage version became a de facto standard because it's specific enough to be actionable, yet general enough to fit nearly any business.
The underlying mental model makes a claim about how value is created and captured. It says that customer experience is not a single moment but a sequence of contexts, each with its own emotional register, information needs, and success criteria. A prospect in the awareness stage has fundamentally different questions than a customer in the retention stage. If you design for one context and ignore the others, you leak value. A company might be brilliant at acquiring attention through content marketing but terrible at onboarding, turning high acquisition into high churn. Or it might have a wonderful product that nobody discovers because awareness-stage touchpoints are absent. The framework forces you to confront the whole chain, not just the links you enjoy working on.
Compared to alternatives, the five-stage model sits in a sweet spot of complexity. Simpler funnels (awareness, consideration, decision) ignore everything after the sale. More elaborate models, like Forrester's customer lifecycle with its eight or more stages, can overwhelm teams that lack dedicated CX research functions. McKinsey's Consumer Decision Journey introduced the valuable concept of a "loyalty loop" but was originally oriented toward consumer packaged goods and can feel abstract in SaaS or services contexts. The five-stage framework borrows the post-purchase emphasis from McKinsey while keeping the linear simplicity that makes it easy to workshop across departments. It has evolved in practice to accommodate non-linear movement. Most experienced practitioners now draw it as a loop or spiral rather than a straight line, acknowledging that customers cycle back through consideration after a failed retention experience, or jump from awareness straight to purchase when urgency is high.
The framework benefits product teams, marketing teams, support teams, and leadership, really any group that needs a shared vocabulary for discussing where customers are and what they need. It works best when you treat it not as a fixed truth about human behavior but as a lens: a way to organize observations, prioritize investments, and spot gaps. Small startups use it informally on a whiteboard. Enterprise organizations build multi-year programs around it with dedicated journey managers per stage. Hamster provides a workspace where teams can run customer journey analysis alongside AI agents, keeping research, mapping, and action items in one place. The method's strength is its universality, and its risk is that universality can drift into vagueness if you don't ground each stage in real data about your specific customers.
How It Works
Step 1: Define your customer segments and select a priority journey
Before mapping anything, decide whose journey you're mapping. A B2B SaaS company might have an enterprise buyer journey, a self-serve user journey, and a partner-driven journey, each fundamentally different. Trying to map all of them at once produces a generic artifact that helps no one. Pick one segment to start with, ideally the one with the highest revenue impact or the one where you suspect the biggest experience gaps. You've done this well when you can describe the segment in specific terms: their role, their goals, their constraints, and roughly how many of them you have. A common mistake is choosing a segment that's too broad ('all users') rather than a specific persona with identifiable behavior patterns. If you're unsure which journey to prioritize, look at where your churn is highest or where customer acquisition cost is disproportionate to lifetime value.
Step 2: Map the current-state touchpoints for each stage
For your chosen segment, inventory every touchpoint where the customer interacts with your brand across all five stages. Awareness might include blog posts, paid ads, conference talks, and word-of-mouth. Consideration might include pricing pages, demo calls, free trials, and third-party reviews. Purchase includes the checkout or contract signing process. Retention covers onboarding, product usage, support interactions, and billing. Advocacy encompasses review sites, referral programs, community participation, and case study requests. The goal is completeness, not elegance. Pull data from analytics, CRM, support tickets, and interviews. You know you've done this well when team members from different departments are surprised by touchpoints they didn't know existed. The most common mistake is mapping only the touchpoints your team controls and ignoring third-party interactions like review sites, comparison articles, or Reddit threads where customers form opinions without your involvement.
Step 3: Research the customer's experience at each touchpoint
Touchpoint mapping tells you where interactions happen. This step tells you what those interactions feel like from the customer's side. Use a mix of methods: review analytics for behavioral data (bounce rates, time on page, conversion rates), analyze support tickets and sales call transcripts for qualitative signals, and conduct 5-10 customer interviews focused on their experience at specific moments. For each touchpoint, capture what the customer is trying to do, what emotion they're feeling, what information they need, and what friction they encounter. You've done this well when you can tell a specific story about a real customer's experience rather than a hypothetical one. Watch out for internal bias: teams tend to assume the customer's experience matches the intended design, and it rarely does. The skill of [identifying pain points and drop-off moments](/skills/identifying-pain-points-and-drop-off-moments) goes deep on techniques for surfacing where the journey breaks.
Step 4: Identify gaps, pain points, and moments of truth
With touchpoint research in hand, analyze the journey for three things. First, gaps: stages or transitions where the customer receives no communication, guidance, or support. The silence between purchase and first login is a classic gap. Second, pain points: moments where the customer encounters friction, confusion, or frustration. These show up as high drop-off rates, negative sentiment in feedback, or recurring support themes. Third, moments of truth: the high-stakes interactions that disproportionately shape the customer's overall perception. A moment of truth might be the first time a user achieves their core goal in your product, or how your team handles a billing dispute. You've done this well when you can rank your findings by business impact, connecting each gap or pain point to a metric like conversion rate, churn rate, or NPS. A variation: some teams use a red/yellow/green scoring system to visually grade each touchpoint and make patterns immediately visible to stakeholders.
Step 5: Design interventions for priority gaps
This is where analysis becomes action. For each priority gap or pain point, design a specific intervention. An intervention might be a new onboarding email sequence (retention gap), a comparison page on your website (consideration pain point), or a customer success check-in at day 30 (transition from purchase to retention). Prioritize interventions by expected impact and implementation effort. Not everything needs to be fixed at once. Focus on the two or three changes that address the largest pain points or the transitions with the steepest drop-offs. You've done this well when each intervention has a clear owner, a timeline, and a measurable outcome. The most common mistake is generating a massive list of improvements and trying to tackle all of them simultaneously, which diffuses effort and delays results. Another pitfall is designing interventions that optimize a single stage at the expense of another, like aggressive upselling during onboarding that hurts retention.
Step 6: Build a visual journey map to communicate findings
The journey map is the communication artifact. It translates your research and analysis into a visual that stakeholders across the organization can understand and act on. A good journey map shows the five stages as columns, with rows for touchpoints, customer actions, emotions, pain points, and opportunities. It should tell a story that anyone in the company can follow without attending a briefing. Keep it to one page or one screen. You've done this well when a new team member can look at the map and immediately understand where the biggest problems are and what's being done about them. The skill of [building visual customer journey maps](/skills/building-customer-journey-maps) covers format choices, tools, and templates in detail. A common mistake is treating the map as the end goal. The map is a communication tool. If it sits in a slide deck and nobody references it in planning meetings, it hasn't done its job.
Step 7: Establish stage-level metrics and review cadence
Each stage needs its own KPIs so you can monitor health over time. Awareness might track brand search volume and reach. Consideration might track demo requests, trial signups, or pricing page visits. Purchase tracks conversion rate and average deal size. Retention tracks churn rate, feature adoption, and support satisfaction. Advocacy tracks NPS, referral rate, and review volume. Define one primary metric per stage and set a quarterly review cadence. You've done this well when your leadership team can look at a dashboard and immediately see which stage is underperforming relative to the others. The skill of [measuring KPIs for each journey stage](/skills/measuring-journey-stage-kpis) provides detailed guidance on metric selection and benchmarking. The most common mistake is over-indexing on awareness and purchase metrics (because they're easiest to measure) while leaving retention and advocacy unmonitored. Another pitfall is measuring too many things per stage, which dilutes focus and makes it hard to know what's actually improving.
When to Use
- When your acquisition numbers look healthy but churn is climbing, and you suspect the problem lives somewhere between purchase and the third month of usage. The framework forces you to examine the post-purchase stages with the same rigor you apply to top-of-funnel marketing, revealing gaps in onboarding, early value delivery, or support responsiveness that your acquisition-focused dashboards don't surface.
- When multiple teams, marketing, sales, product, and customer success, are all working on 'the customer experience' but using different language, different metrics, and different mental models. The five-stage framework provides a shared vocabulary that lets a marketing manager and a support lead discuss the same customer without talking past each other. It's especially useful during cross-functional planning sessions or quarterly reviews.
- When you're launching a new product or entering a new market and need to design the end-to-end experience from scratch. Rather than defaulting to 'build the product, then figure out marketing, then figure out support,' the framework prompts you to design all five stages simultaneously, ensuring that the awareness promise aligns with the product reality and that retention and advocacy are considered before launch, not months after.
- When you have customer data scattered across tools, analytics for awareness, CRM for consideration and purchase, product analytics for retention, and NPS for advocacy, but no unified view of how a single customer moves through the lifecycle. The framework provides the conceptual spine that lets you stitch these data sources into a coherent narrative and spot the points where customers stall or disappear.
- When you're preparing a business case for investment in a specific part of the experience, like hiring more support staff or building an onboarding sequence, and need to show stakeholders how that investment connects to the larger lifecycle. The framework lets you point to a specific stage, quantify the drop-off, and argue for resources with a systems-level view rather than a departmental wish list.
When Not to Use
- When you're a very early-stage startup with fewer than 50 customers and your primary challenge is finding product-market fit. At this stage, the five-stage framework can encourage premature optimization of a lifecycle that isn't yet stable. You don't have enough data to meaningfully map touchpoints or measure stage-to-stage conversion, and the framework might give you a false sense of structure when what you actually need is rapid, unstructured customer discovery. Focus on talking to customers directly before formalizing their journey into five boxes.
- When the customer decision is genuinely instantaneous, like a low-cost impulse purchase with no consideration phase and no meaningful retention dynamic. Convenience store transactions or one-time event tickets don't benefit from five-stage analysis because several stages are either absent or trivially short. The framework assumes a meaningful lifecycle with multiple interactions, and it adds overhead without insight when applied to single-touch transactions.
- When your real problem is internal process dysfunction rather than customer experience gaps. If engineering can't ship on time, or if sales and marketing have a fundamental misalignment about ideal customer profile, mapping the customer journey won't fix those issues. The framework can actually mask organizational problems by redirecting attention to external touchpoints when the root cause is internal. Fix the organizational dysfunction first, then map the journey.
- When you're trying to understand a single, specific interaction in deep detail, like optimizing a checkout flow or reducing support ticket resolution time. The five-stage framework is a wide-angle lens. For micro-level optimization, you need tools like usability testing, task analysis, or service blueprints that zoom in on a single touchpoint rather than spanning the entire lifecycle. Using the five-stage model for this level of detail will produce vague recommendations.
- When the customer's actual behavior involves frequent, rapid switching between stages that the linear model can't capture. Complex B2B enterprise sales with multiple stakeholders, each at different stages simultaneously, can break the framework's assumption that a single entity moves through stages sequentially. In these cases, you may need account-level journey models or stakeholder-specific maps that the basic five-stage model doesn't accommodate without significant adaptation.
Examples
Example: SaaS project management tool with strong acquisition but 45% first-year churn
A 200-person SaaS company had 3,000 monthly trial signups and a healthy 12% trial-to-paid conversion rate, but first-year churn sat at 45%, well above the 25% industry benchmark. They mapped the customer journey and discovered a near-total gap between purchase and active retention. After payment, customers received a generic welcome email and were left to figure out the product themselves. The consideration stage was well-designed with comparison guides and demo videos, but the retention stage had exactly two touchpoints: a billing receipt and an annual renewal notice. The team designed a 30-day onboarding sequence triggered by purchase, added a customer success check-in at day 14, and built an in-app progress tracker showing users how to reach their first 'aha moment' of creating a shared project board. Within six months, first-year churn dropped to 31%. In retrospect, the team wished they had also mapped the advocacy stage earlier, because many of their best customers were quietly satisfied but had no channel to share their experience.
Example: Regional healthcare provider expanding to a second city
A healthcare network with 12 clinics in one metro area expanded to a neighboring city with 4 new locations. Their existing patient journey had been built organically over eight years and worked well in the home market, where brand awareness was high. In the new market, they applied the five-stage framework to design the experience from scratch. They discovered that awareness-stage touchpoints that worked in their home city (physician referrals, community events) didn't exist yet in the new market. They invested in localized search content, Google Business profiles, and partnerships with local employers for consideration-stage credibility. For the purchase stage (booking a first appointment), they simplified online scheduling to three clicks, compared to seven in their legacy system. At six months, the new clinics reached 70% of target patient volume, 15% ahead of projections. The lesson was that the framework prevented them from assuming their existing playbook would transfer to a new context without modification.
Example: D2C skincare brand discovering advocacy was driving 40% of new customers
A direct-to-consumer skincare brand with $8M in annual revenue mapped their customer journey and found something unexpected: 40% of new customers cited a friend or online review as their primary reason for purchasing, meaning advocacy was the dominant awareness channel. Yet the company was spending 65% of its marketing budget on paid social ads (a different awareness channel) and had zero investment in advocacy-stage touchpoints. They redirected 20% of their ad budget into a referral program with meaningful incentives, a post-purchase review request sequence timed to day 21 (when product results become visible), and a micro-community for repeat customers. Within a year, referral-driven purchases increased by 55% and overall customer acquisition cost dropped by 22%. The thing they'd do differently: they'd have surveyed customers about their discovery path much earlier rather than assuming paid media was the primary driver just because it was the most visible line item in the budget.
Example: B2B cybersecurity company with a 9-month sales cycle and 4 stakeholders
A cybersecurity company selling to mid-market enterprises had an average sales cycle of 9 months involving at least 4 stakeholders: a CISO (decision maker), an IT director (evaluator), a procurement lead (buyer), and a CFO (budget approver). They mapped the customer journey and realized they'd been treating it as a single linear path, when in reality each stakeholder entered the journey at a different stage and had different information needs. The CISO was typically in consideration mode before the IT director even reached awareness. Procurement entered only at the purchase stage and often stalled the deal with questions about compliance documentation that the sales team wasn't prepared for. The company built stakeholder-specific content tracks: a business-case template for the CFO, a technical evaluation guide for the IT director, a compliance checklist for procurement, and an executive briefing for the CISO. They also redesigned their CRM workflow to track which stakeholders had been engaged and at which stage. 5 months, a 28% improvement, primarily because procurement-stage friction was eliminated before it created delays.
Skills in This Method
Identifying Pain Points and Drop-Off Moments in the Journey
Techniques for diagnosing where customers experience friction, frustration, or abandonment at each stage of the journey using qualitative and quantitative data.
Building Visual Customer Journey Maps
Step-by-step process for creating visual journey maps that represent the five stages, including selecting formats, tools, and stakeholder collaboration techniques.
Mapping Customer Touchpoints Across Journey Stages
How to identify, catalog, and organize every customer interaction point within each of the five journey stages from awareness through advocacy.
Aligning Content and Channels to Each Journey Stage
How to match the right marketing content types, messaging, and communication channels to awareness, consideration, purchase, retention, and advocacy stages.
Activating Customer Advocacy and Referral Programs
How to systematically convert loyal customers into brand advocates through referral programs, reviews, testimonials, and community-building tactics.
Adapting the Five-Stage Journey Framework for B2B Contexts
How to modify the standard five-stage journey model to account for longer sales cycles, multiple stakeholders, and complex decision-making in B2B environments.
Measuring KPIs and Metrics for Each Journey Stage
Defining and tracking the right performance metrics—such as CAC, conversion rate, NPS, and CLV—for each of the five customer journey stages.
Designing Retention and Loyalty Strategies Post-Purchase
Practical methods for building post-purchase engagement programs, loyalty loops, and churn-reduction tactics within the retention stage of the journey.