What is the buyer journey?
The buyer journey is the path a buying group takes from recognizing a problem to choosing a vendor, including the research, internal discussion and vendor comparison that mostly happen before anyone talks to sales.
A sales funnel records what your team did: a form came in, a meeting got booked, an opportunity opened. The buyer journey covers what the customer did on the way there, and in B2B most of it never reaches your CRM. Someone notices a problem, a few colleagues look into it, they read reviews and ask peers, and a buying committee(opens in a new tab) argues about budget and scope before any vendor hears from them. A team that tracks only form fills and booked meetings tends to meet that group late, sometimes after a shortlist exists. The journey becomes usable once you can place each account on it with evidence a rep could point to, so marketing and sales agree on the next move.
The account's journey is the unit
A B2B purchase is a group decision, and the group is larger than most teams plan for. Forrester's 2026 buying research, drawn from its 2025 survey, puts the average purchase at 13 internal participants and 9 external ones. Each of those people arrives with a different question. The champion may be comparing vendors while the economic buyer has not yet heard the problem described, and the technical evaluator is reading integration docs on a third schedule.
The useful unit is therefore the account's journey, assembled from several people's behavior. One contact reading a pricing page and another opening an ad are two parts of the same journey, and the picture only makes sense with both in it.
The buying jobs loop
The familiar sequence of awareness, consideration and decision is a seller's summary of the path, and buyers don't follow it in order. Gartner frames buying as a set of jobs: identifying the problem, exploring solutions, building requirements, selecting a supplier, validating the choice, and building consensus inside the group. Gartner treats these as non-sequential. A group that has shortlisted vendors can return to requirements when a new stakeholder joins, and a stalled consensus job can send people back to solution exploration.
Buyer journey versus sales funnel
The funnel is the seller's view: leads, MQLs, opportunities, closed-won. Every stage is a handoff your team controls, and an account only appears once someone raises a hand. The buyer journey follows what the buyers are trying to get done, whether or not your team has seen it. An account can be deep into evaluation while the funnel shows nothing, because nobody on that committee has filled out a form yet.
Self-directed research does not remove the rep. A Gartner survey released in May 2026 found that 69% of B2B buyers turn to sales reps to validate AI-generated insights.
A stage needs evidence behind it
Stage names do little work until each one has a definition you can check against data. A team might define "considering" as three roles on the same account active inside two weeks, with at least one on a pricing or integration page. The thresholds are each team's to set. Define each stage so it can be checked against data, and give every stage assignment its reason.
Stages should also be allowed to reverse. A champion goes quiet, a budget freezes, and an account that looked ready to select drops back to evaluation. Gartner describes buying as looping, so a model that only moves forward will overstate how many accounts are close.
Account-level versus contact-level journeys
An account-level journey says a company is warming up: more visits, more ad engagement, a rise in category research. That is enough to decide which accounts deserve attention this month. It cannot say whether the activity comes from three people on the committee or one person reading everything. A contact-level view attaches each signal to a named person and a role, so you can see which committee members are active and which have not appeared at all. Contact-level specificity sits inside the account view. It does not replace it, and the account still carries fit, tier and timing.
The timing window(opens in a new tab) is where the two views pay off together, since a message is only useful while it matches what the account is working on. Vector's Journeys(opens in a new tab) view puts each account's committee and signals on one timeline, and the account journeys post(opens in a new tab) walks through how teams read it. Movement between stages is the thing to measure, and ABM KPIs(opens in a new tab) covers how.
What the journey can't show
Much of the real journey leaves no trace. Peer conversations, private communities, analyst calls and a colleague's offhand recommendation all shape the shortlist without generating a session you can see. Stages built from observable behavior describe the visible part of the path, so any stage model is partial evidence.
A stage also says nothing about fit. An account can behave exactly like one that is selecting and still be a poor match for what you sell, so check fit before spending sales time on an account because of where it sits on the journey.