Customer journey mapping that finds where revenue leaks.

Most businesses know they lose customers somewhere between the first ad click and the second purchase. They just can't point to where. The signup looks fine. The product is good. The team is busy. Yet conversion sags, onboarding drags, and renewals slip, and nobody can say exactly which step is doing the damage. That gap between what you feel and what you can prove is the gap customer journey mapping closes.

A customer journey map is the full picture of how someone moves from never having heard of you to buying again and recommending you. It records what they do, what they're trying to achieve, what they're thinking and feeling, and which of your touchpoints they hit at each stage. Laid out end to end, the friction becomes obvious. The point where people go quiet, the form that loses half its visitors, the onboarding email that never lands: these stop being hunches and start being things you can fix.

This page explains what mapping is, why it pays for itself, and how I run it so the map becomes action rather than a poster on a wall.

What customer journey mapping actually is.

A customer journey map is a visual record of the stages a customer passes through with your business, and what happens to them at each one. The stages usually run something like awareness, consideration, decision, onboarding, use, and loyalty, though the right set depends on your business. For each stage you capture four things: what the customer is doing, what they want, what gets in their way, and which team or system owns the touchpoint.

It is not a sales funnel. A funnel counts volume dropping through stages from your side of the glass. A journey map sits on the customer's side and follows the whole relationship, including everything that happens after the sale, where most of the lifetime value actually lives. The funnel tells you how many people fall out. The map tells you why.

It is also not a one-off workshop artefact. The best customer journey map is a working document that ties to real data and gets revisited when the product, pricing or market shifts. A diagram that nobody has opened since the offsite is just decoration.

Why mapping matters commercially.

The reason to map a journey is money, not aesthetics. Every stage with friction is a place where customers you've already paid to acquire quietly leave. You spent on the ad, the content, the sales time. Then a confusing checkout, a slow onboarding, or a renewal nobody followed up on hands that investment back. Mapping makes those leaks visible so you can stop them in priority order.

Three things tend to surface the moment a journey is laid out honestly:

• The drop-off you can't see in aggregate. Top-line conversion looks acceptable, but a single step is shedding customers. Find it and the whole number moves.
• The handoff nobody owns. Marketing thinks sales has it, sales thinks onboarding has it, and the customer sits in the gap getting no reply. These seams between teams are where most journeys break.
• The effort the customer carries. Repeating information, chasing for an answer, hunting for a feature. Every bit of friction you remove is a reason to stay.

For a scaling or SaaS business this compounds. A small lift in trial-to-paid conversion, or a few points off churn, repeats every month against a growing base. Mapping is one of the few exercises that improves acquisition efficiency and retention at the same time, because it looks at the entire relationship rather than a single funnel stage. It pairs naturally with conversion rate optimisation on the front end and with retention work after the sale.

How to create a customer journey map: the way I run it.

Here is how I approach customer journey mapping in a client engagement. It is deliberately practical. The aim is a map you can act on within weeks, not a beautiful diagram that sits in a drawer.

1. Pick one segment and one goal

A map that tries to cover every customer type at once covers none of them well. We start with a single, valuable segment and one journey, for example a trial user reaching their first real outcome, or an enterprise buyer moving from demo to signed contract. One segment, one goal, one map. We add others later.

2. Define the stages from the customer's side

We set the stages in the customer's language, not your org chart. Then for each stage we write down what they're doing, what they want, what's getting in the way, and how they feel. The emotional line matters more than people expect: the moments of frustration and relief are usually exactly where revenue is won or lost.

3. Bring in real data, not opinions

This is where most maps fall down and where I spend the effort. We pull actual behaviour from your CRM, your product analytics and your support desk: where deals stall, where signups abandon, what people contact you about, how long each stage really takes. A workshop tells you what the team believes. The data tells you what customers actually do, and the two are rarely the same. Getting this right depends on your systems holding clean, joined-up records, which is why mapping so often surfaces a CRM implementation or data-quality problem underneath.

4. Mark the friction and quantify it

With the journey laid out and the data attached, the friction points show themselves. We mark each one and put a rough number against it: how many customers it affects and what they're worth. That number is what turns a long list of annoyances into a ranked set of priorities. Not everything broken is worth fixing first.

5. Turn the map into a fix list with owners

This is the step that separates a useful map from a poster. Every priority friction point becomes a specific change, with a named owner and a date. Rewrite the onboarding sequence. Close the gap between sales and fulfilment. Add the missing renewal prompt. The map is the diagnosis. The fix list is the treatment, and that is the part most exercises skip.

6. Wire it into your operations

Finally we connect the fixes to how the business runs day to day, so the improvements hold instead of decaying. That usually means tightening the handoffs in your CRM, setting up CRM automation for the prompts and follow-ups that were being missed, and agreeing how you'll measure whether each fix worked. A journey map that changes how the team operates is worth far more than one that changes how a slide looks. This is where mapping connects to broader revenue operations: the map shows where the journey breaks, and operations is how you keep it fixed.

What a finished map looks like.

People picture a customer journey map as a swooping infographic. In practice the useful version is closer to a table: one row per stage, columns for what the customer is doing, what they want, the friction, the touchpoint owner, and the data point that proves it. Here is a stripped-back example for a SaaS trial journey, so you can see the shape of it.

Stage	What the customer is doing	Where it leaks	Owner
Awareness	Clicks an ad, lands on the site, sizes you up in seconds	The page answers a different question than the ad asked	Marketing
Signup	Starts the trial, hits the form	Too many fields, abandons halfway	Product / growth
First use	Tries to reach a first real outcome	No guided path, stalls before the value moment	Onboarding
Decision	Weighs up paying	Nobody reaches out, the trial just expires	Sales
Renewal	Comes up for renewal	No prompt, no check-in, quietly churns	Success

Each leak in that table is a number you can size and a fix you can own. That is the whole point: the map is the diagnosis, laid out so the next move is obvious.

The mistakes that waste the exercise.

I get called in as often to rescue a stalled mapping effort as to start one. The same few mistakes come up:

• Mapping the ideal journey instead of the real one. A map of how you wish customers behaved hides every problem worth finding. Use the data, not the brochure.
• Stopping at the diagram. A lovely map with no fix list, no owners and no dates changes nothing. The output is action, not a picture.
• Doing it in a marketing silo. If sales, onboarding and support aren't in the room, you'll miss the handoffs, which is exactly where most journeys break.
• Trying to map everyone at once. One segment done well beats five done vaguely. Start narrow.

Customer journey mapping tools.

People ask about customer journey mapping tools early, usually too early. The honest answer is that the tool barely matters at the start. A spreadsheet, or a shared board in Miro or FigJam, is plenty for the first map. What matters is the thinking and the data behind it.

Where tools earn their place is in the data layer underneath the map. Your CRM, your product analytics and your support platform are where the real journey lives. If those systems are clean and connected, the map writes itself from evidence. If they aren't, you end up mapping opinions, and dedicated journey software won't save you. Purpose-built tools such as Smaply or UXPressia are genuinely useful once the practice is established and you're maintaining several maps, but they are not where you begin.

So the order is: get the map and the data right first, standardise it once it works, and only then reach for a dedicated tool. Buying software before you've done the thinking just gives you a tidier version of a guess.

What working with me includes.

When you bring me in to map a journey, here is what the engagement covers:

• Discovery and data pull. I get into your CRM, analytics and support data, and talk to the people who own each touchpoint, so the map is built on what's really happening.
• The map itself. A clear, end-to-end customer journey map for your priority segment, with stages, actions, friction points and emotional lows marked against real numbers.
• A ranked fix list. The friction points turned into a prioritised set of changes, each with an owner, an expected impact and a date, so you know exactly what to do on Monday.
• The operational wiring. The CRM, automation and reporting changes that hold the fixes in place and tell you whether they worked.
• A working document, not a one-off. A map your team can keep current, plus a simple rhythm for reviewing it as the business changes.

I work with founders and operators of scaling and SaaS businesses, and with hospitality and hospitality-tech teams across the Middle East and beyond, where the journey often spans booking, on-property experience and return, and the handoffs between them are exactly where guests are lost. The method is the same: follow the customer, find the leaks, fix them in order.

From map to action.

A customer journey map is only worth building if it changes what you do. The version I run is built to do exactly that: start with one segment, ground it in real data, find where customers stall and revenue leaks, and hand you a short list of fixes with names and dates against them. The diagram is the easy part. Knowing which leak to plug first, and making sure it stays plugged, is the work that pays for itself.

For the B2B side of this specifically, see our guide to mapping the buyer journey, which covers the buying-committee stages and stakeholders a purchase-focused map needs to account for before a deal ever reaches signature.