B2B Customer Journey Mapping: Adapting the Five Stages

Adapt B2B customer journey mapping to buying groups, long cycles and account-level journeys, with a layer for each role in the deal.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

B2B customer journey mapping starts from the same five stages as any journey, but the customer is a group rather than a person. Awareness, consideration, purchase, retention and advocacy still apply, yet each stage involves several people with different goals, and any of them can stop the deal. A Harvard Business Review article on B2B buying found that unilateral decision makers are now rare: purchases are made by groups whose members all have veto power.

That breaks two assumptions in the standard five-stage customer journey framework. The first is that one actor moves through the stages. In a B2B deal, the person who discovers the problem may be in consideration while the finance approver has not heard of you, and the eventual daily users only arrive in retention. The second is that purchase is a single moment. In practice it is a sequence of internal approvals, security reviews and procurement steps, many of which happen without you.

The adaptation keeps the five stages as the spine and adds three things. It maps the journey at the account level, with a layer for each buying role. It marks the consensus points where the group must agree before moving on. And it maps the internal selling your champion has to do, because much of the consideration and purchase work happens in meetings you are not in.

Use this skill when deals stall without a clear reason, when a single-persona map does not match what sales sees, or when retention depends on users who were never part of the purchase.

How It Works

The core of the adaptation is one map per account type, with parallel rows for each role in the buying group. Nielsen Norman Group recommends one point of view per journey map to keep a map coherent. In B2B, the way to respect that while covering the group is a layered map: one swim lane per role, all sharing the same stage columns, so you can see where the roles are out of step.

Typical roles include the person who feels the problem, the champion who drives the purchase, the economic buyer who approves spend, technical or security evaluators, procurement, and the end users who will live with the product. Each role has its own questions and its own reasons to say no. The champion wants to look smart for choosing well. The security reviewer wants to avoid a risk they will be blamed for. The end users want the new tool not to make their week harder.

Consensus points are the transitions where the group must agree. The HBR authors describe buying groups in which all members hold veto power, which means these points are where deals die quietly. Common consensus points are agreeing that the problem is worth solving, agreeing on a shortlist, and agreeing to sign. Marking them on the map shows what content or help the group needs to get there.

Internal selling is the work the champion does inside their own company: building a business case, answering objections from colleagues, presenting to leadership. Much of it is invisible to the vendor. Mapping it as touchpoints the champion owns, and supplying material for each, turns it from a black box into something you can support.

Retention and advocacy also shift. The people who bought are often not the people who use the product. A B2B retention stage needs its own actor, usually the end users and their manager, and renewal is a new purchase decision that may involve new approvers.

Step-by-Step Guide

Step 1: List the roles in recent buying groups

Review recent won and lost deals in the CRM and list every role that took part, including those who appeared late, such as security or legal. Talk to account executives about who blocked or sped up deals. Keep the list to the roles that appear in most deals and note the occasional ones separately. This list becomes the swim lanes of the map.

Step 2: Map each role against the five stages

For each role, write what they do, what they want to know and what would make them say no in each stage. Many roles will be empty in some stages, which is a finding in itself. Use interviews with won and lost customers to fill the lanes, not only the sales team's view. Keep the stage columns identical across roles so the lanes line up.

Step 3: Mark the consensus points

Find the transitions where the group must agree before moving on, such as agreeing the problem is worth budget or agreeing on a shortlist. For each consensus point, note which roles must agree and what evidence they need. These are the places where stalled deals usually sit. Compare them with where recent deals stalled in the CRM.

Step 4: Map the internal selling your champion does

List what the champion must produce or survive internally: a business case, a security questionnaire, a presentation to the budget holder, answers to colleagues' objections. Treat each as a touchpoint owned by the customer. Note which ones you currently support with material and which you leave to the champion. Gaps here often explain long cycles.

Step 5: Plan for late-arriving stakeholders

Some roles join late, often security, legal or a new executive. Design a short path that brings a late arrival up to speed without restarting the evaluation: a summary of the decision so far, answers to their typical questions, and a named contact. Place this path on the map at the point where late arrivals usually appear.

Step 6: Redefine retention and advocacy for the account

Add the end users and their manager as the main actors in retention, and map their onboarding and adoption separately from the buyer's experience. Treat renewal as a new purchase decision and note which approvers it involves. For advocacy, note who in the account can act as a reference, which is often a user rather than the buyer.

Step 7: Check the map against lost deals

Walk a handful of recent lost deals through the map and see whether it explains where they stopped. If a deal stalled for a reason the map does not show, add the missing role, consensus point or internal step. Repeat the check each quarter with new deals. A map that explains losses is one sales will trust.

Step 8: Assign owners across sales, marketing and success

Give each consensus point and each internal-selling gap an owner: marketing for content, sales for deal support, success for onboarding and renewal. Tie each owner to a stage metric, such as time from shortlist to decision. Review the map with those owners on the same cadence as pipeline reviews.

Best Practices

• Interview lost deals, not only won ones. Won customers explain what worked. Lost ones show where the group disagreed or which role said no.
• Write for the champion's internal audience. Business-case templates, security summaries and short executive briefs help your champion sell inside their company. They are often more useful than another demo.
• Keep the stage columns identical across roles. Shared columns make it obvious when one role is in consideration while another has not started.
• Separate buyers from users in retention. The people who signed rarely use the product daily. Map and measure the users' journey separately.
• Treat renewal as a new decision. New approvers, new budgets and new alternatives appear at renewal. Plan for the consensus the renewal needs.
• Update the roles list as deals change. New roles appear as deal sizes grow or regulations change. Revisit the list when the CRM shows new titles in buying groups.

Common Mistakes

• Mapping only the champion: A map of the champion's journey hides the roles that actually stop deals. Add a lane for every role that can veto.
• Treating purchase as one event: Signing is the end of a chain of approvals. Map the chain so you can support each step.
• Assuming the buyer is the user: Retention built around the buyer misses the people who decide whether the product sticks. Map the users as a separate actor.
• Building the map from sales opinion alone: Account executives see only part of the group's work. Add interviews with customers, including ones you lost.
• Using consumer stage lengths: B2B consideration and purchase can take much longer than consumer journeys. Set expectations and metrics from your own deal history.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: The Five-Stage Customer Journey Framework

Related Skills

• How to Create a Customer Journey Map That Drives Action
• Customer Journey Touchpoints Mapping Across Five Stages
• Designing Customer Retention Strategies for Loyalty

Sources

• HBR: Making the Consensus Sale
• Nielsen Norman Group: Journey Mapping 101

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.