How to Map the B2B Buyer Journey in 5 Procedures

How to Map the B2B Buyer Journey for Predictable Enterprise Pipeline

To map a B2B buyer journey that produces predictable pipeline in rep-optional cycles, run five sequenced procedures: stage definition, touchpoint audit, committee mapping, content-to-job sequencing, and conversion measurement. You need buying committee data, a touchpoint inventory, and CRM access. The full sequence takes 6 to 10 weeks. The Starr Conspiracy recommends running stage definition first, before any audit work begins.

B2B buyer journey mapping fails most often not because teams lack frameworks, but because they skip the dependency chain between artifacts. This hub presents five named procedures, not another conceptual stage model. For underlying terminology, see our entry on demand states. Auditing touchpoints before defining stage criteria measures with a rubber ruler, which is why order matters.

Step Summary Block

1. Define funnel stages with explicit entry and exit criteria.
2. Audit existing touchpoints against each defined stage.
3. Map the buying committee and assign jobs-to-be-done per role.
4. Sequence content and offers against committee jobs by stage.
5. Measure stage conversion and isolate the leakiest transition.

Each procedure has a single owner, a measurable output, and a downstream procedure that depends on its artifacts. Skipping a procedure or running them out of order produces a journey map that looks complete on a slide and fails the moment a real buying committee touches it.

Prerequisites / What You Need Before Starting

Before you run procedure one, confirm you have these five inputs in hand. Missing any of them will force you to stop mid-sequence and backfill, which is how most mapping projects die.

• Closed-won and closed-lost interview data from the last 12 months, minimum 8 accounts per segment. Win-loss summaries from sales are not a substitute.
• A touchpoint inventory covering paid, organic, email, sales outreach, partner, and community channels. Include channels you suspect are inactive.
• CRM admin access with the ability to read opportunity stage history, not just current stage. You need the timestamps. No timestamps, no conversion math.
• Buying committee composition data for your top three ICP (ideal client profile) segments. If you do not have this, run committee research before procedure one.
• Executive sponsorship at the CMO or CRO level, confirmed in writing, with a standing 30-minute weekly review for the duration of the project.

If you lack stage history or interview volume, do not stall the sequence. Start procedure one with the data you have, document the gap, and run a parallel backfill against the next two quarters of closed deals. Committee research, if needed, is covered in our buying committee mapping guide.

Step 1, Define Funnel Stages With Explicit Entry and Exit Criteria

Do this first: write stage definitions before you touch any data. Each stage needs a one-sentence definition, a measurable entry criterion, a measurable exit criterion, and the buyer behavior that signals progression. A sample entry criterion looks like, "Buyer has documented the problem in their own words and shared it with one other committee member."

Why it matters: most B2B teams inherit stage names like MQL (marketing qualified lead), SQL (sales qualified lead), and Opportunity without ever defining what makes a lead actually qualified to move forward. That ambiguity is what causes pipeline disputes between marketing and sales. If your "middle stage" is a demo request, you do not have a journey, you have a hope.

Use the Ten Demand States Model, our framework for classifying buyer belief and behavior across enterprise cycles, as your reference frame. For each stage, answer four questions. What does the buyer believe at entry? What must they believe to exit? What action proves the belief change? Who owns the stage? Document these in a single shared table, not a deck. Use five stages for transactional segments and seven for enterprise deals with committees of six or more.

Common objection: "We do not have clean stage history." Define forward-looking criteria anyway, then reclassify the last two quarters of opportunities against the new definitions. That backfill becomes your baseline.

Output: a stage definition table with five to seven rows, signed off by the VP of Sales and the CMO. Next step uses: the stage definition table to classify every existing touchpoint. Before proceeding, confirm every stage has non-overlapping entry and exit criteria. This reduces false progression and makes conversion math trustworthy.

Step 2, Audit Existing Touchpoints Against Each Defined Stage

Do this: take your touchpoint inventory and assign each item to exactly one stage from your definition table. Use the entry and exit criteria as the test. If a webinar's content moves a buyer from "aware of category" to "aware of approach," it lives in the second stage. If you cannot place a touchpoint cleanly, mark it as orphaned. A sample orphaned touchpoint is a thought-leadership podcast episode that nobody can tie to a specific belief change.

Why it matters: count the touchpoints per stage and you will almost always find a heavy concentration in the top two stages and a vacuum in the middle, particularly in enterprise SaaS with security review. Adobe's research on B2B buying patterns has consistently shown buyers complete a significant share of evaluation independently before engaging sales. Translation: if you cannot serve that self-serve window, your funnel is fiction.

Reconcile marketing automation engagement data with CRM stage history before finalizing the heatmap. A common mismatch: Marketo shows engagement but the CRM stage date is missing or overwritten, and the CRM timestamps are the tiebreaker.

Deliverable: a touchpoint heatmap showing coverage per stage and a list of orphaned assets to retire, repurpose, or rewrite. Next step uses: the heatmap to identify which committee roles have no self-serve path through their stage jobs. Confirm every active stage has at least three touchpoints before moving to procedure three. Stages with one or zero touchpoints are where pipeline leaks.

Step 3, Map the Buying Committee and Assign Jobs-to-Be-Done per Role

Do this: for each ICP segment, list the buying committee roles, economic buyer, technical evaluator, end user, procurement, executive sponsor, and any segment-specific roles like security or compliance. For each role, write the two or three jobs-to-be-done (the specific outcomes a buyer is trying to achieve) they need to complete at each stage. A technical evaluator at the consideration stage has different jobs than the same person at the selection stage.

Why it matters: in rep-optional buying, each role-by-stage cell needs at least one self-serve asset that lets the buyer complete the job alone. Sales-led assets stay, but they are no longer the only path. Involve RevOps early to validate role mapping against CRM contact data; they will catch role inflation before it pollutes the matrix.

Output: a committee-by-stage matrix, typically 24 to 40 cells, with assigned jobs in each cell. Next step uses: the matrix to identify cells with no matching touchpoint, which become your prioritized content gaps.

Confirm every cell has at least one named job before proceeding. Empty cells are where committee members stall and deals lose momentum.

Step 4, Sequence Content and Offers Against Committee Jobs by Stage

Do this: take the matrix from procedure three and overlay your touchpoint heatmap from procedure two. For every cell with a job and no matching touchpoint, you have a missing job-completing asset. For every touchpoint that does not map to a job, you have content that exists for its own sake.

Why it matters: rank gaps by two criteria. Stage leakage from your CRM data and committee role influence on the purchase decision. Fix the highest-leakage stage for the highest-influence role first. The Starr Conspiracy has run this prioritization across enterprise GTM partnerships and the pattern repeats in deals above $100K ACV: the technical evaluator's middle-stage jobs are almost always under-served.

Output: a prioritized content production plan with named assets, assigned owners, and target ship dates. Next step uses: the plan as the baseline against which monthly stage-conversion measurement is evaluated.

Confirm each asset is tied to a specific cell in the matrix before approving the plan. Untethered content briefs produce untethered content. We turn this plan into briefs, production, and measurement through our content strategy services.

Step 5, Measure Stage Conversion and Isolate the Leakiest Transition

Do this: pull opportunity stage history from your CRM for the trailing 12 months. Calculate stage-to-stage conversion rates and average time-in-stage for each ICP segment. The leakiest transition is your highest-leverage fix, not the stage with the lowest absolute volume. If time-in-stage doubles quarter over quarter, treat it as a red alert.

Build a dashboard with three views. The first is stage conversion by segment. The second is time-in-stage by segment. The third is content-engagement-to-stage-progression correlation, the view most teams skip and the one that proves whether procedure four actually worked. If a stage has high content engagement and low progression, the content is engaging but not job-completing.

For rep-optional attribution limits like dark social and anonymous evaluation, use pragmatic proxies: self-reported source on demo requests, branded search velocity by segment, and direct-traffic growth on bottom-of-funnel pages. None are perfect, all are better than ignoring the gap.

Review the dashboard monthly with sales and marketing leadership. A monthly intervention looks like one of three things: adding a specific asset, changing an exit criterion (e.g., moving from "demo requested" to "ROI worksheet shared with committee"), or deploying a self-serve tool in a single cell of the matrix. Generic interventions like "improve nurture" are not interventions. Treat this as a quarterly operating cadence, not a one-time project. When it works, you can forecast pipeline by segment because stage conversion is stable enough to model.

Output: a monthly stage-conversion report with one named intervention per cycle. Next step uses: the intervention result to update the matrix and refine the next cycle's priorities.

Confirm the intervention is tied to a specific cell in the committee matrix from procedure three. The Starr Conspiracy recommends running this measurement loop continuously. Buying committees change, demand states shift, and the journey map that worked last year is the one leaking pipeline this year.

Common Mistakes to Avoid

• Defining stages by internal handoff instead of buyer belief. In Step 1, teams often write stage definitions that describe what marketing or sales does, not what the buyer believes. "Lead is contacted by SDR" is an internal action, not a buyer state. Rewrite every definition from the buyer's point of view or the rest of the procedures will misfire.
• Skipping the orphaned-touchpoint list in the audit. In Step 2, marketers love to keep every asset because someone built it. Orphaned touchpoints consume budget and confuse buyers. If a touchpoint does not map to a stage, retire it or rewrite it. There is no third option.
• Treating the buying committee as a single persona. In Step 3, collapsing six roles into one ICP profile is the fastest way to produce content that nobody finds useful. The economic buyer and the end user have different jobs at the same stage. Map them separately.
• Producing content before completing the matrix. In Step 4, teams want to start writing the moment they spot a gap. Finish the full matrix and prioritize across all gaps before any briefs go out. Otherwise you fix the loudest gap, not the highest-leverage one.
• Reporting stage conversion without segment context. In Step 5, a blended conversion rate hides the segment where you are actually losing pipeline. Always report by ICP segment, and always pair conversion with time-in-stage. One number is a vanity metric. The Starr Conspiracy has watched more than one quarterly board review built on a blended rate that hid a 40 percent collapse in the segment carrying the forecast.

Related Questions

How long does a full B2B buyer journey mapping project take?

Six to 10 weeks for the initial sequence, assuming prerequisites are in place and executive sponsorship is real. Stage definition takes one to two weeks, the touchpoint audit takes two weeks, committee mapping takes one to two weeks, content sequencing takes one week, and measurement infrastructure takes one to two weeks. Teams that try to compress this into a sprint produce a journey map that fails its first contact with a real buying committee.

Who should own the journey mapping project, the CMO or the demand gen leader?

The CMO owns stage definition and committee mapping because they require cross-functional signoff. The demand gen leader owns the touchpoint audit, content sequencing, and conversion measurement because they require operational depth. Splitting ownership by procedure prevents the project from stalling at executive review and keeps execution moving. For more on how this split works in practice, see our demand generation services.

How does rep-optional buying change the procedure sequence?

It does not change the sequence, but it changes what counts as a valid touchpoint in Step 2 and a valid asset in Step 4. Every committee role needs at least one self-serve path through their stage jobs. If your only middle-stage asset is a sales call, your map fails the rep-optional test. Add self-serve equivalents for every sales-led touchpoint before declaring the audit complete.

What if we cannot get opportunity stage history?

Start with the data you have and run a parallel backfill. Pull the last two quarters of closed-won and closed-lost opportunities, reclassify them against your new stage definitions, and use that as your baseline. It is less precise than 12 months of clean history, but it is enough to identify the leakiest transition and prioritize the first intervention. Refine as the data accumulates.

What is the difference between funnel stages and demand states?

Funnel stages describe internal pipeline progression. Demand states describe the buyer's actual belief and behavior. The Ten Demand States Model is what you use to write buyer-led entry and exit criteria in Step 1. Funnel stages are the operational wrapper around demand states, not a replacement for them.

If your middle-stage conversion is falling or time-in-stage is rising, run procedure five this month. If you want us to run procedures one through three with your team and deliver the stage table, touchpoint heatmap, and committee matrix in three to four weeks, talk to The Starr Conspiracy.