The Five-Stage Customer Journey Framework

Created by Philip Kotler, Hermawan Kartajaya and Iwan Setiawan - https://www.wiley.com/en-us/Marketing+4.0%3A+Moving+from+Traditional+to+Digital-p-9781119341208

Overview

The five-stage customer journey framework divides a customer's relationship with a company into awareness, consideration, purchase, retention and advocacy. Each stage gets its own questions, touchpoints, owners and metrics, so a cross-functional team can look at one customer lifecycle and agree on where it leaks. The framework is used by marketing, product, sales and customer success teams that share a customer but measure different slices of the relationship.

The version most teams use today descends from a long line of funnel models. The oldest is AIDA (attention, interest, desire, action), which is commonly attributed to E. St. Elmo Lewis, while the earliest printed precursor was an anonymous three-step formula in Printers' Ink in 1898 (attract attention, then interest, then convince). AIDA ends at the sale. Later variants such as AIDAS added a satisfaction stage after the action, which was the first move toward treating the time after purchase as part of the journey.

The most direct published source for a five-stage path that runs from awareness to advocacy is the 5A customer path in Marketing 4.0, the book by Philip Kotler, Hermawan Kartajaya and Iwan Setiawan that Wiley published in December 2016. Its five stages are Aware, Appeal, Ask, Act and Advocate. MarkPlus, the consultancy Kartajaya founded, describes the 5A path as the successor to an earlier 4A model of Aware, Attitude, Act and Act Again, and defines Advocate as cultivating loyalty and advocacy among satisfied customers. Practitioners who wanted to retire AIDA have credited the 5A path as the needed update, because it accounts for how technology has changed the way people find, research and recommend brands.

The labels on this page are a practitioner rendering of that lineage rather than Kotler's own wording. Appeal and Ask collapse into consideration and Act becomes purchase. In the 5A path, retention and repurchase sit inside Advocate, which a review of Marketing 4.0 describes as loyalty shown through retention, repurchase and finally advocacy to others. The practitioner version pulls retention out as its own stage, with a dedicated owner and metric, because much of a subscription or repeat-purchase customer's value arrives after the first sale. Treat the five stages as a shared vocabulary built on that source, and cite Marketing 4.0 when someone asks where the idea came from.

The framework is also criticized, and the criticism is useful. Marc Stickdorn of the service design firm Smaply argues that the standard sequence of awareness, consideration, decision, retention and advocacy is a marketing-funnel convention weighted toward pre-purchase, and that teams should name stages after what customers actually do, such as getting started or hitting a wall. The two views fit together. Use the five stages as the top-level spine that every team recognizes, then break each stage into customer-named phases when you map it in detail.

The five stages describe a common pattern, and real customers often depart from it. Summaries of Marketing 4.0 point out that customers may not travel the 5A path in full or in order. A referral can take a buyer from awareness to purchase in a day, and a bad renewal can push a long-time customer back into evaluating alternatives. The value of the framework is that it makes every stage visible, including the post-purchase ones that acquisition dashboards tend to ignore.

Journey work also compounds with retention economics. Harvard Business Review summarized research that acquiring a customer costs five to 25 times as much as retaining one, and Frederick Reichheld's work at Bain found that a 5% gain in retention raised profits by 25% to 95% in the same article. Those figures are a reason to give the last two stages equal attention, not a forecast for any one business. If your team keeps its journey maps and stage definitions in Hamster, agents working on campaigns or onboarding can read the same stage model the team agreed on.

How the Stages Line Up with Earlier Models

Core Principles

Map the journey from the customer's side

Customers do not experience your org chart. They experience one continuous relationship that happens to pass through marketing, sales, product and support. Nielsen Norman Group recommends one actor and one point of view per map for exactly this reason. When a team maps its own process instead, it optimizes internal handoffs and leaves the customer's gaps untouched.

Each stage has its own job and its own metric

A prospect in awareness needs to learn that a problem is solvable. A customer in retention needs to keep getting value that justifies the cost. Mixing those contexts produces mismatched work, such as sending a comparison guide to someone who has not yet recognized the problem. Give each stage one primary metric, so a strong stage cannot hide a weak one in a blended revenue number.

Touchpoints are the unit of analysis

Stages stay abstract until you list the specific interactions inside them: an ad, a pricing page, a sales call, an onboarding email, a support ticket, a review site. Research on customer experience notes that customers now meet firms through myriad touch points across channels and media, and many of those are owned by someone else. Without a touchpoint inventory you cannot say where a stage breaks.

The transitions leak more than the stages

Teams tend to own stages, and nobody owns the gaps between them. The handoff from marketing to sales, the silence between signing and first use, and the quiet months before a renewal are where customers fall through. Name an owner for every transition, not only for every stage, and measure the conversion across it.

Treat the order as a convention

The stages are drawn left to right because that order is useful for planning. Real customers skip, loop and re-enter, which reviews of the 5A path note as well. Design each stage so that a customer arriving from an unexpected direction still finds what they need, for example a referred buyer who lands on the pricing page without having read anything else.

Advocacy is a result of the earlier stages

Referral programs and review prompts amplify advocacy that already exists, so they work best once customers are already satisfied. Bain's own description of Net Promoter says promoters are the customers who stay, buy more and generate most referrals, which means advocacy depends on everything before it. Fix retention before you fund an advocacy program.

Feed what you learn back to the start

Why customers stay or leave should change who you target in awareness and what you promise in consideration. The words that happy customers use should become the words in your acquisition copy. Run the framework as a loop with a review cadence, and the stages improve each other instead of being optimized in isolation.

Steps

1. Pick one segment and one journey Decide whose journey you are mapping before you map anything. A company with self-serve users, enterprise buyers and partner-led deals has three different journeys, and a single map of all of them helps no one. Start with the segment where revenue is concentrated or where you already suspect the largest gap. Describe that segment in specific terms: role, goal, constraints and how they usually find you. If the description reads "all users", narrow it before moving on.

2. Inventory touchpoints for every stage List every place the segment interacts with you or forms an opinion about you, stage by stage. Include touchpoints you do not own, such as review sites, community threads, analyst reports and peers. Pull from analytics, the CRM, support tickets and sales notes, and ask people in each department what they see. A good inventory surprises at least one team with touchpoints they did not know about. The touchpoint mapping skill covers the audit in detail.

3. Research the experience at each touchpoint The inventory says where interactions happen. Research says how they feel. Combine behavioral data with interviews, support transcripts and sales call notes, and capture for each touchpoint what the customer is trying to do, what they need to know and where they get stuck. Nielsen Norman Group's standard is that journey maps should be truthful narratives, not fairy tales, grounded in qualitative research. Mark any cell that rests on assumption so the team knows what still needs checking.

4. Find gaps, pain points and moments of truth Read across the research for three things. Gaps are stages or transitions where the customer hears nothing from you, such as the stretch between purchase and first login. Pain points are moments of friction that show up as drop-off, negative feedback or repeat support themes. Moments of truth are the few interactions that shape the whole relationship, such as the first time the product does the job it was bought for. Rank all three by their effect on a stage metric.

5. Design interventions for the top few problems Pick the two or three problems with the largest effect and design a specific change for each: a new onboarding sequence, a comparison page, a check-in call before renewal. Give each change an owner, a date and the metric it should move. Check that a fix for one stage does not damage another, for example an aggressive upsell during onboarding that lifts expansion revenue and hurts retention. Resist the long list; spreading effort across twenty fixes delays all of them.

6. Visualize the journey so others can act on it Turn the research into a one-page map with the stages as columns and rows for touchpoints, customer actions, emotions, pain points and opportunities. The map is a communication tool, so a new team member should understand the biggest problems without a briefing. Keep it where planning happens, not in a slide deck nobody opens. The journey map skill covers formats and facilitation.

7. Set stage metrics and a review cadence Choose one primary metric per stage and look at them together on a fixed cadence, usually quarterly. Typical choices are branded search or reach for awareness, trial or demo starts for consideration, conversion for purchase, churn or renewal for retention, and referral rate or Net Promoter Score for advocacy. Watch for the common tilt toward awareness and purchase metrics simply because they are easier to collect. The stage KPI skill covers definitions and instrumentation.

When to Use

• Acquisition looks healthy but churn is rising. The framework forces the post-purchase stages to get the same scrutiny as the top of the funnel, which is usually where the unexplained loss sits.
• Marketing, sales, product and success all work on "the customer experience" with different words and metrics. Five named stages give them one vocabulary for planning and for arguing about priorities.
• You are launching a product or entering a market and need to design the whole relationship at once. Designing all five stages together keeps the promise made in awareness consistent with what the product delivers in retention.
• Customer data is spread across the ad platform, the CRM, product analytics and survey tools. The stages give you a spine to join those sources into one view of how a customer moves.
• You need a business case for investment in one part of the experience, such as onboarding or support staffing. Pointing to the drop-off at a specific stage makes the case in customer terms rather than as a department's request.

When Not to Use

• You are still searching for product-market fit with a handful of customers. The lifecycle is not stable yet, and unstructured customer conversations will teach you more than a formal map.
• The purchase is a single impulse transaction with no evaluation and no repeat relationship. Several stages are empty, and the framework adds overhead without insight.
• The real problem is internal, such as sales and marketing disagreeing on the ideal customer. A journey map can hide that disagreement behind customer-facing fixes; resolve it first.
• You need to optimize one interaction in depth, such as a checkout form. Use usability testing or a service blueprint, which shows the frontstage and backstage work behind a single touchpoint.