Why customer journey mapping in B2B rarely works
Let's start with a situation you probably know. Your company has three sources of truth about the customer: the salesperson's notes in the CRM, data from website analytics, and what the customer says in a meeting. Each of these sources describes a different fragment of the same story, but nobody puts them together. The result is that decisions about campaigns, content, and the order of contact are based on gut feeling rather than on what actually happens in the buying cycle.
A customer journey map is supposed to change that. In theory, it is an analytical tool that visualizes the process of a person moving from the first, still dormant need all the way to purchase and use of a product or service. Kreutzer (2019, p. 87) points out that such a visualization helps identify the customer's important needs and possible pain points, meaning the places where the customer stops, doubts, or gives up. Sounds simple. In practice, most B2B maps do not work because they are created in isolation from data and from the team that would later use them.
In B2B the problem is even more complex. A purchase usually involves several people: a technical person, a financial decision-maker, sometimes procurement, and the end user. Each of them has a different journey map, different questions, and different touchpoints with the brand. One shared map for everyone usually dissolves into generalities and stops being useful.
Where to start so the map is not fiction
Start with the persona and the scenario, and leave the list of channels for later. Kreutzer (2019, p. 92) states directly that creating a customer journey map starts with personas, and for each persona you need to develop a separate map. This matters because in B2B the most common mistake is making one map for "the customer" when in reality you are dealing with a buying committee.
In practice it looks like this: choose one role, for example the person responsible for implementation on the client side, and describe a specific scenario. Not "the customer is looking for a solution", but "the customer was instructed by the board to organize the process within a quarter and is looking for a contractor". The scenario must have a goal and a starting point, because without that the map turns into a wish list.
Only then do you describe the phases: need recognition, information gathering, comparing options, decision, implementation, use. In each phase you record three things: what the person does, what they think, and what they feel. Emotions are crucial here because they show where friction appears. A salesperson will tell you the customer "is thinking about it". The map should show that in the comparing phase the customer feels uncertainty because they have no way to verify your claims without talking to your current client.
If you want to see how such conclusions translate into concrete campaign actions, take a look at our approach to B2B marketing strategy, where we treat the map as a starting point, not as an addition to a presentation.
Brand touchpoints: where you really collect data
Brand touchpoints are all the places where the customer comes into contact with your company: website, LinkedIn, webinar, email, conversation with a salesperson, invoice, onboarding, technical support. Most teams list a dozen or so, and then discover they only have data on three.
Do a simple test. For each touchpoint, answer two questions: do I know how many customers pass through it, and do I know what happens there when something goes wrong. If you do not have an answer to either question, that touchpoint is in reality an assumption. Assumptions are the most expensive part of the map because you base your budget on them.
In B2B it is especially easy to omit touchpoints that are not "marketing". A conversation with the technical department before signing the contract, a visit to the plant, an exchange of emails with accounting about payment. All of this influences the decision to repurchase and whether the customer recommends you further. A customer journey map that ends at contract signing describes only half of reality.
It is also worth separating touchpoints you control from those you do not control. Opinions in industry groups, comparisons at competitors, recommendations online. You will not influence them directly, but you can make sure the customer has something to share.
-
1
Need recognition
The customer sees a problem but is not yet looking for a supplier. Question: how to solve this at all?
-
2
Information gathering
The customer learns about solution categories and possible providers. Question: who handles this and how does it work?
-
3
Comparing options
The customer narrows the list and looks for evidence. Question: will this company actually deliver what it promises?
-
4
Decision
The client selects a vendor and has to justify the choice internally. The question: what risk am I taking on?
-
5
Implementation and usage
The client works with the solution and evaluates whether they chose well. The question: will it be just as good after the contract is signed?
How to read the map so it drives decisions
The map itself is just a picture. Its value appears when you turn it into a list of decisions. The simplest way is to go through each phase and write down three things: where we lose clients, where we lose time, and where we lose credibility.
An example from agency practice. A client in the manufacturing industry had a high-performing website and a high number of inquiries, but a low conversion rate to meetings. The map showed that the problem was not in the campaign, but at a touchpoint everyone overlooked: the first reply email from the salesperson. Marek from the sales department sent his response after 47 hours. By then the client had written to three competitors, and in an email to us he wrote briefly: "I have already received offers from two companies, if this is still relevant for you, please get in touch by Friday." Marek's template contained no question about context, just a PDF with an offer. Changing the template and cutting response time to four hours delivered more than another campaign.
The second way to read the map is to compare it with analytics data. Caution is useful here, because classic metrics such as recency, frequency, and monetary value look backward. As Kumar (2018) notes, these metrics do not account for a client's future potential, and methods based on CLV, meaning customer value over the entire relationship, better reflect future profitability. In the map this means one thing: not every client who bought quickly is as valuable as the one who took six months to mature but will stay for years.
The third way is to look for places where the client has to repeat something. If the same document reaches you three times, if the client has to explain twice what their business does, that is a signal that your touchpoints are not connected. In B2B this kind of friction costs the most, because the client reads it as a preview of what working together will look like.
Customer journey in B2B and lead generation
The customer journey map and lead generation are two views of the same process. The map tells you where the client is and what they need. Lead generation answers how to get them there and how to recognize that they are ready for a conversation.
Without a map you do this blindly. You send the same content to everyone, measure the number of form submissions, and wonder why the leads are low quality. With a map you see that in the need recognition phase the client is not looking for a vendor, only for a way to solve the problem. That is when the content that works is a diagnosis, not an offer. In the comparison phase the client looks for evidence, so a case study and a conversation with a current client work. In the decision phase the only thing that matters is whether you can take the risk off the person who signs.
This distinction translates directly into how you build B2B lead generation. Instead of one funnel you have several paths, each with a different opening question and a different qualification criterion. A lead who filled out a form after a webinar about implementation is in a different place than one who downloaded a cost calculator. Treating them the same is the most common reason salespeople stop trusting marketing leads.
| A map as a presentation | A map as a decision-making tool | |
|---|---|---|
| Who creates it | Marketing only | Marketing, sales, technical support |
| Starting point | A list of channels | A persona and a specific scenario |
| Data | Intuition and assumptions | Data from CRM, analytics, and customer conversations |
| Output | A document in a folder | A list of changes with owners and deadlines |
| Review | None | Every six months or after a change in the offer |
The most common mistakes in customer journey mapping
The first mistake is creating the map once and treating it as a document forever. The B2B buying cycle changes along with the market, budgets, and who makes the decisions. A map without a date and an owner ages faster than a price list.
The second mistake is a map created only by marketing. If the workshop has no salesperson, no technical support, and no one who talks to customers after implementation, you get a nice picture of what marketing would like to be true.
The third mistake is the lack of decisions at the end. A map that does not end with a list of changes in the process, content, or tools is a costly exercise. It is worth assigning every finding to a person and a deadline right away, even if it is just a change to a single email.
The fourth mistake is ignoring the customers you lost. A conversation with someone who chose a competitor gives you more than ten conversations with satisfied customers. In the map, this is the most valuable point, because it shows exactly where things broke.
The fifth mistake is too much detail at the start. A map with fifty touchpoints and twenty personas will not get used. It is better to start with two personas and one scenario, and add the rest as needed.
FAQ: the most common questions about customer journey maps
What is a customer journey map in B2B?
It is a visualization of the process a person goes through from the first appearance of a need to the purchase and use of the service. In B2B, it is created separately for each role in the buying committee, because the decision-maker, the user, and the technical person have different questions and different touchpoints with the brand.
Where do you start when creating a customer journey map?
With a persona and a specific scenario, not with a list of channels. Describe the goal with which the person enters the process, what actions they take at each stage, and what they think and feel. Only then assign touchpoints to the stages and check which of them you have real data on.
How long should a customer journey map stay up to date?
In B2B, a sensible rhythm is a review every six months and an update after any major change in the offer, pricing, or sales team structure. A map without an owner and a review date quickly stops matching reality.
How do you connect a customer journey map with lead generation?
By separating the paths. Each stage in the map represents a different customer question, so it calls for different content and a different lead qualification criterion. This way, the salesperson receives a contact with information about what stage the customer is at, not just a phone number.
Does a customer journey map work in a short sales cycle?
Yes, but then it is shorter and more focused on a single touchpoint, for example the pricing page or the first conversation. The value still lies in the same thing: showing where the customer stops and why.
Sources
- Kreutzer, R. T., Customer Journey Map, in: Toolbox for Marketing and Management, 2019
- A study on customer analytics, the section on RFM and CLV metrics