B2B Buyer Journey Assessment

What This Assessment Does

The B2B Buyer Journey Assessment by The Starr Conspiracy scores your buying committee's readiness across four dimensions: Problem Clarity, Committee Alignment, Solution Awareness, and Vendor Readiness. It is built for B2B tech buyers, RevOps leaders, and marketing teams who need to know exactly where a deal stands. The average committee in our sample scores 47 out of 100 on first attempt, which maps to early Solution Exploration.

Most so-called buyer journey models are vendor maps drawn from the seller's side of the table. They tell sales when to send the case study. They do not tell you, the buyer, why three stakeholders just went silent or why procurement keeps rewriting the requirements doc. This tool flips the view. It diagnoses your side of the deal.

How The Assessment Scores

The scoring logic draws on four published benchmarks and one internal dataset. Gartner reports that 77% of B2B buyers describe their most recent purchase as complex or very difficult. Gartner also documents that the typical B2B buying committee now includes six to ten decision makers, each bringing four to five pieces of independently gathered information. Dreamdata's 2024 B2B benchmark puts the average enterprise sales cycle between 192 and 326 days depending on ACV. Forrester data, cited across CXL and Heinz Marketing analyses, holds that roughly 67% of the buyer journey is complete before a prospect contacts sales.

We layer those external benchmarks against an internal sample of 240 HR tech and B2B SaaS deals tracked between Q3 2023 and Q2 2025. Each question maps to one of the four scored dimensions. Answers carry weighted values from 1 to 5. Your composite score lands you in one of four named stages with a specific recommendation for what to do next.

The limitations are worth naming. This is a self-reported diagnostic. It captures the perspective of whoever takes it, not the full committee. The strongest use is to have three or four stakeholders take it independently, then compare results. Divergence between stakeholder scores is itself the most useful finding the tool produces.

The Four Stages We Score Against

Problem Identification. The committee agrees a problem exists but has not yet defined its scope, cost, or urgency. Internal language is still inconsistent. Different stakeholders describe the same pain in incompatible terms.

Solution Exploration. The problem is defined. The committee is now learning what categories of solution exist, what they cost, and what trade-offs each implies. Most education happens here, and most deals stall here.

Requirements Building. The committee converges on a solution category and begins writing the must-haves, the nice-to-haves, and the hard constraints. Procurement, security, and legal enter the conversation. Champion fatigue starts to set in.

Vendor Selection. Shortlist defined. Demos scheduled. Reference calls in flight. The decision is no longer about what to buy. It is about who to trust.

How To Read Your Result

A score of 0 to 25 puts you in Problem Identification. The work ahead is internal alignment, not partner shopping. A score of 26 to 50 places you in Solution Exploration, where the highest-leverage move is consuming category-level education rather than product demos. A score of 51 to 75 means you are Building Requirements, and the right next step is a structured discovery conversation with two or three partners. A score of 76 to 100 means you are in Vendor Selection, and the question is no longer what but who.

If two stakeholders on the same committee score in different bands, that gap is the blocker. Fix the gap before you fix the partner shortlist.

What To Do With Your Score

Use the result as a working document, not a verdict. Share it with your committee. Surface the disagreements. The 67% pre-vendor-contact statistic from Forrester is real, but it hides something important: the buyers who close successfully spend that pre-contact time building internal consensus, not just consuming content. The assessment tells you which of those two activities your team actually needs more of.

For a deeper look at how buying committees behave across the ten demand states, see our framework page. To understand the language your committee should be using, the buying committee glossary entry defines roles, dynamics, and decision authority. If you want to benchmark your cycle length and committee size against industry norms, the B2B buyer journey benchmarks page collects the full sourced dataset.

Related Questions

What are the stages of the B2B buyer journey?

There are four buyer-side stages: Problem Identification, Solution Exploration, Requirements Building, and Vendor Selection. These are not funnel stages from the seller's perspective. They describe what the buying committee is actually doing at each point, which is rarely linear and often loops back when a new stakeholder enters.

How long does the B2B buyer journey take?

Dreamdata's 2024 benchmark puts the average B2B SaaS cycle between 192 days for deals under $25K ACV and 326 days for deals over $100K ACV. Enterprise HR tech deals in our internal sample averaged 287 days from first internal conversation to signed contract.

How many people are involved in a B2B purchase decision?

Gartner data shows the typical B2B buying committee includes six to ten decision makers. In our HR tech sample, the average committee size for deals over $50K ACV was 7.4 stakeholders, with procurement, security, and a business-unit sponsor appearing in more than 80% of deals.

Why does the B2B buyer journey stall?

Deals stall most often in Solution Exploration, where new stakeholders enter and reset the conversation. The second most common stall point is the transition from Requirements Building to Vendor Selection, when procurement applies cost or compliance constraints the champion did not anticipate.

The Bottom Line

Stop letting partners draw the map of your own purchase. Take the assessment, run it across your committee, and use the divergence between scores as your real diagnostic. The deal does not move forward when you talk to more partners. It moves forward when your committee agrees on what stage it is in.