Shalvi Singh's writing

GTM Fundamentals · intermediate · node 2.2

The buyer committee

A buying decision is made by a committee whose composition varies by company size, industry, and risk profile. The committee is not optional—even a sole founder deciding to buy enterprise software has a committee (themselves as founder, the finance person, the ops person). The committee's makeup determines the decision timeline, what criteria matter, what gets blocked, and who has veto power. In a startup, speed and founder vision dominate. In growth-stage companies, procurement and legal gain weight. In enterprises, you must navigate economic buyers, end-users, IT departments, and sometimes CFOs with opposing interests. Your motion fails when you sell to the wrong committee member or assume a consensus that does not exist. Successful GTM means mapping who sits at the table, what incentivizes each member, and how to build alignment or manufacture consensus.
intermediate Last updated 2026-06-25

Prerequisites

GTM Stack/TiersMarket structure

You are selling to a company, not to a person. But the company does not speak with one voice. It speaks with several, and they want different things.

This is why the best pitch to an engineer differs radically from the best pitch to the buyer’s CFO—and why a sales motion that works perfectly when you reach the right person falls apart when you reach the wrong one.

Your GTM must first answer a question most founders skip: who sits at the committee table? And then: what is each member’s incentive, veto power, and timeline?

The diagnostic: who is in the committee for each segment?

A buyer is not one person. A buyer is a coalition of people whose interests may or may not align, whose veto power varies, and whose priorities are shaped by what their boss measures them on.

The composition of this committee varies by:

Company size. A 5-person startup has a committee of one (the founder) who overrides all consensus. A 50-person company has a founder still calling shots, but with a CFO and ops person pushing back on cost. A 500-person company has founders who have lost direct override authority; they have to convince the CFO, the CIO, the VP of Ops, and the end-user department. An enterprise (5,000+) has committees that barely talk to each other and have opposing interests.

The decision’s integration depth. A tool that connects to nothing has a smaller committee. The engineer who needs it can demand it, and the decision is made. A tool that integrates with your ERP, your billing system, your analytics platform, and your data warehouse has a massive committee. Procurement gets involved. IT gets involved. Finance gets involved. The CFO’s office gets involved because now you’re touching critical infrastructure.

Risk profile. Low-risk, low-cost decisions (a $500 SaaS tool) have a small committee: the person who wants it and their manager. Medium-risk decisions ($50,000, critical to a single team) add procurement and the department head. High-risk decisions ($500,000, organization-wide, strategic) add C-suite, legal, finance, IT, and sometimes the board.

Existing precedent. Has the company already bought from your category? If your category is familiar (CRM, email tool, analytics platform), the committee is smaller and moves faster because decision frameworks exist. If your category is new to them (AI governance, composable infrastructure, synthetic data), the committee is larger because it has to justify itself to skeptics.

Organizational design. The same company size can have radically different committees depending on structure. Some organizations centralize procurement; others let departments buy freely. Some have strong IT gatekeeping; others have none. Some give the CFO veto over all software; others don’t. The org chart, not the company size, determines the committee.

To diagnose your committee, ask:

  1. Who owns the budget? This is the economic buyer. It might be the CTO, CFO, COO, or VP. They control approval and can say no for financial or strategic reasons.
  2. Who will use the product? These are the end-users. They have veto power only if they actively resist; otherwise they are information providers who confirm the tool is worth the switching cost.
  3. Who blocks solutions they dislike? This might be IT (if they have real control over infrastructure), Procurement (if they have authority), Legal (if there are contract risks), or Compliance (if you touch regulated data).
  4. Who can override everyone else? In startups, this is the founder. In mid-stage companies, this is often the CTO or CEO if they have conviction. In enterprises, this is rare; consensus is required.

Get specific names. When you say “the CFO blocks budget,” you mean a specific person. When you say “IT must approve,” you mean specific people and processes. The committee is not abstract.

The diagnostic matrix: mapping incentives

Once you know who sits at the table, map what each member wants. This is where most sales motions break down.

Assume a $200,000 infrastructure-software deal at a 200-person company. The committee likely looks like this:

The CTO (economic buyer). Owns the budget. Measured on infrastructure reliability, cost, and developer velocity. Wants lower cost, faster deployment, fewer integrations to maintain. Will evaluate: price, ROI timeline, switching costs, operational complexity.

The Head of Finance (procurement gatekeeper). Does not own the decision but can block it. Measured on cash efficiency and risk management. Wants predictable costs, long contract terms, vendor stability, established market position. Will evaluate: price, contract terms, vendor financial health, SLA guarantees.

The VP of Engineering (end-user advocate). Does not own the decision but can veto. Measured on team velocity and system reliability. Wants tools that require minimal training and integrate with existing systems. Will evaluate: ease of adoption, team impact, vendor responsiveness.

The IT Security Officer (risk gatekeeper). Does not own the decision but can block. Measured on security incident avoidance. Wants SOC 2 compliance, data residency controls, access logging, vendor audit compliance. Will evaluate: security posture, compliance, data handling.

These four people cannot all be convinced by the same argument. The CTO cares about architecture fit. Finance cares about contract terms. Engineering cares about adoption friction. Security cares about compliance.

If your motion emphasizes architecture fit (the CTO pitch) and ignores contract terms, Finance will slow-walk the deal. If you emphasize lower costs (the Finance pitch) but the tool requires six months of integration work, Engineering will resist. If you ignore security requirements and assume they will be “figured out in the legal process,” Security will block the entire deal.

The motion must address all four, in their language, with evidence that matters to them.

CTO pitch: “This reduces your infrastructure complexity from X to Y, cuts provisioning time from days to minutes, and integrates with your existing Kubernetes setup. Switching cost is three months of migration; payback is six months of reduced ops costs.”

Finance pitch: “Three-year contract, locked pricing, transparent cost model with no per-node surprises. We have $200M funding, SOC 2 certified, and references at similar-scale companies.”

Engineering pitch: “Your team can adopt this in parallel to existing systems. We provide a two-week onboarding. No one rebuilds their integrations. Your current tooling stays in place.”

Security pitch: “SOC 2 Type II, data residency in your region, encryption at rest and in transit, full audit logs, and quarterly vendor security reviews. We maintain a $5M cyber insurance policy.”

Notice: the same product, four completely different narratives. Each committee member cares about different dimensions of the same product. Your pitch must cover all four, or the committee will fragment and the deal will stall.

The timeline problem: committee size predicts decision speed

Here is a hard rule: committee size inversely predicts decision speed.

A founder making a decision alone can move at founder speed: I want this, we buy this, we sign on Tuesday. Timeline: 1 week.

A 3-person committee (founder, finance, ops) can move at consensus speed if consensus is natural. If not, timeline: 2-4 weeks of alignment meetings.

A 5-person committee (CTO, CFO, VP Eng, IT, Compliance) where not everyone agrees can easily stretch to 2-3 months. Each person thinks they are protecting the company. Each person raises legitimate concerns that require addressing.

An enterprise committee (CTO, CFO, VP Ops, VP of category, Legal, Security, Procurement) where there is no clear override authority routinely takes 6-12 months. The decision does not fail; it just stalls across quarterly boundaries, gets reopened with new stakeholders, and eventually muddles forward.

Most founders understand this intellectually but not in their GTM design. They see a 3-month deal and assume poor sales execution. But if the committee is genuinely 5 people, and they do not all agree, and there is no override authority, three months is fast.

To accelerate the timeline, you do one of three things:

Reduce the committee. Find a buyer who can override the consensus and take the risk. This usually means selling to the founder or a C-level with authority. It is the fastest path but often involves higher stakes and stronger personalities.

Create urgency that collapses alignment. When the pain is acute enough, committees move faster. A company in crisis makes decisions in days. A company optimizing in good times takes months. Create urgency through competitive tension (“another company in your space just signed”), regulatory change (“this new rule requires you to implement by Q3”), or threat escalation (“your current vendor is at EOL”).

Build consensus proactively. Do the alignment work upfront. Get all stakeholders in the room early. Address objections from each person before they become blocking issues. This extends the early process but shortens the negotiation and closing phases.

Most teams try to minimize the early alignment work, thinking it slows deals. But skipping consensus work pushes the problem to the end: you close the CTO, then Finance blocks you, then you have to reopen the whole thing. It is better to spend two weeks building consensus early than six weeks waiting for Finance to catch up.

Asymmetric committees: same size company, different structures

The same company size can have radically different committee structures and decision speeds. This matters because it means the same product needs different motions depending on which company you are selling to.

Company A: 150 people, founder-led, flat org. The founder still makes major vendor decisions. Procurement exists but is weak. IT is understaffed and mostly reactive. Budget owner: CEO/Founder. Committee size: 2 (founder, finance person). Timeline: 2-4 weeks. Pitch strategy: founder-first, with finance details secondary.

Company B: 150 people, founder-backed, departmentalized. The founder has stepped back. VP of the relevant function owns the budget. Procurement has authority. IT has veto power on infrastructure. Budget owner: VP of the function. Committee size: 4-5. Timeline: 6-8 weeks. Pitch strategy: VP-first, build alliances with Procurement and IT, founder only if there is stalling.

Same size. Opposite committee structures. The GTM that works for Company A (founder-first, informal process, quick closing) will fail at Company B (VP first, formal RFP process, vendor review board).

To diagnose which structure your prospect has:

Ask the champion: “Who will be in the final approval meeting?” If they name one person (the founder, the VP), small committee. If they name three or more people, larger committee.

Ask: “Is there an RFP process?” If yes, Procurement has authority. If no, decision is more informal.

Ask: “Has IT reviewed us yet?” If yes and they are positive, timeline is shorter. If not, IT is a future gate. If no and you know they will object, timeline just extended.

Ask the champion directly: “Is your boss the final decision maker?” If yes, small committee. If no, it is larger.

Do not assume. Ask directly. The champion usually knows the real structure even if they are not in every meeting.

Mapping stakeholder incentives: the real framework

Once you know the committee and the timeline, map each person’s incentive. Here is the framework:

What does this person’s boss measure them on? (This is their primary metric.)

What outcome would make them look good to their boss? (This is their win condition.)

What outcome would make them look bad? (This is what they will block.)

What is their veto power? (Can they kill the deal alone?)

What information persuades them? (References, numbers, case studies, technical docs, compliance proof, financial analysis?)

An example:

CIO at an enterprise (decision-gate, veto power).

  • Measured on: System uptime, security posture, vendor stability, cost containment.
  • Looks good if: Implemented on time, no outages, passes security audit, stays on budget.
  • Looks bad if: New vendor causes outages, security breach, vendor fails, implementation overruns, hidden costs.
  • Veto power: Absolute. Can kill any infrastructure vendor deal.
  • Persuaded by: SLAs, reference calls with other CIOs, security audit results, 3-year stable financials, no surprises in the contract.

Head of Procurement (decision-gate, veto power).

  • Measured on: Contract terms, avoiding bad deals, volume discounts, vendor compliance.
  • Looks good if: Gets favorable terms, vendor stays solvent, no legal surprises, negotiates down.
  • Looks bad if: Gets fleeced, vendor negotiates hard, contract surprises, vendor fails and causes chaos.
  • Veto power: Can kill deals on contract terms.
  • Persuaded by: Market-standard terms, proof of how other customers negotiated, volume discounts, payment flexibility, clear termination clauses.

VP of Engineering (influencer, weak veto).

  • Measured on: Team velocity, code quality, time to deployment.
  • Looks good if: Tool does what was promised, team adopts it, velocity improves.
  • Looks bad if: Tool slows the team down, requires extensive training, integrates poorly, team resists.
  • Veto power: Can delay by pushing back hard, but CTO can override.
  • Persuaded by: Demo that works, user testimonials, minimal training required, API documentation, quick integration path.

When you map incentives this precisely, your pitch changes. You are no longer selling the product. You are selling the outcome that makes each committee member look good.

The asymmetry: same product, different narratives

Here is a concrete example. You are selling infrastructure software to a 500-person company.

To the CTO (technical decision-maker): “Your team can migrate in 8 weeks with zero downtime using this migration toolkit. Your ops cost drops 30%. You own this decision.”

To the CFO (finance gatekeeper): “Your current vendor bills on consumption; this is fixed capacity with predictable annual costs. Three-year agreement at locked price. Same reliability, 20% lower cost.”

To Procurement (legal gatekeeper): “Standard MSA with SOC 2, no custom terms required. Other Enterprise customers negotiate these exact terms. No surprises in year two or three.”

To the CIO (security gatekeeper): “We pass your standard security questionnaire. SOC 2 Type II. Data stays in your region. Quarterly security reviews. $10M cyber liability insurance.”

Same product. Four narratives, each addressing what makes that person look good. When you pitch the CTO about cost, you bore them. When you pitch the CFO about architecture, you lose them. When you pitch Procurement about technology, you remind them that technical people negotiate badly.

The mistake most teams make is writing one pitch and trying to use it for everyone. This assumes the committee is aligned and cares about the same things. In large deals, the committee is fragmented. Alignment is the problem you must solve.

Founder mistakes: selling to the wrong committee member

Mistake 1: Selling to the enthusiast instead of the budget holder.

The CTO loves your product. They want to buy it. They champion it internally. You think you have a deal. But the CFO owns the budget and has concerns about contract terms. The deal stalls. You spend weeks on the CTO, who has no budget authority, while the real decision-maker (the CFO) has not been convinced.

The fix: Ask directly—“Who owns this budget?” If the answer is not the person you are talking to, involve the budget holder immediately. The CTO can be your champion, but the CFO must be your buyer.

Mistake 2: Assuming consensus when there is disagreement.

You close the CTO. You think you have a deal. Six weeks in, Procurement says the contract terms are unacceptable. The deal reopens. You now have to negotiate Procurement while keeping the CTO happy. The deal drags.

The fix: Get all committee members aligned before signature, not after. Ask the CTO: “Will Procurement negotiate on terms, or do they have fixed requirements?” If fixed, get Procurement in the room early.

Mistake 3: Losing the champion by ignoring the gatekeepers.

Your champion (the VP of Engineering) is 100% sold. But you have not addressed IT’s security concerns. IT blocks the deal. Your champion now looks bad (“I pushed this and it got killed”) and loses authority. They distance themselves. The deal dies.

The fix: The champion’s credibility depends on delivering a smooth process. Make the champion look smart. Ask them: “Who else needs to be convinced? What are their concerns?” Help your champion win internally by pre-addressing IT’s concerns.

Mistake 4: Selling benefits, not outcomes.

You pitch the CTO on the tool’s architecture. You pitch the CFO on the feature set. But you have not mapped what outcome makes each person look good. The CTO cares about his ops cost and team velocity. The CFO cares about price and predictability. The architecture is a means to those outcomes, not the outcome itself.

The fix: Ask each committee member directly: “If we implement this, what would success look like for you?” Then measure your pitch against their definition, not yours.

Mistake 5: Thinking the decision is binary when it is sequential.

You assume the committee decides all at once. But often, they decide sequentially: IT approves, then Procurement approves, then Finance approves, then Ops approves. If any gate rejects you, the deal restarts at the beginning or dies entirely. A smooth committee process is one where each sequential gate approves because you have pre-addressed their concerns.

The fix: Map the approval sequence with your champion. Identify each gate. Address each gate’s concerns before you submit to them. A deal that is sequentially approved is slower but much more likely to close.

The rules

Rule 1: The committee is not optional. Even a founder buying software for their startup has a committee: the founder deciding as founder, the finance person reviewing, the ops person assessing implementation. Get specific names.

Rule 2: Committee composition predicts timeline. Larger committees take longer. This is not a failure of your sales motion; it is math. Account for it in your forecast.

Rule 3: Incentives determine what persuades. The CTO is not persuaded by contract terms. The CFO is not persuaded by architecture. Know what each person needs to hear.

Rule 4: Consensus is not assumed; it is built. You must work to align a fragmented committee. The team that skips alignment work pays for it in the closing phase.

Rule 5: The champion’s credibility depends on the process being smooth. Help your champion look smart. Address gatekeepers’ concerns before the champion stakes their credibility on your deal.

Rule 6: Veto power is real. Some committee members can kill the deal alone. Identify them early. Do not let a veto surprise you in month three.

The next question: what buys this committee?

Knowing the committee is the foundation. The next step is understanding how this specific committee buys. Does it require a lengthy RFP process? Do they rely on vendor comparisons? Are they constrained by procurement policy?

Once you know the committee and how they buy, you design a motion that navigates both. The product has not changed. Your GTM has.

Key takeaways

  • Buying decisions are made by committees, not individuals. The committee varies by company size, risk, and integration depth.
  • Committee composition determines decision speed (founder override vs. consensus), criteria (cost vs. risk vs. fit), and veto power.
  • In startups, the founder often overrides everyone else. In enterprises, fragmented incentives create competing veto points.
  • The same size company can have radically different committee structures depending on who owns the budget and organizational design.
  • Founder mistake: selling to the CTO when the CFO or CEO has veto power, or assuming alignment that requires alignment work.

Related concepts

Sales motionStakeholder alignmentBuying criteriaDecision timelineProcurement

How to cite this

@misc{shalvi_gtm_fundamentals_the_buyer_committee_2026,
  author = {Singh, Shalvi},
  title  = {The buyer committee},
  year   = {2026},
  url    = {https://shalvisingh.com/gtm/fundamentals/the-buyer-committee},
  note   = {GTM World Model — GTM Fundamentals}
}

Singh, Shalvi. "The buyer committee — GTM Fundamentals." shalvisingh.com, 2026. https://shalvisingh.com/gtm/fundamentals/the-buyer-committee