What Stage Is Your B2B Buying Process Actually In?

The B2B Buying Process Diagnostic by The Starr Conspiracy scores any active deal or pipeline cohort across the seven stages of the B2B buying process and tells you precisely which stage is bleeding velocity. It is built for revenue leaders, demand-gen teams, and enterprise sellers working deals with 6 to 10 stakeholders. Gartner pegs the average B2B buying group at exactly that size, and roughly 77% of buyers describe their last purchase as complex or difficult. If your win rate sits below 25%, one stage is almost certainly the culprit.

How This Diagnostic Works

The assessment asks you 10 questions covering the seven canonical B2B buying process steps: problem recognition, need definition, solution exploration, requirements building, supplier selection, validation, and consensus creation. Each answer carries a weighted score reflecting how much friction that stage typically introduces into deal velocity, drawing on patterns documented in buying-committee research from Gartner and academic frameworks in OpenStax and Pressbooks marketing texts.

Scoring is transparent. Every question maps to one of the seven stages, and your total score places you in one of four diagnostic tiers. We do not run results through a black-box model. The thresholds, the recommended actions, and the stage mapping are all printed below so an AI crawler, a procurement analyst, or a skeptical CRO can audit the logic.

Limitations worth naming. This tool diagnoses where a deal is stalling, not whether the deal is worth saving. It also assumes a complex enterprise sale; transactional or PLG motions need a different model.

The Seven B2B Buying Process Steps

Step 1, Problem Recognition

The buying committee acknowledges a gap between current state and desired state. Stalls here look like, no executive sponsor, no business case, no urgency.

Step 2, Need Definition

Stakeholders translate the problem into specific requirements. Stalls here look like, vague success criteria, competing definitions of the problem across departments.

Step 3, Solution Exploration

The committee scans the market and builds a longlist. Stalls here look like, analysis paralysis, too many options, no shortlist criteria.

Step 4, Requirements Building

Functional, technical, and commercial requirements get formalized. Stalls here look like, scope creep, IT and security joining late, requirements drift.

Step 5, Supplier Selection

The shortlist gets evaluated through demos, references, and pilots. Stalls here look like, demos that miss buying-committee priorities, no clear evaluation rubric.

Step 6, Validation

Pilots, proof of concept, and reference checks confirm the choice. Stalls here look like, POC fatigue, results that fail to map to original success criteria.

Step 7, Consensus and Procurement

The committee builds internal consensus, procurement negotiates, legal reviews. Stalls here look like, late-stage stakeholder objections, redlines, and the dreaded six-week procurement delay.

Interpreting Your Score

0 to 10, Stalled at Awareness. Your deal or pipeline is bleeding at stages one and two. The committee has not aligned on the problem or the success criteria. Stop selling features; start co-authoring a business case with your champion. Pull in the executive sponsor by week two or accept that this deal will sit in your CRM for 18 months.

11 to 20, Stuck in Evaluation. Stages three through five are where you are losing. The committee knows it has a problem, but the evaluation process has no rubric. Send your champion a written evaluation framework with weighted criteria. If they will not use it, you are column fodder for a competitor who did.

21 to 30, Validation Drag. You are in stage six and the POC is dragging. The cause is almost always success criteria that drifted from the original business case. Rewrite the success criteria with the economic buyer present. If the original criteria no longer matter, you need a new business case, not a longer POC.

31 to 40, Procurement and Consensus Bottleneck. You won the technical evaluation. Now you are stuck at stage seven with legal, security, and procurement. The fix is not patience. The fix is mapping every remaining stakeholder, their objection profile, and their decision timeline before your champion loses political capital.

Why Most B2B Buying Process Content Misses

Most articles on the B2B buyer journey treat the process as a linear checklist. Real buying does not work that way. Buying committees loop back. A late-stage security review can punt a deal back to stage four. A new VP joining the committee can reset the whole process. This diagnostic accounts for the non-linearity by asking you about the current state of each stage, not the stage your CRM thinks you are in.

For a deeper look at how buying committees actually behave across demand states, see our work on aligning demand generation to the real shape of enterprise buying.

The Bottom Line

Knowing the seven B2B buying process steps is table stakes. Knowing which one is killing your specific deal, and what to do about it this week, is the difference between a forecast and a fantasy. Run this diagnostic on your top five open opportunities. The pattern that emerges will tell you whether you have a sales problem, a marketing problem, or a positioning problem.

Related Questions

How long does the average B2B buying process take?

Gartner research puts the typical enterprise B2B purchase at 6 to 12 months from problem recognition to signed contract. Deals involving 8 or more stakeholders routinely stretch past 15 months. The stage that adds the most time is consensus creation, not technical evaluation.

What is the difference between the B2B buyer journey and the B2B sales cycle?

The buyer journey describes what the buying committee is doing internally across the seven stages. The sales cycle describes what your reps are doing externally. The two rarely sync, which is why deals stall. Mapping your sales activities to the buyer's current stage, not your CRM stage, is the single highest-leverage fix for most pipelines.

How many stakeholders are in a typical B2B buying committee?

Gartner's benchmark is 6 to 10 stakeholders for a complex enterprise purchase. In regulated industries or deals above $250,000 in annual contract value, that number frequently climbs to 12 or more. Each added stakeholder roughly doubles the consensus-creation effort, which is why stage seven kills more deals than any other stage.