The B2B Buying Committee: How to Market to Everyone Who Signs Off

1. Blog
2. Strategy & Positioning

By Saroj Jha · October 5, 2026 · 11 min read

B2B software is bought by a group, not a person. Map who is in that group and what each person needs to believe, then give your champion what they need to bring the others along. The five steps below show how, with one example company.

Most early-stage B2B startups market to one person: the user who books a demo and loves the product. Then the deal goes quiet. Finance wants a business case, IT wants a security review, and none of them saw your marketing.

This is normal. Forrester's 2026 buyer research reports that "the typical buying decision now includes 13 internal stakeholders and nine external influencers"^[1]. Gartner found that "seventy-four percent of B2B buyer teams demonstrate unhealthy conflict during the buying decision process": members have conflicting objectives, disagree on the best course of action, or are overruled by outside decision-makers^[2]. The idea itself is old. In 1972, Webster and Wind described organizational buying "as an organizational decision-making process"^[4]. In my view, what has changed is the size of the group.

Running case: Example Co. Fictional

Example Co. is a seed-stage B2B SaaS startup whose software automates the month-end close for finance teams at companies with 50 to 500 employees. Its message is "Close the books in days, not weeks, without adding headcount." The team is eight people, including two founders and one account executive. The price is about $1,500 a month (about $18,000 a year), the typical sales cycle is about 45 days, and the goal is 30 new customers in the next 12 months. Four people shape each deal: the controller (champion and daily user), the CFO or VP Finance (economic buyer), IT and security (review), and sometimes the company's outside accountant (influencer). The problem in this post: controllers love the demo, then deals stall when the CFO and IT get involved. Example Co. and all its numbers are illustrative.

Step 1: Map the buying group by role, not job title

A job title tells you who someone is. A role tells you what they do in this decision. Five roles cover most B2B software deals:

• Champion: wants the product and does the selling inside the company.
• Economic buyer: owns the budget and gives the final yes.
• Users: work with the product every day.
• Reviewers: can say no but rarely say yes on their own, such as IT, security, legal and procurement.
• Influencers: advise from inside or outside, such as a consultant or an accountant.

These role names are common practice, not a standard. Two groups are easy to forget. Procurement: Forrester reports that "procurement professionals are decision-makers in 53% of business buying cycles"^[1]. And people outside the company: Forrester's count of nine external influencers comes from its Buyers' Journey Survey of nearly 18,000 business buyers^[5].

For each role, write the one question that person needs answered before they agree. That question is your marketing brief.

Example Co., step 1 Fictional

The founders list the four roles and the question each asks. The controller: "Will this save my team days at month-end?" The CFO: "Is it worth about $18,000 a year to us?" IT and security: "Is our financial data safe, and who can see it?" The outside accountant: "Will the audit trail make my review easier?" Until now, its marketing answered only the first. All fictional.

Do this

List every role that took part in your last five won and lost deals, and write the one question each person needed answered.

Free template

Map the buying group in one sheet

The free Sales Process Workbook has a Buying committee sheet: each role, what they must believe and who is still unreached.

Step 2: Map the journey as buying jobs, not a funnel

A funnel shows what your company sees. Buyers see a set of tasks. Gartner describes six "buying jobs": problem identification ("We need to do something."), solution exploration ("What's out there to solve our problem?"), requirements building ("What exactly do we need the purchase to do?"), supplier selection ("Does this do what we want it to do?"), validation ("We think we know the right answer, but we need to be sure.") and consensus creation ("We need to get everyone on board.")^[6].

In my view, buying often starts with an organizational change. Many changes are visible from outside, such as a new finance leader, a funding round or an acquisition. Watch for them.

Example Co., step 2 Fictional

Example Co. lists its triggers: a new CFO or controller, a new entity or acquisition, a funding round, and an audit with findings. Then it maps one asset to each buying job, from a month-end close checklist for problem identification to a one-page business case for consensus creation. All fictional; the full list is in Figure 2.

Do this

For each of the six jobs, name the asset you have today. Where you have nothing, that is your next piece of content.

Step 3: Message the group, not each person on their own

The tempting move is to send each person content about their own priorities. Gartner's research warns against it. In its survey of 632 B2B buyers in August and September 2024, "content that focuses on individual-level relevance can create conflict within the buying group, resulting in a 59% negative impact on buying group consensus", while "tailoring for buying group relevance positively impacts consensus by 20%". And "when buyers experience buying group relevance, they are three times more likely to report a high-quality deal"^[2].

In practice, that means one shared story (the problem, the cost of doing nothing, the outcome) with a section showing each role how it is affected. The CFO sees IT's concern answered, and IT sees why finance wants the product.

Example Co., step 3 Fictional

Example Co. replaces four separate one-pagers with one business case built on its message: "Close the books in days, not weeks, without adding headcount." Page one states the shared problem and the cost of a slow close. Then comes one short section per role: hours saved for the controller's team, cost and payback for the CFO, data access and security for IT, and the audit trail for the outside accountant. The controller shares it with all four. All fictional.

Do this

Rewrite your main sales document so that every role from Step 1 finds its question answered in the same document.

Step 4: Equip the champion, and be there when the group checks facts

Much of the buying happens when you are not in the room. In Gartner's survey of 645 B2B buyers in August and September 2025, buyers used "an average of seven information sources during a recent purchase", 45% used generative AI, and 67% said they prefer a buying experience without a sales rep. Yet "sixty-nine percent of B2B buyers prefer to validate AI-generated insights with sales reps"^[3]. Buyers research on their own, then want a person to confirm what they found.

So do two things. Give your champion a kit to sell for you inside the company. And make it easy for anyone in the group to check facts with a person: a named contact, a security call, a reference call.

Trials matter too. Forrester reports that "more than 60% of business buyers now make use of a trial"^[1]. A trial is where users form their view, so plan which roles take part and what each should see.

If you sell an AI product

If you sell an AI product, the group checks more facts, and different ones. In my view, three questions come up, and each belongs to a different role. Users and the champion ask: does it work on our data, not only in the demo? Reviewers in IT, security and legal ask: where does our data go, and is it used to train a model? The economic buyer asks: what will it cost as usage grows, and what happens if the AI model provider behind the product changes its prices or terms? Put an answer to each in the champion's kit.

The trial changes too. A demo runs on examples you chose; a trial runs on theirs. AAJ's judgement: before the trial starts, agree with the champion on a few test cases from their own work and on what result counts as a pass. Then the outcome is something the CFO and IT can read, not only the users.

C3 AI, a public enterprise AI software company, describes a priced version of this step in its annual report for the fiscal year ended April 30, 2026: "Our typical sales cycle begins with one or more product and technical presentations about C3 AI, leading to a mapping of our capabilities to customer use cases." Then "we typically sign a paid IPD agreement", "generally lasting up to six months. During that period, we work with the customer to deploy a production-level C3 AI Application." After a successful IPD, customers "may continue to license" the software for a consumption-based fee or a multi-period commitment. The filing also warns: "Our sales cycles can be long and unpredictable, particularly with respect to large subscriptions, and our sales efforts require considerable time and expense"^[7]. This is what the filing says, not how the company decided internally. In my view, the lesson for a seed-stage AI startup is not the six months. It is that proving the product on the customer's own use case is a planned step in the deal, and C3 AI charges for it.

Example Co., step 4 Fictional

The account executive sends the champion's kit after every first demo. It has five items: the one-page business case (CFO), a security pack (IT and security), a sample audit trail (outside accountant), a forwardable summary email, and a mutual plan for the 45-day cycle that puts the security review in week two, not week six. The CFO and IT each get an offer of a 20-minute call. All fictional.

Do this

Build your champion's kit this week and send it after every first demo.

Step 5: Win one team, then widen the group

The buying group for the first purchase is rarely the last. Two well-known filings describe starting with one team and expanding across the customer.

What Slack's and Zoom's filings show

Slack's 2019 registration statement says usage "inside organizations of all kinds is typically initially driven bottoms-up, by end users", and that enterprise decision-makers often decide to adopt Slack "after noticing substantial organic adoption by individuals and teams within the organization." It adds: "Expansion within organizations on Slack is a significant contributor to our growth." Its Net Dollar Retention Rate "was 143% as of January 31, 2019", and the sales cycle for its enterprise product, Enterprise Grid, "typically extends for multiple months"^[8].

Zoom's 2019 registration statement says it seeks "to expand within organizations by adding new hosts, having workplaces purchase additional products, or expanding the use of Zoom into other teams and departments within an organization." It reports that "55% of our 344 customers that contributed more than $100,000 of revenue started with at least one free host prior to subscribing." It also warns: "Large organizations typically undertake a significant evaluation and negotiation process due to their leverage, size, organizational structure and approval requirements, all of which can lengthen our sales cycle"^[9].

These are what the filings say, not an account of how either company made its choices internally, and the figures are from 2019. Both describe the same pattern: users first, decision-makers next, and a longer, more formal process as the buyer gets bigger.

In my view, the lesson for a seed-stage company is to plan the second buying group before the first deal closes. Note who else in the customer could use the product, and track whether the group around each deal is getting wider.

Example Co., step 5 Fictional

Example Co.'s first customers use it to close the books for one entity. The expansion path: more entities, then the financial planning team, which uses the closed numbers for reporting. Each step adds people to the buying group. Example Co. also tracks one number on every open deal: how many of the four roles are engaged. A deal with only the controller engaged by day 20 gets a call from a founder. All fictional.

Do this

Add a "roles engaged" field to every open deal in your CRM and review it every week.

What changes by stage?

• Pre-seed — In every sales call, ask: "Who else needs to agree, and what will they ask?" Your notes become your first buying-group map.
• Seed — Write the role map (Step 1), fill the six buying jobs (Step 2) and build the champion's kit (Step 4).
• Series A–B — Run account-based marketing to named accounts with content for each role, track roles engaged per deal in your CRM, and plan expansion paths by customer segment.

What mistakes should I avoid?

• Marketing only to the user. The economic buyer and the reviewers decide too.
• A different story for each person. Gartner's data suggests it can split the group.
• Leaving security to the end. Invite IT and security early.
• Reading "rep-free" as "no help wanted". Buyers research alone, then want a person to confirm.
• Counting leads instead of roles engaged. One keen champion is not a buying group.

Example Co. is a fictional company. Example Co. and all its numbers are illustrative.