Mapping the buyer journey. From first search to signed deal.

The short answer. It's their process, not yours.

A buyer journey map is a written picture of what a real prospect thinks, asks and needs between noticing a problem and signing a contract. Done properly, it has nothing to do with your CRM stages. Most founders build a sales funnel first and assume the buyer's thinking lines up with it neatly. It rarely does. Gartner's B2B buying research is blunt about this: buyers spend only around 17% of their total purchase journey actually meeting with potential suppliers, and when comparing multiple vendors, as little as 5 to 6% of that time is spent with any single sales rep. The other 80-plus per cent happens without you in the room, which is exactly why the map matters.

For founder-led B2B businesses, this gap is the whole point of doing the work. If you only design content and outreach for the moments a prospect is talking to you, you're building for a small fraction of their actual journey. A proper map covers the research, comparison and internal debate that happens before, between and after those conversations.

That gap has widened again recently. A Gartner sales survey published in March 2026 found 67% of B2B buyers now prefer a rep-free buying experience, up from 61% in a comparable survey less than a year earlier, and Forrester reports that 89% of B2B buyers now use generative AI tools as part of their research. A prospect asking ChatGPT or Gemini to compare providers before they've spoken to anyone is now the norm rather than the exception, which means your buyer journey map needs to account for a research channel that didn't exist in most maps built even two years ago.

None of this means sales conversations matter less. It means the conversations that do happen carry more weight, because the buyer has already formed a view before they book the call. A map that only plans for what happens once someone reaches out undersells how much of the decision is already made by that point, and where in the earlier research it was actually influenced.

How it works in practice. Three stages, six buying jobs.

The simplest version of the map has three stages. Awareness is the buyer realising they have a problem worth solving, not yet looking at vendors. Consideration is active research: comparing approaches, shortlisting providers, working out what "good" looks like. Decision is choosing, negotiating and getting internal sign-off. Most marketing content still gets built for decision-stage buyers, "book a demo", "get a quote", when the majority of the audience at any given time is still in awareness or consideration and isn't ready for that ask yet.

For B2B specifically, Gartner's research goes further and breaks the journey into six buying "jobs" a purchase group has to complete, in no fixed order: identifying the problem, exploring solutions, building requirements, selecting a supplier, validating the choice and creating internal consensus. That last one, consensus creation, is where most B2B deals actually stall. Gartner's 2024 research puts a typical buying group at 6 to 10 stakeholders, and Forrester's 2025 Buyers' Journey Survey found the average deal now involves 13 internal stakeholders plus external participants, up from prior years. A map that assumes one decision-maker is mapping a journey that doesn't exist.

Mapping each stage means answering four questions for every one: what is this person trying to figure out, what would move them forward, who else is involved at this point, and what content or proof actually answers their question rather than talking about your product. Write the answers down per stage, per buyer type if you sell to more than one kind of stakeholder. An IT evaluator worried about integration risk and a finance buyer worried about total cost are in the same "consideration" stage asking completely different questions.

It helps to walk through what each of the six buying jobs actually looks like from the buyer's side, not just name them. Problem identification is the buyer convincing themselves and their colleagues that the current way of working is costing them enough to justify a change. Solution exploration is scanning the market for what kinds of fixes even exist, often without a shortlist yet. Requirements building is where a buying committee argues internally about what "must have" actually means, usually the stage where the most disagreement happens. Supplier selection narrows that list to two or three real contenders. Validation is checking the chosen supplier against risk: references, security, implementation track record. Consensus creation is getting every stakeholder who can veto the deal to actually say yes, and it's the job most sales processes have no content built for at all.

What good looks like. Specific enough to act on.

A working buyer journey map names the actual questions prospects ask, in their words, not generic labels like "research" or "evaluate". Pull these from real sources: sales call notes, support tickets, the questions that come up on discovery calls, and where relevant, what prospects are typing into ChatGPT or Google before they ever contact you. If your sales team keeps hearing the same three objections at the same stage of every deal, that's the map telling you something your content isn't currently addressing.

Win/loss interviews are the most underused source. Calling three recently won and three recently lost prospects and asking them, in their own words, what almost stopped the deal and what tipped it, surfaces detail no internal workshop will produce. Do this once a quarter rather than once, since the answers shift as your product, pricing and competitors change. If a pattern shows up twice in a row, that's a signal worth building a whole section of content around, not a one-off anecdote to note and forget.

A worked example: a founder-led CRM implementation firm was closing deals with the operations lead who first made contact, but losing them at the finance sign-off stage almost every time. Mapping the journey properly showed finance stakeholders weren't seeing anything until the proposal, by which point their questions about total cost of ownership and implementation risk had never been addressed. Adding a short cost-and-risk brief aimed specifically at that stakeholder, introduced two stages earlier than the proposal, closed that gap. The fix wasn't a better proposal. It was noticing a stakeholder the map had been missing.

The same firm found a second gap once they started tracking it properly: technical evaluators were asking about data migration risk on almost every deal, but that question only ever came up verbally on discovery calls, never in writing. Once it was added as a short section on the pricing page itself, aimed directly at that stakeholder rather than at the operations lead, evaluators stopped raising it as a late-stage objection and started referencing it as reassurance instead. Neither fix required new product capability. Both came from watching where a specific stakeholder's question went unanswered on the map.

Pitfalls to avoid. Where most maps go wrong.

The most common mistake is building the map from internal assumptions rather than real buyer behaviour. A workshop full of your own team guessing what prospects think produces a map of your product, not their journey. Pull directly from sales call recordings, lost-deal reviews and the actual questions prospects ask; if you can't source a stage from something a real buyer said or did, treat that section as a hypothesis, not a fact.

The second is mapping only the buyer who talks to sales. With deals now involving well over ten stakeholders on average, a map centred on one champion misses the finance, legal, IT and end-user perspectives that quietly decide most B2B purchases behind the scenes. Ask your sales team who else showed up in the room, on the call, or in the thread, even when that person never spoke to you directly.

The third is treating the map as a one-off exercise rather than something that gets checked against reality. Buying behaviour shifts, especially as more research moves to AI tools before a prospect ever reaches a human. If your sales cycle length, win rate or the objections your team hears start moving, that's the signal the map is out of date, not a reason to keep running the old one for another year.

A fourth, quieter pitfall is building separate maps for marketing and sales that never get reconciled. Marketing often maps the journey around content consumption while sales maps it around CRM stage, and the two rarely agree on where a given prospect actually sits. Reconcile them into one shared map with one shared vocabulary, so a "consideration stage" lead means the same thing whichever team is looking at it. Without that, handoffs between teams keep breaking in exactly the places the map was supposed to fix.