How to Map a SaaS Customer Journey, Step by Step
TLDR
A customer journey map is a simple table that traces what a person does, thinks, and struggles with at each stage of using your product, from first hearing about it to becoming a regular. For SaaS, its real job is finding where clarity breaks in your funnel. This guide walks a worked example and shows you how to build the map yourself in a spreadsheet.
WHO THIS IS FOR
This is for founders and product or marketing people who know users are leaking somewhere between the ad click and the renewal, and want a cheap, honest way to find out where. No workshop required. A spreadsheet and an afternoon will do.
What is a Customer Journey Map?
A customer journey map is a visual or tabular document that lays out the stages a customer moves through with a product, and records what they do, think, feel, and struggle with at each one. Its purpose is to expose the gaps between how a company imagines the experience and how customers actually live it.
Why Map the Journey at All?
Because every team has a version of the journey in their heads, and it is wrong in ways that cost money. The map exists to replace the imagined journey with the real one.
Inside a company, the journey looks like the funnel diagram: ad, homepage, signup, onboarding, activation, renewal, a tidy left-to-right flow. From the customer's side, it is nothing like that. They saw your product mentioned somewhere, forgot about it, hit the problem again three weeks later, searched, landed on a comparison page you did not write, opened your pricing before your homepage, signed up on a phone during a commute, and stalled at an empty dashboard. The map is where those two stories get reconciled, and the gaps between them are your fixable problems.
We keep coming back to one idea in this work: the distance between what a product does and what a person thinks it does, the Perception Lag. A journey map is the cheapest instrument for finding where that lag lives, because it forces you to write down what the customer believes at each stage, not just what they click.
What Are the Stages of a SaaS Customer Journey?
Six stages cover almost every SaaS product: awareness, evaluation, signup, activation, adoption, and renewal. B2C tools compress them, enterprise stretches them, but the sequence holds.
Awareness is when the person first learns you exist, usually in a place you do not control. Evaluation is the comparison window: your site, a competitor's, a Reddit thread, a pricing page. Signup is the moment of commitment, small as it is. Activation is the first real result inside the product, the moment the promise gets kept or broken. Adoption is the stretch where the product becomes a habit rather than an experiment. And renewal, or expansion, is where the quiet verdicts of every earlier stage show up as a number on your dashboard.
The mistake most first-time mappers make is spending all their ink on awareness and evaluation, the marketing stages, and skimming activation and adoption, the product ones. For SaaS, the money is in the middle. A SaaS customer journey lives or dies between signup and habit, which is exactly where most companies have never looked closely.
How Do You Build the Map?
A real map has stages across the top and a handful of rows down the side. You can build it in any spreadsheet in an afternoon. Fill it with evidence, not with what the roadmap says should be happening.
- Pick one customer type. One map per audience. A map that averages a solo founder and an enterprise buyer describes nobody, and every insight in it is mush.
- Lay out the six stages as columns. Awareness, evaluation, signup, activation, adoption, renewal. Rename them to fit your product if you need to, but keep the spine.
- Fill five rows per stage: what they do, what they are thinking, what they feel, where the friction is, and which touchpoint they are on. The thinking row is the one teams skip and the one that finds the clarity gaps.
- Use evidence, not assumptions. Session recordings, support tickets, cancellation reasons, five real conversations. Where you have no evidence, mark the cell as a guess. The guesses are a research to-do list.
- Mark the moments of truth. Every journey has two or three points where people either commit or quietly leave. In SaaS, it is usually the first session and the second one. Circle them.
- Turn the worst gap into one fix. The map is not the deliverable. Pick the biggest friction at the most important moment, fix that one thing, and re-look in a month.
That is the whole method. Six columns, five rows, filled with real evidence, one fix at the end. You do not need a tool or a download to run it, and the version you build from your own data will always beat a template filled with someone else's assumptions.
If you would rather have someone find the leak for you, that is what a clarity audit does. We trace the journey the way a real visitor lives it, from first click to activation, and tell you the one gap to close first.
Get a clarity audit
A Worked Example: Where the Map Finds the Leak
Here is a compressed version of the pattern we see most often when a SaaS team maps honestly for the first time. The columns are stages, the rows show what the customer does and thinks, and the last row is what the map exposed.
Read the bottom row and notice something: none of those findings is a feature request. They are clarity failures, and each one is cheaper to fix than anything on the roadmap. That is the usual outcome of a first honest map, and it is why we run one early in most engagements at Peppermint. The map tells us where to point the design work before anyone opens a design tool.
How Is B2B Journey Mapping Different?
B2B adds people. The user, the manager who approves, sometimes procurement and security, each running their own smaller journey inside the big one. Your map has to hold more than one traveler.
The practical move is to keep one primary map for the user who champions the product, then add a thin row tracking what the decision-maker needs at each stage: a case study during evaluation, a security answer before signup, a usage report before renewal. Miss those and the champion's journey ends at a locked door someone else holds the key to. The user journey map for the individual stays the spine. The buying committee gets a lane, not a separate document.
How Often Should You Update the Map?
Revisit it when something material changes: a new pricing model, a repositioned homepage, a new onboarding flow, or a metric that moved and nobody knows why. For most SaaS teams, that lands around twice a year, plus a look whenever churn does something surprising.
A journey map that gets built once in a workshop and then laminated is a souvenir. The useful version is a living document that gets ten minutes whenever new evidence arrives, because the customer journey mapping habit matters more than the artifact. The point was never the map. The point is a team that keeps checking its story against reality, and fixes the gap instead of the symptom.
Frequently Asked Questions
What is a customer journey map?
A document, usually a table, that traces the stages a customer moves through with your product and records what they do, think, feel, and struggle with at each one. Its job is to replace the journey your team imagines with the one customers actually experience.
What are the stages of a SaaS customer journey?
Awareness, evaluation, signup, activation, adoption, and renewal. Consumer tools compress the early stages, and enterprise stretches them, but the sequence holds. For SaaS, the decisive stretch is the middle, between signup and habit, where most teams have never looked closely.
How is B2B customer journey mapping different?
More people travel the journey. A user champions the product while a manager, and sometimes procurement or security, decide alongside them. Keep one primary map for the user and add a row for what each decision-maker needs at every stage, or the journey ends at a door your champion cannot open.
Do I need a special tool to make a journey map?
No. A spreadsheet or a whiteboard does the job. Put the six stages across the top, the five rows down the side, and fill it with real evidence. Dedicated tools like Miro or Figma boards are pleasant for workshops, but the value is in the evidence you gather, not the canvas.
How often should a journey map be updated?
When something material changes: pricing, positioning, onboarding, or a metric moving without explanation. For most SaaS teams, that is roughly twice a year. A map built once and never revisited stops describing reality within a couple of quarters.
