# How to Market to a B2B SaaS Buying Committee

> Map the six to eleven people in a software deal, then build the assets each one needs: champion kits, business cases, security answers, procurement help.

Source: https://saas-marketing.net/guides/b2b-saas-buying-committee/
Topic: B2B SaaS Marketing
Type: guide
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/b2b-saas-buying-committee/

## Short answer

A B2B SaaS buying committee is the group of six to eleven people who must agree before software gets bought: a champion, an economic buyer, end users, IT and security, procurement, finance and legal. Each one asks a different question, so each one needs a different asset. Marketing's job is not to reach all of them directly. It is to arm the champion with forwardable material that answers the other six questions when you are not in the room.

## Key takeaways

- Gartner puts the typical complex B2B buying group at six to ten people, and legal plus procurement pushes enterprise deals to eleven.
- 6sense found 81 percent of buyers pick a preferred vendor before contacting sales, and that vendor wins about 84 percent of the time.
- Build one forwardable asset per committee question rather than one nurture track per persona, because the champion does the forwarding.
- A published trust centre answers the security reviewer before the questionnaire arrives and removes two to four weeks of stalled time.
- Procurement stalls are rarely about price, they are about missing paperwork: W-9, insurance certificates, DPA, SOC 2 and a signed MSA.
- The measurable proof is contacts per closed opportunity, which should climb from two to five or six once the kit is live.

---

One person signs a 60,000 dollar software contract. Seven people can stop it. The champion who filled in your demo form has to run an internal review you will mostly not attend, using material you either gave them or did not, and most B2B SaaS teams produce content for the champion and nothing at all for the six people the champion has to convince.

Gartner's work on complex B2B purchases puts the typical buying group at six to ten people. Add legal and procurement on a six-figure deal and eleven is normal. The count matters less than the structure. Each role asks exactly one question, and when nobody answers it the deal does not die loudly. It goes quiet in week nine and shows up in your pipeline review as "checking in with Dave".

## Who actually shows up on a 60,000 dollar deal

Seven functions, and they arrive in a predictable order. The champion and end users come first, security and finance arrive once the deal looks real, and procurement plus legal appear only after a verbal yes.

Contract value is the best predictor of how many of the seven you will meet. A 9,000 dollar team tool usually involves a manager and their team, so two roles. A 60,000 dollar platform pulls in five to seven. Above roughly 150,000 dollars you get all eleven seats including a second security reviewer and an outside counsel review of the MSA.

Read the right-hand column again. Only two of those seven assets are things a salesperson can produce in a deal cycle. The rest are marketing artefacts that either exist before the deal starts or hold it up by a week each while somebody writes them.

When a deal stalls at security review, the usual fix is a sales engineer manually filling in a 280-question spreadsheet. That takes four to nine hours and repeats on every deal. The marketing fix is one public trust page and one pre-filled questionnaire, built once. Same outcome, roughly a hundredth of the recurring cost.

## The 81 percent problem: most of this happens before you know the deal exists

6sense's B2B Buyer Experience Report found that 81 percent of buyers had already picked a preferred vendor before they contacted any sales team, and that the preferred vendor went on to win about 84 percent of the time. Gartner's number sits alongside it: buyers spend roughly 17 percent of their total purchase journey meeting suppliers at all, split across every vendor in consideration.

That changes what committee marketing is for. You are not trying to influence a live evaluation with a well-timed email. You are trying to be the vendor the champion already wanted before the evaluation opened, and then to make it easy for that champion to defend the choice. Everything on the [b2b saas buying committee benchmarks](/research/b2b-saas-buying-committee-benchmarks/) page points the same direction.

**81%** of B2B buyers had selected a preferred vendor before contacting any sales team

So the sequencing is backwards from how most teams run it. The committee assets are not late-funnel collateral. They are the thing that makes an early-stage reader confident enough to start an internal conversation at all, which is why they belong in your core [B2B SaaS marketing](/b2b-saas-marketing/) programme rather than in a sales enablement folder nobody opens.

## Build a committee map that survives contact with a real deal

A committee map is a one-screen table per open opportunity: name, role, what they care about, whether they are for you, and what you last gave them. Most CRM instances already have the fields. Almost nobody fills them in, because nobody made it somebody's job.

**Mapping a live opportunity**

The output that matters is the aggregate. Count contacts per closed-won opportunity across your last 50 deals. If the median is two, you are running single-threaded and your win rate is hostage to one person's job security. A healthy mid-market number is five or six.

## Why one champion beats eleven nurture tracks

Here is the position this page takes: build assets for all seven roles, and route almost all of them through one person. Per-persona nurture is the wrong answer for nearly every SaaS company under 50 million dollars in revenue.

The reason is unglamorous. You cannot get the email addresses. Your form captures a marketing manager. The CFO who approves the spend has never visited your site, is not in your database, and would not open a cold nurture sequence from a vendor their team is evaluating. Buying an enriched list of CFOs at your target accounts and dripping them content produces exactly the outcome you would expect, which is a rising unsubscribe rate and one very annoyed champion who now has to explain why the vendor spammed their boss.

The champion, by contrast, has something you will never have: internal credibility and a recurring meeting. They can walk the business case into a budget review. You cannot. Design for that. This is the core argument behind [buying group marketing for B2B SaaS](/guides/buying-group-demand-generation/) as well, and it is why the definition on the [buying committee](/glossary/buying-committee/) page emphasises roles over contact records.

Direct multi-threading still earns its place in two situations. Named enterprise accounts where an ABM programme genuinely has the contact data and the ad budget to reach eight people at one company. And security, where the reviewer will find your trust page themselves without any introduction, because that is how their job works.

Over-indexing on the champion has a failure mode too. If your champion leaves, the deal dies with them, and champion turnover kills a real share of enterprise pipeline every year. The mitigation is not more nurture tracks. It is insisting on a second named contact before you forecast the deal, and making the business case a document that lives in their shared drive rather than an attachment in one person's inbox.

## What goes in a champion enablement kit

Five assets. Build them once, version them twice a year, and give every AE the same links so the story does not drift.

**The one-page business case.** Problem, current cost of doing nothing, proposed spend, expected return, implementation timeline, risk. One page, editable, no logo bigger than the numbers. The champion will change your figures to match their reality, which is fine and in fact the point. A ready-made [champion business case template](/templates/champion-business-case/) saves you the six weeks of internal debate about format.

**This ROI model.** A spreadsheet, not a web calculator, because the CFO wants to see the formulas and change the assumptions. Keep it to eight inputs or fewer. Anything longer gets replaced by the CFO's own model, which will be less favourable to you.

**The internal deck.** Ten to fourteen slides the champion presents as their own recommendation. Branded lightly, written in their voice rather than yours. Include one slide on why now, one on what happens if the decision slips a quarter, and one on the two alternatives considered and rejected.

**This security summary.** Two pages for a non-technical audience: where data lives, who can access it, which certifications you hold, what happens in an incident. This is the document the champion forwards to IT before the formal review starts, and it often prevents the formal review from being a blocker at all.

**The competitor comparison.** An honest one. If a rival genuinely does something better, say so and say who should pick them. Champions get destroyed internally when a colleague finds the weakness they were not warned about, and a [SaaS competitive battlecard template](/templates/competitive-battlecard/) that only lists your wins is worse than no battlecard. The deeper version of this sits in [content that helps your champion sell internally](/guides/champion-enablement-content/).

## Security review is a marketing surface, not a sales chore

The security reviewer is the only committee member who will find your material without a human introducing it. They search for your company name plus "SOC 2" or "trust centre", and what they find either speeds the deal up or adds three weeks.

Vanta, Drata, Gong and Rippling all publish trust pages that answer the standard questions without a conversation: certifications with issue dates, subprocessor lists, uptime history, data residency, and in several cases a downloadable SOC 2 report behind a click-through NDA. Vanta and Drata both sell trust-centre products, which is why their own pages are worth copying as a specification.

| What the reviewer asks for | If it is public | If it lives in an inbox |
| --- | --- | --- |
| SOC 2 Type II report | Same day, self-serve with NDA click-through | 2 to 5 days, needs AE plus legal |
| Penetration test summary | Same day | 3 to 10 days, often needs the vendor's own vendor |
| Subprocessor list | Same day | 1 to 3 days and frequently out of date |
| Completed security questionnaire | Same day if pre-filled to CAIQ or SIG Lite | 4 to 9 hours of SE time per deal |
| Data processing agreement | Same day | 2 to 7 days, legal queue |

Put a rough cost on the right-hand column. If you run 120 security reviews a year and each burns six hours of sales engineering plus two weeks of calendar time, a trust page pays for itself in the first quarter. That is the least contested ROI case in this entire article.

## Procurement and legal, where good deals go quiet

Procurement is not trying to negotiate you down as its first move. Procurement is trying to complete a file. Missing paperwork causes more delay than price disagreement, and the paperwork is boringly consistent across companies.

The pack that unblocks it: current W-9 or local tax equivalent, certificate of insurance naming the required coverage levels, signed vendor information form, standard MSA and DPA in Word format with your acceptable redlines pre-marked, three reference customers of similar size, and a clear written discount policy so procurement can tell their boss they extracted something. Keep all of it in one folder an AE can share in thirty seconds.

Legal moves at the speed of your willingness to publish terms. Companies that post their MSA, DPA and SLA publicly get redlines back in days because outside counsel can review before the deal is even signed off internally. Companies that treat the contract as confidential until the last moment get a two-week legal queue at the exact moment everyone wants to close the quarter. The teardown in the [enterprise SaaS deal teardown](/examples/enterprise-saas-deal-teardown/) shows the stage-by-stage version of this with dates attached.

A 140,000 dollar deal verbally agreed on 12 March. Security cleared 19 March. Procurement requested an insurance certificate on 23 March that the vendor's broker took nine business days to reissue. Legal redlines landed 6 April. The deal signed 14 April and slipped a quarter. Nothing in that sequence was about the product, the price or the champion.

## How to tell whether any of this is working

Four numbers, tracked quarterly. None of them require an attribution platform.

- **Contacts per closed-won opportunity.** Median should move from two toward five or six within two quarters of shipping the kit.
- **Days in security review.** Measure from first questionnaire to cleared. A published trust page typically takes this from three weeks to under one.
- **Business case attachment rate.** What share of opportunities above your ACV threshold have the business case sent. If it is under 40 percent, your AEs do not know it exists.
- **Stage where deals die.** Tagged at close-lost. When procurement and legal account for more than 15 percent of losses, the problem is paperwork rather than positioning.

Self-reported attribution helps here in a way platform data cannot. Add one question to your demo form: "who else will be involved in this decision?" The answers become both a committee map and a content backlog, and the [champion enablement for buying committees](/playbooks/champion-enablement-b2b-saas/) playbook turns that backlog into a production schedule.

## Start with the two seats you have never written for

Pull your last 20 closed-won deals and list every person who touched them. You will find two roles that received nothing from you at any point, and for most SaaS companies those two are security and finance. Build those assets first, because they are the ones already costing you calendar weeks.

**First 30 days**

The work is unglamorous and none of it will win a content award. It will, though, take weeks out of your cycle and raise the number of people inside the account who can defend the purchase when your champion is on holiday. That is the whole job.

## Frequently asked questions

### How many people are on a B2B SaaS buying committee?

Gartner's research on complex B2B purchases puts the typical buying group at six to ten people. In SaaS the number tracks contract value: a 10,000 dollar tool often involves two or three, a 60,000 dollar platform involves five to seven, and anything above 150,000 dollars usually adds procurement and legal for a total near eleven. Count distinct job functions, not email addresses.

### Who are the seven roles in a SaaS buying committee?

Champion, economic buyer, end user, IT and security reviewer, procurement, finance and legal. The champion drives the internal process, the economic buyer owns the budget, end users decide whether the product is adopted, IT and security clear the risk, procurement negotiates terms, finance approves the spend and legal signs the paper. One person can hold two roles at smaller companies.

### What is champion enablement in B2B SaaS?

Champion enablement means giving your internal advocate the material they need to sell your product to their colleagues without you present. In practice that is a one-page business case, an editable ROI model, an internal slide deck, a security summary and a competitor comparison. The test is simple: could your champion forward it to their CFO unchanged and have it land.

### Should we build a separate nurture track for each buying committee persona?

Usually not. Most SaaS companies cannot get valid email addresses for the CFO, the security lead and the procurement manager, so a per-persona drip reaches an audience that does not exist. Build assets each role would find useful, then route them through the champion who already has internal credibility and calendar access. Reserve direct multi-threading for named enterprise accounts.

### Why do SaaS deals stall in security review?

Because the reviewer needs artefacts nobody prepared. A typical software security review requests a SOC 2 Type II report, a penetration test summary, a data processing agreement, a subprocessor list and a completed questionnaire. If those live in a salesperson's inbox rather than on a public trust page, each request adds days. Companies with published trust centres routinely cut two to four weeks from this stage.

### How do you market to an economic buyer you cannot reach?

You write for them and deliver through someone else. The economic buyer reads one document: a short business case with the problem, the cost of the status quo, the proposed spend, the expected return and the risk of doing nothing. Make that document a single page, make the numbers editable, and hand it to the champion who already has the meeting booked.

### What is the difference between a buying committee and a buying group?

Nothing meaningful in practice. Buying committee is the older sales-side term for the set of people who must agree on a purchase. Buying group is the newer demand-side term, popularised as CRM platforms added the ability to score an account's set of contacts rather than one lead. Same people, different system of record.