What Is B2B Buying

What Is B2B Buying and How Mid-Market B2B SaaS Revenue Teams Win Complex Deals

What is B2B buying? B2B buying is the multi-stakeholder process by which organizations evaluate, select, and procure solutions, involving 6 to 10 decision-makers moving non-linearly through evaluation, consensus, and risk management. For mid-market B2B SaaS revenue teams (100 to 500 employees), The Starr Conspiracy rebuilds the B2B buying process around demand states to reduce forecast variance from 25 to 35 percent down to 10 to 15 percent within 90 days. That is clarity tied to measurable growth, not a funnel re-labeling exercise.

Composite use case. The narrative reflects engagement patterns and quantified ranges observed across mid-market B2B SaaS clients, not a single named client. Ranges vary by ACV, sales motion, and data quality.

At a glance:

• Segment: mid-market B2B SaaS, 100 to 500 employees
• Timeline: 14 to 16 week engagement, 90-day measurement window
• Primary outcomes: forecast variance cut roughly in half; stakeholder coverage per deal roughly doubled

Typical B2B buying process steps (non-linear, not a funnel):

1. Problem recognition
2. Internal alignment
3. Requirements definition
4. partner evaluation
5. Risk and security review
6. Procurement and legal
7. Decision and signature
8. Implementation planning

What actually drives a B2B purchase decision:

• Risk reduction (career risk for the economic buyer)
• Stakeholder alignment across the committee
• Proof (peer references, case data, pilots)
• Implementation confidence
• Commercial terms and procurement fit

The Problem

Most mid-market B2B SaaS revenue teams still treat B2B buying like a linear funnel. It is not. B2B buying is less a line and more a group chat with veto power, where any one of 6 to 10 stakeholders can stall a deal indefinitely. If you call it a buyer journey, fine, but run it as demand states.

What competitors miss: surface-level explainers list stages and stakeholders. They do not quantify the operational cost of getting it wrong. For a mid-market B2B SaaS company running a 9 to 12 month enterprise sales cycle, the cost shows up in four places:

Method note: all "before" figures cited below are observed across composite engagements; ranges vary by ACV, sales motion, and data quality. Measurement basis is listed in the Before/After table.

• Lose deals. 30 to 45 percent of late-stage opportunities slip a quarter or more, typically because a committee member who entered late (legal, security, finance) was never engaged earlier. Security's job is to say no. Procurement enters late to de-risk careers. Both stall deals you thought were closed.
• Waste content. 40 to 60 percent of marketing content is produced against pipeline labels nobody on the buying committee actually occupies. It is created, gated, and never opened by the people it was meant to influence.
• Miss forecasts. When CRM stages reflect rep optimism instead of buyer behavior, forecast variance exceeds 25 percent quarter over quarter. If your CRM stages are just guesses, your forecast is fiction.
• Burn RevOps time. RevOps leads spend 6 to 10 hours per week reconciling sales-reported stage data against actual buyer signals. That is a full FTE quarter every year, burned on cleanup.

Net: you lose time, accuracy, and influence.

Mini-scenario. A $180K ACV deal enters legal review in month seven. Security flags a data residency issue nobody surfaced in discovery. The deal slips two quarters. The rep insists it is "still active." The forecast says 80 percent close. It closes at 40 percent of original scope, nine months later. Phase 1 committee mapping would have surfaced security in month two. Phase 3 stage exit criteria would have blocked the deal from advancing without security signoff.

The B2B buying process does not fail because teams lack effort. It fails because the operating model assumes a buyer journey that does not exist.

The Approach

The Starr Conspiracy applies its GTM Kernel methodology, anchored to the Ten Demand States framework, to rebuild how mid-market B2B SaaS revenue teams understand and influence the B2B buying process.

Plain-English translation:

• Demand states: where a buyer is mentally (for example, "problem unaware," "partner evaluation," "risk mitigation"), not where a rep wishes they were.
• Intent signals: third-party data points (research activity, content consumption, peer review behavior) that indicate which demand state a buyer is in. If you cannot tie a signal to a demand state, it is noise.
• Buying committee: the group of internal stakeholders evaluating and approving a purchase. The committee map is your org chart for risk.
• RevOps (revenue operations): the function that owns CRM schema, routing, and pipeline definitions.

The work is operational, and it touches sales, marketing, and revenue operations in the same engagement.

Phase 1, Buying Committee Mapping (Weeks 1 to 4)

A 3-person Starr Conspiracy team (a strategist, a research lead, and an operations analyst) audits the last 24 months of closed-won and closed-lost deals.

• Purpose: Identify the real buying committee composition by deal size, vertical, and solution category. This phase drives the stakeholder coverage metric in the Before/After table.
• Inputs: CRM data, win/loss interviews, conversation intelligence transcripts.
• Outputs: A documented committee map naming the typical committee, their information needs, and the demand state in which each enters the process. A working artifact looks like a one-page diagram with roles arranged by entry point in the cycle, annotated with the questions each role asks and the proof they require.
• How it gets used: Sales multi-threads earlier. Marketing uses it as the foundation for content mapping in Phase 2.

Counterintuitive takeaway: Start with committee mapping, not personas. Personas describe people. Committee maps describe risk paths, which is why we change three CRM fields and stage-exit criteria, not just messaging.

Phase 2, Demand State Content Mapping (Weeks 5 to 10)

Marketing content is re-mapped from internal lifecycle labels to demand states. A buyer in "problem unaware" needs different content than a buyer in "partner evaluation."

• Purpose: Match assets to the demand state of each committee member. This phase drives content reuse rate and committee-member engagement rate.
• Inputs: Existing content inventory, committee map from Phase 1.
• Outputs: Gap analysis plus 8 to 12 new pieces aligned to the highest-value demand states.
• Common pitfall: Teams try to retrofit existing content to demand states without an honest gap analysis. The reuse-rate numbers in the Before/After table only move when you cut the dead assets, not just re-tag them.

Phase 3, CRM and Intent Integration (Weeks 8 to 14)

The revenue operations workstream connects intent signals to HubSpot or Salesforce. Stage definitions are rewritten around demand states. Sales playbooks are rebuilt so reps know which committee member to engage first based on the entry signal. This phase drives the forecast variance metric.

What changes in the CRM:

• Committee role field on the contact object, populated for every active deal contact
• Demand state field on the opportunity object, required at every stage transition
• Stakeholder coverage score as a calculated field tracking committee roles engaged versus required
• Intent-to-state mapping rules routing 6sense, Bombora, or G2 signals to demand state changes
• Stage exit criteria requiring named committee coverage and demand state evidence before advancement

Replace rep-optimism stage data with buyer-behavior stage data. Pipeline reviews become evidence-based, not narrative-based.

Phase 4, Enablement and Measurement (Weeks 12 to 16)

Sales gets trained on the new committee maps and demand state playbooks. Marketing instruments dashboards measuring progression between demand states and asset-to-opportunity influence rather than lead volume alone. A weekly pipeline review replaces the old monthly forecast call. Dashboards do not fix politics, but they expose it, which is the whole point of moving stage-exit criteria into the CRM.

The Outcome

Mid-market B2B SaaS revenue teams that complete the engagement see measurable shifts in pipeline quality, consensus speed, and forecast accuracy within the 90-day measurement window after rollout.

Key Stat Callout

According to the Salesforce State of Sales report (6th edition, 2024), B2B buying decisions now involve an average of 6 to 10 stakeholders, and buyers complete the majority of their evaluation before engaging a partner directly. Teams that map the typical committee and demand states early get into the conversation before the shortlist is set. (Source: salesforce.com, Salesforce State of Sales, 6th edition, 2024.)

Before and After Summary

Ranges vary by ACV, sales motion, and data quality. All "before" figures are observed across composite engagements; "after" figures are measured within 90 days of rollout.

Two quantified outcomes anchor the engagement:

1. Forecast variance reduced from 25 to 35 percent down to 10 to 15 percent within 90 days of rollout, measured as forecast-to-actual variance in the client CRM.
2. Stakeholder coverage per active deal increased from 2 to 3 contacts to 5 to 7 contacts within the 14 to 16 week engagement, measured via committee map adherence audits inside CRM.

• Forecast variance cut roughly in half within 90 days post-rollout
• Stakeholder coverage roughly doubled within the 14 to 16 week engagement
• RevOps reclaims 5 to 8 hours per week previously lost to stage cleanup

If your forecast variance is above 20 percent, this is the fastest fix that does not require more leads. Get the buying committee and demand states workshop outline. The 60-minute working session with your CMO, VP Sales, and RevOps lead delivers a preliminary committee map, two priority demand state plays, and a CRM routing recommendation tied to your existing stack.

Here is what it takes to implement this without breaking your CRM or your managers.

Implementation Details

Team size and composition. A 3-person Starr Conspiracy team (strategist, research lead, operations analyst) partners with a client-side team of:

• 1 CMO sponsor
• 1 VP of Sales
• 1 RevOps lead
• 2 to 4 marketing managers
• 2 sales managers

Phased timeline. Total engagement runs 14 to 16 weeks, followed by a 90 day measurement window. Phases overlap intentionally. Phase 3 begins in Week 8 while Phase 2 is still in flight, because CRM schema work needs the committee map but does not need to wait for content production.

Connection points. CRM (HubSpot or Salesforce), conversation intelligence (Gong or Chorus are typical), intent data (6sense, Bombora, or G2 are examples, not requirements), and the existing marketing automation platform.

Prerequisites. Three things must be in place before kickoff:

1. At least 24 months of CRM data with closed-won and closed-lost dispositions.
2. Executive sponsorship from both marketing and sales leadership. Without it, Phase 4 enablement stalls.
3. A named RevOps owner who can make schema changes inside the CRM. If RevOps cannot change the schema, do not start.

Change management. The hardest part is not the methodology. It is asking sales managers to stop running monthly forecast calls the way they have run them for a decade. The Starr Conspiracy embeds a change lead in Phases 3 and 4 to coach managers through the transition to weekly, evidence-based pipeline reviews.

Objection: sales will not adopt this. The mitigation is Phase 4 enablement starting in Week 6 (vocabulary) and a VP of Sales co-owning the playbook rewrite. Adoption fails when RevOps owns the rollout alone.

Objection: we already have personas. Personas describe individual buyers. Committee maps describe how the typical committee interacts, gates each other, and surfaces risk. Keep your personas. Add the committee map.

Lesson learned. In early engagements, demand state training for sales happened in Week 12. That was too late. Reps had been working deals for three months under old assumptions and resisted re-mapping live opportunities. The current approach introduces demand state vocabulary in Week 6, so reps are fluent before the CRM cutover.

Common failure mode. Skipping the win/loss interviews in Phase 1 because "we already know our buyers." What we look for in the data: late-stage stakeholder additions, recurring objection clusters, deals that slipped between stages without a documented reason. Teams that skip this step produce committee maps that match rep folklore rather than buyer reality, and the rest of the engagement compounds that error.

Related Use Cases

• B2B Demand Generation for Mid-Market SaaS. Same segment, different job-to-be-done. Focuses on top-of-pipeline creation using demand states to prioritize channel investment and creative, rather than on committee-stage execution.
• Buying Committee Mapping for Enterprise HR Tech. Same job-to-be-done, different segment. Adapts the committee mapping methodology for longer cycles (18 to 24 months) and larger committees (12 to 18 stakeholders) common in enterprise HR technology purchases.
• CRM and Intent Data Integration for RevOps Teams. Same segment, narrower job. Isolates the Phase 3 work for teams that already have a committee map but need help operationalizing intent signals and rewriting pipeline labels.
• Sales and Marketing Alignment for B2B SaaS. Adjacent job-to-be-done. Addresses the organizational and incentive design work that often surfaces during a buying committee engagement but extends beyond its scope.

If you are deciding whether this fits your situation, start here.

Frequently Asked Questions

How long does B2B buying take for mid-market SaaS?

Enterprise B2B buying cycles for mid-market B2B SaaS run 9 to 12 months from first touch to closed-won. Committee formation often starts before the partner is aware of the opportunity, with buyers completing most of their evaluation independently before engaging sales (Salesforce State of Sales, 6th edition, 2024).

How many people are involved in a B2B buying decision?

The typical mid-market B2B SaaS buying committee includes 6 to 10 stakeholders spanning the economic buyer, technical evaluator, end users, procurement, legal, and security. Enterprise deals can push this to 12 to 18.

What is a B2B buying committee?

A B2B buying committee is the group of internal stakeholders involved in evaluating, approving, and signing off on a purchase. It is rarely formally chartered, which is why mapping it is the first step in any serious B2B buying engagement with The Starr Conspiracy.

How is B2B buying different from B2C?

B2B buying is multi-stakeholder, consensus-driven, risk-averse, and non-linear. B2C is largely individual, emotion-influenced, and shorter cycle. The committee dynamic is the single biggest difference and the reason B2B revenue teams need committee maps, not personas.

Do we need intent data tools to do this?

No. Intent tools (6sense, Bombora, G2) sharpen the signal but are not prerequisites. The committee map and demand state framework work without them. Most clients add intent data in Phase 3 if not already in place.

What if our CRM data is messy?

Then Phase 1 takes the full four weeks instead of three. The Starr Conspiracy will tell you directly during scoping if data quality requires a pre-engagement cleanup sprint. Bad data is a delay, not a disqualifier.

What results should we expect, and when?

Within the 14 to 16 week engagement, expect stakeholder coverage per deal to roughly double, measured as committee roles engaged per active opportunity. Within 90 days post-rollout, expect forecast variance to fall by roughly half, measured as forecast-to-actual variance. These are typical ranges from composite engagements, not guarantees.

What are the prerequisites to working with The Starr Conspiracy on this?

You need 24 months of CRM data, executive sponsorship across sales and marketing, and a named RevOps owner empowered to make schema changes. If any of those three are missing, The Starr Conspiracy will tell you directly before signing. The engagement will not deliver without them.

If you want this live before next quarter's pipeline review cadence is set, kickoff needs to happen 14 to 16 weeks before that date. Talk to The Starr Conspiracy about a buying committee and demand states engagement.

The Outcome

Across mid-market B2B SaaS partnerships using the GTM Kernel approach, The Starr Conspiracy has consistently delivered:

Sales cycle compression from 9 months to 6 months on average, a 33% reduction, measured 6 months after enablement rollout. The driver: earlier identification of the full buying committee and proactive engagement of procurement and security 60 days sooner than before.

Win rate lift from 18% to 27%, a 50% relative improvement, measured across 90 days of new opportunities post-implementation. The driver: matching content and outreach to demand states rather than guessing where a buyer sits in a linear funnel.

Wasted rep capacity reduced by 6 hours per week, recovering roughly $23,400 in productive selling time per rep per year at a 12-person team scale.

According to Gartner, B2B buyers now spend only 17% of their total purchase time meeting with potential suppliers, and when comparing multiple suppliers, that figure drops to 5 or 6%. Teams that map the buying committee and serve the right content to the right demand state capture a disproportionate share of that narrow window.