The Buying Committee
In B2B enterprise, one person wants your product and six people can kill the deal — mapping the buying committee is as important as the product itself.
🎯 By the end you'll understand
Who sits on a typical B2B enterprise buying committee and what each role actually cares about, how to develop a champion and what champions specifically need from you to win the internal fight, why deals go dark after a positive discovery call and what that silence usually means, and how to build and read a stakeholder influence map that tells you where your deal is actually at risk.
KEY INSIGHTThe person who wants it cannot buy it alone
You close deals with economic buyers. You build deals with champions. You lose deals to people you never met.
Your discovery call went well. The Director of Quality at a mid-sized auto parts manufacturer was engaged, asked smart questions, and said three times that this is exactly what her team needs. You followed up with a deck, a pricing sheet, and a proposed pilot timeline. That was three weeks ago. She has not returned your calls. You think something changed. You are right — but not in the way you think. The champion you developed is still on your side. The economic buyer you never spoke to has put the budget conversation on hold. The IT security lead you do not know about has flagged your edge device deployment request for a full vendor assessment. And procurement has added you to a queue that moves on a 90-day cycle you were never told about.
A deal with a single champion is not a deal — it is a warm conversation waiting to be killed by the org. Enterprise purchases involve multiple stakeholders with different incentives, different veto powers, and different relationships to your product. The founder who maps only the champion maps only one node in a network where any other node can kill the deal unilaterally. Stakeholder mapping is not a nice-to-have sales activity. It is the analytical work that tells you whether you actually have a deal.
CORE CONCEPTThe six roles on a B2B enterprise buying committee
These roles are not always six separate people. In smaller companies, one person plays two or three. In enterprise, they are genuinely distinct, with separate reporting lines and separate agendas. The mistake is assuming the org chart reflects the actual influence map — it rarely does.
Champion — your internal seller
The champion is the person inside the account who wants you to win and is willing to put their credibility on the line to make it happen. They attend your calls, coach you on the internal politics, share documents they are not supposed to share, and run interference when other stakeholders raise objections. Without a champion, you do not have a deal — you have a product demo that someone found interesting. Champions are usually the person who first identified the problem your product solves, and they are typically mid-level: senior enough to have organizational credibility, junior enough to still feel the pain personally. In Forge's target ICP, that is typically the Director of Quality or Quality Engineering Manager.
What the champion is not: the most senior person who has heard of you. An executive who said "this looks promising" at a conference is not a champion. A champion is someone who has a specific personal win tied to your product succeeding and has taken a concrete action to advance the deal internally — booked your meeting with the economic buyer, forwarded your materials to IT, scheduled the site visit. Action is the differentiator.
Economic buyer — the person who writes the check
The economic buyer controls the budget. They have discretionary authority to approve the spend without requiring a committee decision above them — or they have direct access to the person who does. In a $30K–$80K ACV deal for a manufacturer, the economic buyer is typically the VP of Operations, COO, or CFO. They rarely attend product evaluations. They care about one thing: the financial return on the spend, expressed in terms they already use (scrap reduction, rework cost, downtime minutes per month, customer charge-backs). You cannot close a deal without access to the economic buyer. A champion who cannot get you a meeting with the economic buyer is either too junior to move the deal or insufficiently committed to doing so. Both are serious red flags.
Technical evaluator — the person who can say no to the product
Technical evaluators control the technical compatibility assessment. In a manufacturing context, this is often the IT/OT (operational technology) manager, the systems integrator who manages the plant floor infrastructure, or the engineering lead who owns the MES (Manufacturing Execution System). They do not care if the product solves the business problem — they care whether it can be deployed without creating new security risks, integration headaches, or operational dependencies on a vendor who might not exist in three years. Technical evaluators can veto a deal even if the champion and economic buyer are aligned. They must be engaged separately, with a different message than you use with the business stakeholders.
End user — the people who will live with the product
End users are the inspection operators, QA technicians, and line supervisors who will actually interact with your product daily. They are rarely involved in the buying decision until late, and then often only as a veto bloc: if they complain loudly enough that the system is unusable or creates more work, they can reverse a deal that has already closed. Smart sellers involve end users early — not to close them, but to remove the late-stage objection. A pilot that includes end user training and feedback loops is far more likely to convert than one that installs a device and expects adoption without investment.
Legal / procurement — the people who control the timeline
Legal and procurement do not evaluate your product at all. They evaluate your contract, your data practices, your insurance, your liability exposure, and whether your terms match their standard vendor template. In enterprise, legal review is measured in weeks to months, not days. Procurement has standard payment terms (net-60 is common) and required process steps (RFP, approved vendor list, DPA) that are non-negotiable. The founder who closes a verbal agreement in October and expects a signed contract in November has not talked to procurement. Engage legal and procurement early — not to rush them, but to understand the timeline and requirements before they surprise you.
Executive sponsor — the air cover that makes budget real
The executive sponsor is a senior leader (VP, SVP, C-suite) who has made your category of problem a priority. They do not run your evaluation — they create the organizational permission for it. When the CFO says in a quarterly review "we need to reduce our quality-related costs by 15%," that is the executive sponsor moment. Deals that have executive sponsorship move differently: budget is easier to release, internal resistance is lower, procurement moves faster. The absence of an executive sponsor is not fatal — many deals close without one — but it means your champion is fighting the internal budget battle without air cover, which is slower and riskier.
| Role | Primary concern | Their win condition | Typical veto power |
|---|---|---|---|
| Champion | Problem solved; personal credibility with sponsor | Looks smart for finding the solution | Weak alone; strong when aligned with EB |
| Economic Buyer | ROI — cost reduction or revenue protection | Budget well spent, no surprises | Absolute on budget; can kill with one word |
| Technical Evaluator | Security, integration, supportability | No new infrastructure risk added | High — can block indefinitely with "security review" |
| End User | Ease of use; does it make my job harder? | Same or better workflow, less blame for escapes | Moderate — loud complaints can unwind a closed deal |
| Legal / Procurement | Risk, compliance, fair process | Standard-compliant contract, approved vendor | Timeline veto — can delay 3–6 months |
| Executive Sponsor | Strategic priority execution | The initiative succeeds visibly | Positive — accelerates rather than blocks |
HOW IT WORKSDeveloping your champion — what they need from you
Champions do not arrive fully formed. You develop them. A champion starts as someone who is engaged and interested; they become a champion when they take visible internal action on your behalf. The transition from interested contact to active champion is the most important move in enterprise sales — and it requires specific inputs from you, not just enthusiasm about your product.
Here is what champions actually need to do their internal selling:
A business case they can present without you
Your champion will be asked to justify the spend in a meeting you will not attend. If the only thing they can say is "it detects defects better," they will lose to the CFO's "can we do this with existing headcount?" objection. You need to give your champion a one-page ROI summary — in the exact units their company uses — that they can walk into a budget meeting and defend. For Forge: average quality escape cost ($X per incident based on the customer's own data), current escape rate, estimated reduction from Forge deployment, payback period in months. The champion presents your math, not your product. Make the math easy for them to explain and defensible under pressure.
Ammunition for the objections they know are coming
Your champion has already heard the internal objections before you have. They know the CTO will raise a security question. They know the operations team will worry about downtime during installation. They know legal had a bad experience with a small vendor three years ago. Ask your champion directly: "What objections are you going to face when you propose this internally? Let's work through each one." Then prepare written responses — not for you to send, but for your champion to deliver. The champion who has a ready answer to the security question looks prepared and credible. The champion who has to say "let me go back and ask the vendor" looks like they did not do their homework.
Access to the right people, structured as their request
You cannot ask for a meeting with the economic buyer cold — it looks presumptuous and puts your champion in an awkward position. Instead, coach your champion to request the meeting as their own initiative: "I'd like to bring in the team to walk through the ROI model with you — do you have 30 minutes next week?" The same meeting, but your champion owns it. This approach works for every stakeholder. You need IT access? Your champion schedules a joint technical review. You need procurement to move faster? Your champion makes the internal case for prioritization. Your job is to coach the request, not make it yourself.
Regular intel on the internal state of the deal
The champion is your eyes inside the account. Develop a cadence — weekly check-in, not "just following up" but specific questions: "Did you get time with Maria about the budget? What did she say? Who else is she talking to?" This cadence serves two purposes. First, you get intelligence about deal health that you cannot see from outside. Second, the regularity of contact keeps the deal alive in your champion's mind — enterprise buyers are busy, and deals that are not top of mind get deprioritized without malice. Your champion has thirty other things to do; a standing touchpoint keeps your deal on the active list.
Ask your champion to take one concrete internal action before your next scheduled call — book a meeting with the economic buyer, forward your security FAQ to IT, or send you the procurement vendor intake form. If they do it: real champion. If they explain why they could not this week but definitely will next week: marginally committed champion who needs help removing blockers. If three calls go by with no internal action: you are talking to a champion who cannot or will not do the internal selling, and you need to either develop a new champion or qualify the deal out.
Not all champions are equal. A champion who is enthusiastic but organizationally marginal — new to the role, low tenure, no budget history, no direct access to the economic buyer — is a champion who cannot win the internal fight regardless of how much they want to. Enthusiasm without influence does not close deals. You must assess your champion's organizational influence explicitly, not just their personal commitment to your product.
SEE ITStakeholder Map Builder — visualize deal risk from influence vs. support
The map forces three questions that most early-stage founders skip. First: have you identified an economic buyer at all? A map with only a champion and end users is not a deal map — it is a wish list. Second: do you have any high-influence supporters, or is your entire deal resting on people who care but cannot move budget? Third: have you identified your high-influence resistors? Knowing who can kill your deal before they do is the entire point of the exercise.
FORGEMapping the buying committee at Forge's eight accounts
Forge has closed eight customers and $320K ARR. The founder has closed every deal personally. Across those eight deals, a clear pattern has emerged in the buying committee structure — and the pattern reveals both where deals have been moving reliably and where the current pipeline is exposed.
Champion: Director of Quality or Quality Engineering Manager — the person whose team runs with Forge daily and whose metrics are directly affected. In every closed deal, this person was the initial contact, the deal driver, and the primary reference for pilot expansion.
Economic buyer: VP of Operations or COO — controls the capital expenditure budget for production technology. In six of eight deals, this person never attended a product call; the champion presented the ROI case. In two deals, the founder got a direct meeting, which accelerated close by an average of 22 days.
Technical evaluator: IT/OT Manager or Plant Engineering Lead — reviews the edge device for network security, SCADA/MES compatibility, and vendor SLA requirements. This is where three early deals nearly stalled. Forge now sends a technical pre-assessment document before any pilot conversation, which surfaces IT objections four to six weeks earlier.
Legal/procurement: Ranges from a single procurement officer (smaller plants) to a formal vendor assessment committee (publicly traded manufacturers). Average legal review time across closed deals: 34 days. Longest: 71 days. Forge has learned to start the procurement intake process in parallel with pilot negotiations, not after.
The pattern also reveals a pipeline risk the founder has not yet fully addressed: two of the current five active deals have champions with influence scores the founder would rate 2/5 or below — mid-level quality engineers who are enthusiastic but have no direct path to the economic buyer and no established track record of initiating capital purchases. Both deals have been in "active evaluation" for more than 60 days with no economic buyer contact. In the Forge context, 60 days without economic buyer engagement is a strong signal that the champion is stuck and has not told you.
After eight deals, the Forge playbook now includes explicit champion qualification: (1) Has this person sponsored a capital purchase of >$25K in the last 18 months? (2) Can they name the economic buyer and describe their current relationship with that person? (3) Have they taken at least one internal action on behalf of this deal in the past two weeks — meeting booked, document forwarded, IT introduced? If the answer to all three is yes, this is a real champion. If any answer is no, treat it as a prospect, not a deal.
IN PRACTICEWhen deals go dark — what silence after a good call actually means
The most common and most misunderstood failure mode in enterprise sales: the positive discovery call followed by weeks of silence. The founder interprets this as the champion being busy, or deprioritizing the follow-up, or waiting for an internal meeting to happen. Those things may all be true — but they are symptoms, not the root cause. The root cause is almost always one of three things:
The champion lost the internal budget conversation
This is the most common reason for deal silence. The champion pitched the economic buyer — in a weekly one-on-one, at a quarterly planning meeting, in a Slack message — and got a "not this quarter" or "let's revisit in the new fiscal." The champion is embarrassed to tell you, because telling you means admitting they could not land the internal sell. So they go quiet and hope either the situation changes or you move on. The diagnostic: has it been more than two weeks since any response, and did the last conversation end with a champion action that required internal budget discussion? If yes, the champion almost certainly lost the budget fight. The correct response is not more follow-up emails — it is a direct, low-stakes message to the champion: "I know this kind of thing can get deprioritized internally. No problem if the timing is off — can you give me a quick read on where things actually stand?"
A new stakeholder appeared that you did not know about
A new IT security policy kicked in. A new CTO joined and froze all vendor evaluations. A compliance audit started. A competitor who already has an approved vendor relationship appeared. These external events are invisible to you but completely paralyze the champion, who is now navigating an obstacle they did not anticipate and does not know how to solve. The champion does not tell you because (a) they do not fully understand what changed yet, and (b) they are hoping it resolves on its own. The diagnostic: ask directly what has changed internally since you last spoke, not whether they are still interested.
The champion was never able to advance the deal internally and never told you
The most uncomfortable scenario: the champion was always too junior to move the deal, and neither of you acknowledged it explicitly. They liked the product, they had good conversations with you, they sincerely intended to do the internal selling — but they never had a realistic path to the economic buyer and they were not going to admit that to themselves or to you. The deal was always dead in the current champion configuration. The only corrective is to either develop a new champion who is higher in the org, or ask your existing champion directly: "To be honest with you — do you have a direct path to the person who controls this budget? If not, can you introduce me to that person so I can make the case directly?" The discomfort of that question is less expensive than another two months of follow-up.
Founders systematically interpret deal silence optimistically — "they're busy," "the meeting is coming," "they said they were interested." This is not dishonesty; it is motivated reasoning under conditions of uncertainty. The cure is to set explicit deal health criteria at the start of every qualified opportunity: if two weeks pass without a champion action (not just a response), the deal is flagged as at-risk. At four weeks without a champion action, the deal is in danger and requires a direct conversation about what has changed. Silence is data. Treat it as such.
WEAKNESSWhere this bites
The most engaged person in your sales process is often not the most powerful person. Enthusiastic champions are easy to spend time with, they give good feedback, and they make the sales process feel productive. But enthusiasm and organizational influence are independent variables. A quality engineer who loves your product and has been at the company for 14 months has zero track record of moving capital budget. An operations director who has been lukewarm in your calls but has run three technology deployments in the past two years is the person whose support actually moves the deal. Assess influence separately from engagement — they are different things.
The most common timing mistake in enterprise sales. Founders defer procurement engagement because it feels premature and transactional, and because starting the legal process signals commitment in a way that feels risky before the business case is closed. But procurement and legal run on fixed cycles that are entirely indifferent to your sales timeline. A procurement team that processes new vendors on a 90-day cycle does not care that you closed the business case in week 8 — they will start their process in week 90. Engage procurement as soon as you have a qualified opportunity, even if only to ask: "What is your vendor intake process? What do you need from us to begin the assessment?" The answer will restructure your entire deal timeline.
Champions leave. Champions get reorganized into other roles. Champions have off-quarters where they lose political capital. A deal built on a single champion is one personnel change away from starting over. The best enterprise sellers develop champion redundancy — a primary champion who drives the deal and a secondary stakeholder (often the end user lead or a friendly technical evaluator) who is independently sold on the value and can keep the deal alive if the primary champion is disrupted. In a six-to-nine-month enterprise sales cycle, not building redundancy is a bet that no one in the account will change roles, get reorganized, or lose a budget battle. That is a bad bet.
KEY INSIGHTHow this connects
- 4.4 · The Discovery Call — Learning While Selling — the discovery call is where you first map the committee. Every question you ask about "who else is involved in decisions like this" is a stakeholder mapping question. If your champion says "it's really just me and my boss," that is either true or it is a sign that your champion does not have a clear map of their own buying process — both require follow-up.
- 4.6 · Pilots, POCs, and the Pilot Trap — the pilot structure is where stakeholder map accuracy gets tested in real time. End users who were not properly engaged become blockers during pilot setup. Technical evaluators who were never briefed call a halt two weeks in. The buying committee map you build today determines whether your pilot runs clean or gets stuck in the mud.
Understanding the buying committee is not a sales technique — it is a structural description of how enterprise organizations make purchase decisions. The committee does not change because your product is better or your champion is more enthusiastic. It is the environment you are selling into, and ignoring it does not make it smaller. Every lesson in this stage builds on the assumption that you are selling to an org, not a person — this lesson is where that assumption becomes actionable.
GLOSSARYKey terms
- Champion
- The internal stakeholder who actively advocates for your product, is willing to put their credibility behind the purchase, and takes concrete actions to advance the deal inside the org. Distinguished from an enthusiastic contact by evidence of internal action, not just stated interest.
- Economic buyer
- The stakeholder with discretionary authority to approve the budget for the purchase. May be a single person (VP of Operations) or require sign-off from a small committee. The economic buyer must be engaged before a deal can close — accessing them is the champion's primary job.
- Technical evaluator
- The stakeholder who assesses the product's security, infrastructure compatibility, and operational risk. In manufacturing, typically the IT/OT manager. Technical evaluators cannot approve a purchase but can indefinitely block one by requiring assessment steps the seller is not prepared for.
- Organizational influence
- A stakeholder's actual ability to shape a purchase decision — distinct from their enthusiasm for your product. Influence is a function of seniority, budget history, cross-functional relationships, and track record of initiating similar purchases. High enthusiasm with low influence does not move deals.
- Executive sponsor
- A senior leader who has designated the category of problem your product addresses as a strategic priority. Executive sponsors do not run evaluations — they create organizational permission for spend. A deal with an executive sponsor moves significantly faster than one without.
- Champion qualification
- The set of criteria used to distinguish a genuine champion (who can and will do the internal selling) from an enthusiastic contact (who wants your product but cannot or will not move the deal organizationally). Key criteria: track record of similar purchases, path to economic buyer, evidence of recent internal action.
- Deal going dark
- The pattern of a qualified opportunity becoming unresponsive after a period of positive engagement. Almost always indicates an internal setback — budget denied, new stakeholder appeared, champion is stuck — that the champion has not communicated to the seller. Silence is a deal health signal, not a scheduling artifact.
- Stakeholder map
- A structured representation of every person involved in a purchase decision, showing their role, their relationship to the purchase (support or resistance), and their organizational influence. Used to identify deal risk — specifically, high-influence resistors and champions with insufficient organizational power to win the budget fight.
ACTIVE RECALLCheck your understanding
Answer in your own words first, then reveal.
1A founder says "I have a strong champion — they love the product and call me every week." What information is missing from this claim, and how would you determine whether this is actually a deal?›
Enthusiasm and frequency of contact are not evidence of champion quality. The missing information: Has this person taken a concrete internal action to advance the deal? (booking meetings, forwarding documents, introducing the founder to the economic buyer) Do they have organizational influence? (track record of initiating capital purchases, direct access to budget holders) Have they identified the economic buyer and established a path to that person? If the champion calls weekly but has not booked a meeting with the VP of Operations after six weeks, they are a friendly contact, not a deal driver. The test is action, not enthusiasm. A champion who cannot describe what happened internally in the last two weeks has likely not advanced the deal internally in the last two weeks.
2Your deal has been "in evaluation" for 45 days with no economic buyer contact. What are the three most likely explanations, and what is the right next action for each?›
1. Champion lost the budget conversation. Action: Have a direct, low-stakes conversation — "I know timing can shift internally — can you give me a straight read on where this stands?" Do not accuse; give them a graceful way to tell you the truth. 2. A new stakeholder or policy appeared and the champion is navigating it. Action: Ask "What has changed internally since we last spoke?" rather than "Are you still interested?" The second question produces social-desirability answers; the first produces information. 3. The champion was never positioned to advance the deal and has been hoping the situation resolves. Action: Ask directly whether the champion has a clear path to the economic buyer. If not, offer to help: "Would it be useful if I put together a one-pager you could share with your VP directly?" or "Is there someone more senior I should be talking to so I'm not putting all of this on you?" Both reframe the conversation productively.
3Why should you engage procurement and legal as early as possible in an enterprise deal, even if the business case is not yet closed?›
Because procurement and legal operate on their own timelines that are independent of your sales timeline. A company whose procurement team processes new vendors on a 90-day cycle will take 90 days regardless of when you submit the paperwork — and that clock starts when you engage, not when you close the business case. If you engage procurement after the business case is closed, you have added 90 days (or whatever their cycle is) to a deal that was otherwise done. Additionally, early procurement engagement surfaces requirements — data processing agreements, insurance minimums, approved vendor list criteria, required contract terms — that can require changes to your standard contract or your data infrastructure. Discovering these requirements after the business case is closed is both more stressful and more likely to cause the deal to collapse under time pressure. The correct approach: engage procurement as soon as you have a qualified opportunity, if only to ask "what is your process and what do you need from us to begin it?"
4What is the difference between a champion's enthusiasm and their organizational influence, and why does conflating them lead to bad outcomes?›
Enthusiasm is a measure of how much the champion wants your product to win. Organizational influence is a measure of their actual ability to make that happen — which is a function of their seniority, their relationships with budget holders, their track record of initiating similar purchases, and the political capital they have to spend on an internal advocacy campaign. A quality engineer hired 10 months ago may be your most enthusiastic champion and have influence near zero. An operations director who has been lukewarm in your calls but who has run three successful capital deployments in the past four years and has a standing weekly with the COO is the person whose support actually moves budget. Conflating them leads to two bad outcomes: spending enormous energy developing and servicing a champion who cannot win the internal fight (because you mistake their engagement for capability), and underinvesting in harder-to-develop but more powerful stakeholders because they are less immediately rewarding to interact with. Assess influence explicitly — ask your champion directly about their budget history, their relationship with the economic buyer, and how similar purchases have moved in the past.