A B2B customer journey map example. What it looks like with a real buying committee.

Why this matters. A B2B journey has a committee in it, not one customer.

A B2B customer journey map has to account for the fact that "the customer" is rarely one person. Gartner's research on B2B buying puts the typical purchase decision at six to ten stakeholders once you count the economic buyer, the technical evaluator, the day-to-day user, procurement and, on anything with contract or data implications, legal. Map the journey as if it were one person's path from awareness to purchase, the way most generic templates do, and you'll miss the point where deals actually stall: the internal negotiation between people who want different things from the same decision.

Gartner's own 2025 buyer research found that 74 percent of B2B buying teams show what it calls unhealthy conflict during the decision process, disagreement severe enough to slow or derail a deal, not the normal back-and-forth of a group making a decision together. A journey map that only tracks the champion's experience is blind to exactly the friction that kills most deals. A proper B2B map, built on the same discipline covered in our guide to customer journey mapping, tracks each stakeholder's questions separately, stage by stage, alongside the single shared journey the deal as a whole moves through.

The list, with how to apply each. A worked six-stage B2B example.

If you haven't mapped a journey before, our plainer explainer on what a customer journey map actually is covers the basic structure this example builds on. Here is what it looks like once a real B2B buying committee is involved.

1. Problem recognition, where a champion notices the gap

Someone inside the business, usually a manager rather than the final decision-maker, notices a cost, a delay or a workaround that has become too expensive to keep tolerating. At this stage the map should track what triggered the search (a missed target, a new hire who can't get set up quickly, a competitor doing something better) and where that person goes first: a peer, a search engine, a LinkedIn post, rarely a vendor's website.

2. Vendor shortlist, where the champion builds a case

The champion narrows a list from many options to two or three, and starts building an internal case for why this problem is worth solving now. The map should record what convinces them to shortlist a vendor (a specific, named result, not a generic claim) and what they need from you to build that internal case: a one-page summary they can forward, not a forty-slide deck they have to summarise themselves.

3. Technical evaluation, where a different person asks different questions

A technical evaluator, often not the champion, joins to check integration, security and implementation effort. Their questions are almost never the champion's questions: not "will this solve my problem" but "will this break something else, and how much work is it to set up." Miss this stage in the map and you'll keep answering commercial questions to someone who is actually blocked on a technical one.

4. Procurement and legal, where the deal can quietly stall

Contract terms, data processing agreements and payment terms move to procurement and legal, who were not in any earlier conversation and have no relationship with you at all. This is where B2B deals go quiet for weeks, not because interest has cooled, but because the paperwork stage has its own separate, slower clock that the sales conversation doesn't control.

5. Executive sign-off, where the case has to survive a retelling

The champion presents the case to whoever holds budget authority, usually without you in the room. The map should account for the fact that your pitch gets retold by someone else, under time pressure, to someone who has not seen any of the earlier stages. What you gave the champion to carry that retelling matters more here than anything you said directly.

6. Onboarding and the first honest verdict

The champion who fought for this purchase is now personally exposed if it doesn't work. The first 90 days decide whether they become an internal advocate for renewal and expansion, or quietly stop defending the decision when it comes up. Map this stage with the same attention as the sale itself; most B2B journey maps stop at the signature and miss where retention and expansion actually get decided.

Picture a workflow software vendor selling a mid five-figure annual deal into a 200-person logistics operator. The ops manager who first raised the problem spent three weeks building an internal business case before procurement ever saw a contract, and the deal very nearly died in week six when legal flagged a data residency clause nobody on the champion's side had thought to ask about earlier. Mapping the journey by stakeholder, not just by stage, would have surfaced that question in week two instead of week six, while there was still time to answer it without the whole deal losing momentum.

Where teams go wrong. Mapping the champion's journey and calling it done.

The most common mistake is building one journey for "the customer" when there are five different people with five different sets of questions inside that one deal. A map that only reflects the champion's experience will always miss where procurement, legal or a technical evaluator quietly stalled things, because nobody was tracking their journey at all. See where customer journey pain points actually hide for the single-journey version of this same mistake.

The second is assuming the map ends at the signature. The onboarding period is where a champion either becomes an advocate who fights for renewal, or goes quiet, and a map that stops at "deal closed" misses the exact window where that gets decided.

The third is treating every B2B deal as if it has the same committee. A small deal might genuinely be a one or two-person decision; a deal with legal, compliance and multi-year budget implications might involve eight. Use the actual buying group for this specific deal, not a generic template borrowed from a different sales motion. Our fuller free customer journey map template is a good starting structure for a simpler, single-buyer journey; the moment a second stakeholder with a different agenda enters the picture, that structure needs the stakeholder-by-stage view this example uses instead.

My rule with any B2B deal above a handful of stakeholders: map the paperwork stage as carefully as the pitch. Reps spend disproportionate energy on the parts of the journey they can see and influence, the demo, the proposal, and almost none on procurement and legal, which is exactly where deals that felt "basically done" quietly die. It's the same commercial discipline behind the wider growth consulting work we do: fixing the parts of the funnel that are invisible until you go looking for them.