Customer journey mapping is the work of recording, stage by stage, how a buyer moves from first hearing of you to paying you and coming back, using real evidence rather than a workshop's guesses. Done well, it tells you which one or two stages cost you the most revenue. This article sets out the customer journey mapping process from end to end: the evidence you collect, the sessions you run, and how to hold the finished map in the levelpartner.ai platform so it stays connected to live numbers.
Why evidence comes before the workshop
Most mapping starts with sticky notes. That produces a map of what the room believes. Start with records instead. Pull what the platform already knows about stage volumes and timings, read a sample of conversations, and talk to a handful of recent clients. Then run the workshop to explain what the evidence shows.
This order changes the conversation. Instead of debating whether buyers drop off after the first call, you are discussing why the people in your own records did, and how many of them.
Before you start
- At least three months of contacts and opportunities in the platform.
- A list of six to ten recent clients and three to five recent lost prospects willing to talk.
- One person from marketing, sales and delivery each.
- Half a day in the diary for the workshop.
How to set it up
- Note last quarter's stage counts from a Funnel widget on your dashboard.
- Read twenty conversation threads in Conversations, picked at random across stages.
- Interview five clients and three lost prospects about how they decided.
- Write each finding on a card, with its source noted underneath.
- In the workshop, sort the cards into stages from first contact to repeat purchase.
- Agree four to seven stages and name each in plain words.
- Under each stage, list the touchpoints, the buyer's main question and the main pain point.
- Pick the two stages with the biggest drop and agree one change for each.
- Update your pipeline in Opportunities > Pipelines to the agreed stage names.
- Add tags or custom fields that capture each pain point, so you can count it next quarter.
End to end customer journey mapping
End to end means the map does not stop at the sale. For most firms of 10 to 250 people, the cheapest revenue sits after the first purchase: renewals, upsells and referrals. A map that stops at "won" ignores it.
Include onboarding, first result, renewal and referral as stages. The platform can hold all of them: a second pipeline for client lifecycle, workflows for check-ins and review requests, and payments history for renewals. The customer success customer journey guide covers the post-sale half in detail.
Suppose the consultancy maps seven stages. Its pre-sale data shows a steady rate from enquiry to proposal. Its post-sale data shows that only 18 of last year's 60 clients bought a second engagement, and that none of them were asked. In that position, one change would matter more than the rest: a review call at day 90. These figures are illustrative.
Choosing who to interview
Pick clients who bought in the last six months, while the decision is fresh. Include at least one who nearly did not buy. Their hesitation tells you more than a happy client's praise. For lost prospects, choose people who reached a proposal or a quote, not cold enquiries who never replied.
Ask the same four questions each time: what started the search, who else they looked at, what nearly stopped them, and what made them decide. Record the answers on cards straight away, word for word where possible.
What it replaces
Mapping replaces the onboarding pack that describes the journey nobody follows, and the assumption that the firm's weak point is lead volume. In most stalled businesses, the map shows a conversion or retention problem, not a volume problem.
Time it takes
The first map takes about a week of part-time effort: two days of evidence gathering, half a day of workshop, and a day of platform changes. Afterwards, re-run the evidence every six months. That is a morning's work if the tags and fields are in place.
The mistake most people make
Mapping the ideal journey. Teams map what should happen and then wonder why the numbers do not match. Map what currently happens, including the awkward parts, and use a separate customer journey roadmap for the future state.
When not to map
Skip formal mapping if you have fewer than a few dozen clients a year. Talk to each of them instead. Also skip it if your pipeline data is empty or unreliable; fix the records first, otherwise the map rests on guesses again. If you only need a quick working draft, read map out customer journey for a one-afternoon version.
Troubleshooting
Interviews contradict the data
Both are useful. Data shows where buyers drop; interviews explain why. If they conflict on where, trust the data and dig into the interview.
The workshop produces twelve stages
Too much detail. Merge stages that share an owner and a buyer question until you have seven or fewer. Put the detail into customer journey steps instead.
Nobody uses the map after the workshop
It lives in a slide deck. Put the stage names into the pipeline and the dashboard, so the map is what people see every day.
Frequently asked questions
What is the customer journey mapping process in short?
Gather evidence, interview, run one workshop, agree stages, then put those stages into your pipeline and reporting. The last step is the one most firms skip.
Who should lead the mapping?
Someone who is not the head of any single team, so no stage gets special treatment. An operations lead often fits.
Do we need a separate map for each industry we serve?
Only if the stages differ. A mortgage broker and a real estate agency have different journeys; two service lines in the same agency usually share one.