B2B Buying Process Steps Compared

The 7 B2B Buying Process Steps and How Each One Differs by Deal Size and Org Type Verdict up front. If you're running a sub-$25K SaaS deal, Self-Serve SaaS wins on speed and unit economics. If you're chasing a $250K+ enterprise contract with a buying committee of 9+ stakeholders, Traditional RFP procurement still wins on risk control and consensus. For everything in between, the Hybrid Model is the only realistic answer, and it's where most B2B revenue actually lives right now. Decisive factor: risk tolerance and consensus load. The more political cover a buyer needs, the more the process bends toward RFP. The less risk, the more it bends toward self-serve. Every other source treats the B2B buying process as a linear, seven-step checklist that applies equally to a $5K Slack subscription and a $5M ERP rollout (see the typical linear treatments on marketveep.com, openstax.org, and oroinc.com). It doesn't work that way. The seven steps are stable. What changes is who's involved, how long each stage takes, where deals stall, and which steps compress, expand, or quietly get skipped. Take a regulated financial services buyer replacing a core platform versus a product manager expensing a $40 tool. Same seven steps. Completely different deal. What this is: a diagnostic for mapping your own buying reality across Traditional RFP procurement, Self-Serve SaaS, and the Hybrid Model. What this is not: a checklist, a funnel, or a generic explainer. If you're in the buying demand state, this is the map. How to use this page - Start with the two comparison tables to locate your deal. - Read the step sections that match your model. - Use the "Where deals stall" callouts to pressure-test your current pipeline. - Use the buying committee notes to assign ownership before kickoff. After reading, you should be able to: forecast realistic cycle time, identify where your deals are most likely to stall, and assign clear ownership at each step. Table 1. The Seven B2B Buying Process Steps by Buying Model Typical ranges. Use as a diagnostic, not a guarantee. One-line example per model: - Traditional RFP: a regulated enterprise replacing a core platform across 12 business units. - Self-Serve SaaS: a product manager expensing a $40/seat tool to fix a workflow this week. - Hybrid: a 600-person SaaS company buying analytics with the data team driving and procurement gating the final paper.   Map your buying model with The Starr Conspiracy. We help B2B tech teams build marketing systems that match how buyers actually buy. Stop losing weeks to the wrong process. Talk to us about a buying-model map,   Table 2. The Same Seven Steps by Deal Size Typical ranges. The bigger the deal, the more steps 5 and 6 expand. Definition: buying committee. The cross-functional group that signs off on a B2B purchase. Roles typically include economic buyer, technical evaluator, end user, procurement, legal, and security. Size scales with deal risk, not deal size alone. 1. Need Recognition Picture a VP of HR walking out of a board meeting with a mandate to fix retention. That's the trigger. Need recognition is the moment an organization decides a problem is worth solving with outside help. It sets the urgency, the budget envelope, and the political weight of the deal. Get this stage wrong and every downstream step is mis-scoped. What it's for: establish the trigger and the stakes. Primary driver: the person whose KPI is on the line. Where deals stall - The trigger event is real, but no one owns the budget. - "Strategic priority" is declared, but no executive sponsor signs. - The pain is felt by one team, but the solution requires four. Buying committee role at this stage - RFP: an executive sponsor and a strategy or PMO function frame the need. - Self-Serve: a single user is both originator and approver. - Hybrid: a team lead surfaces the need, ops validates the business case. What changes by model. RFP needs are top-down and strategic. Self-serve needs are bottom-up and personal. Hybrid sits in the middle, which is exactly why it stalls when ops can't validate the team lead's case. 2. Requirements Definition Direct answer. Requirements definition is where the buyer translates pain into specifications. It looks like rigor. It's often politics. Whoever writes the requirements controls the shortlist, and in our client work, most buyers don't realize that until it's too late. Purpose: scope what "good" looks like before talking to vendors. Owner: the function that will operate the solution day-to-day. Where deals stall - Requirements get written around a preferred vendor (we've seen entire RFPs lifted from one vendor's website). - Stakeholders bolt on must-haves with no prioritization. - Security and legal aren't consulted, then torpedo the spec at step 6. Buying committee role at this stage - RFP: formal requirements doc reviewed by 6+ stakeholders. - Self-Serve: a feature checklist in someone's notes app. - Hybrid: an internal brief circulated for async input. What changes by model. Traditional RFP procurement turns this into a 4 to 8 week exercise. Self-Serve SaaS compresses it to hours. The Hybrid Model lands at 1 to 2 weeks, and that's where most enterprise tech buying now lives. 3. Partner Research Here's the practical breakdown. Partner research is how buyers build their consideration set. It's the stage AI engines have changed the most, because buyers now arrive at vendor sites already half-decided. If you're not in the consideration set before this stage, you're rarely added during it. What it's for: identify credible options. Primary driver: the evaluator or champion. Where deals stall - The shortlist is built from outdated analyst reports. - Peer recommendations dominate, and you weren't named. - Internal stakeholders push pet vendors with no qualification. Buying committee role at this stage - RFP: analyst relations, procurement, and the evaluator co-build the long list. - Self-Serve: the user searches, reads, and decides alone. - Hybrid: champion gathers inputs, then socializes the long list with the committee. What changes by model. RFP buyers send formal RFIs to 5 to 10 partners. Self-serve buyers Google, ask peers, and skim G2. Hybrid buyers mix analyst inputs with peer DMs and short demos. 4. Evaluation and Shortlist Direct answer. Evaluation narrows the field to the two or three options that will actually compete. This is where vendor differentiation either holds up or collapses. In most enterprise deals we see, vendors lose here not on capability, but on the buyer's inability to defend the choice internally. Purpose: select finalists. Owner: the technical evaluator plus the economic buyer. Where deals stall - The scoring matrix is built after demos, to justify a pre-made choice. - The POC has no success criteria. - References don't match the buyer's use case (think a healthcare buyer handed three retail references). Buying committee role at this stage - RFP: scored matrix, formal references, security questionnaires (SOC 2, data residency, pen test results). - Self-Serve: free trial telemetry is the evaluation. - Hybrid: 2 to 3 finalists run a paid pilot with defined success metrics. What changes by model. RFP buyers want auditability. Self-serve buyers want proof in the product. Hybrid buyers want a pilot that gives them political cover. 5. Buying Committee Consensus Direct answer. Consensus is where one stakeholder's preference becomes the organization's decision. It is the stage that breaks more enterprise deals than any other, because consensus is not the same as agreement. It's the absence of a credible block, the moment a security lead stops saying "I have concerns." Purpose: convert preference into a defensible group decision. Owner: the champion, with the economic buyer as backstop. Where deals stall - A late-arriving stakeholder reopens settled questions. - Security or legal raises a deal-breaker no one flagged earlier (data residency is the classic one). - The champion leaves or changes role. Buying committee role at this stage - RFP: 9 to 14 stakeholders, formal sign-off, documented dissent. - Self-Serve: 1 to 3 people, often just the end user. - Hybrid: 5 to 7 stakeholders aligning async, usually in Slack or a shared doc. What changes by model. I've watched this blow up deals at $250K+ more times than I can count. The pattern is always the same: speed, safety, and political cover, in some mix. Name the mix early or lose weeks to the wrong conversation. 6. Negotiation and Purchase Direct answer. Negotiation and purchase is where commercial, legal, and security gates close the deal or kill it. By this stage, the buying decision is largely made. What's being negotiated is risk transfer, not value, things like liability caps, indemnification language, and uptime SLAs. Purpose: transfer risk, finalize commercials. Owner: procurement, with legal and security in support. Where deals stall - MSA redlines that should have been raised at step 2. - Security review uncovers a SOC 2 or data residency gap. - Budget approval slips a quarter. Buying committee role at this stage - RFP: procurement-led, 6 to 12 weeks typical, often longer in financial services or healthcare. - Self-Serve: self-checkout or a low-touch closer. - Hybrid: AE-led, with a procurement gate that activates at roughly $50K+. What changes by model. Enterprise procurement lead times of 6 to 12 weeks are normal, not a failure. If your forecast assumes 3 weeks, your forecast is wrong. 7. Post-Purchase Review Direct answer. Post-purchase review determines whether the buyer renews, expands, or churns. It is the most underweighted stage in B2B and the one that most directly drives net revenue retention. Treat it as the start of the next buying cycle, because that's what it is. Purpose: prove value and set up expansion. Owner: customer success plus the economic buyer. Where deals stall - No success metrics were defined before purchase. - The champion who bought the product leaves. - Usage stalls, and no one runs an intervention. Buying committee role at this stage - RFP: annual business review, formal KPIs, executive readout. - Self-Serve: usage telemetry and churn risk scoring. - Hybrid: quarterly business review plus product telemetry. What changes by model. RFP buyers want governance. Self-serve buyers want product value. Hybrid buyers want both, and they will benchmark you against each. Bottom line The seven steps are stable. The execution is not. Speed, safety, and political cover are the three drivers that bend each step, and the buying model you're in determines which one dominates. If you think you don't have a process, you do. It's just implicit. Make it explicit and you'll stop misdiagnosing where your deals actually stall. At The Starr Conspiracy, we don't sell AI experiments. We build marketing systems that actually work, and this is how we think about buying reality. After 25 years in B2B tech GTM, the pattern is consistent: buying-model clarity is what makes messaging, content, and GTM execution land. Frequently Asked Questions How many steps are in the B2B buying process? Seven is the canonical count: need recognition, requirements definition, partner research, evaluation and shortlist, buying committee consensus, negotiation and purchase, and post-purchase review. The number is stable across models. What changes is how long each step takes and who's involved. Who is involved in B2B purchasing decisions? It depends on deal size and risk. A sub-$25K self-serve purchase often involves 1 to 3 people. A mid-market deal pulls in 5 to 7 stakeholders. An enterprise purchase typically includes 9 to 14 stakeholders across the economic buyer, technical evaluator, end user, procurement, legal, security, and executive sponsor. How long does the B2B buying process take? Self-Serve SaaS can close in days. Hybrid Model deals commonly run 6 to 12 weeks. Traditional RFP procurement at enterprise scale often runs 4 to 9 months, with negotiation and security review alone taking 6 to 12 weeks. What is the difference between the B2B buyer journey and the B2B buying process? The B2B buying process is the set of steps an organization takes to make a purchase. The broader concept of a buyer journey is often used to describe individual awareness and consideration patterns. At The Starr Conspiracy, we use demand states instead, because they describe what buyers are actually doing, not where they sit in a marketer's funnel. What is a buying committee and when does one form? A buying committee is the cross-functional group that signs off on a B2B purchase. It typically forms when deal value crosses a procurement threshold (often around $50K) or when risk, compliance, or cross-team dependencies trigger formal review. Below that threshold, a single user or small team usually decides. Why do B2B deals stall most often? Deals stall when the process is mismatched to the deal reality. The most common failure modes are unclear ownership at need recognition, requirements written around a preferred vendor, late-arriving stakeholders at consensus, and security or legal gates raised too late in negotiation. Is the B2B procurement process the same as the B2B sales cycle? No. The procurement process is the buyer's internal workflow. The sales cycle is the seller's view of the same deal. They overlap but rarely align on timing, which is why most forecast slippage happens at steps 5 and 6.   Stop losing weeks to the wrong process. Get a buying-model map you can use to align stakeholders, timeline, and vendor evaluation. We help B2B tech teams build marketing systems that match how buyers actually buy. Work with The Starr Conspiracy,