Selling to Committees: Buyer vs. User in B2B
Lesson 73: Selling to Committees: Buyer vs. User in B2B
Lesson 73: Selling to Committees: Buyer vs. User in B2B
Lesson 72 introduced the Enterprise Adoption Ladder and established that Rung 3 progression requires engaging gatekeepers — central IT and security stakeholders — who were never part of a product's original grassroots adoption. This lesson names those gatekeepers explicitly and extends the picture further: in most B2B purchasing decisions of any real size, there is no single "customer" at all. There is a committee of distinct people, each with a different relationship to the product, a different definition of success, and often genuinely conflicting incentives, and a deal succeeds or fails based on whether all of them, not just the most enthusiastic one, are satisfied.
Consumer product intuition breaks down badly here. A consumer PM learns to obsess over a single user's needs, because in a consumer context the person using the product, the person paying for it, and the person deciding to buy it are almost always the same individual. In B2B, these are frequently three, four, or five different people: an end user who will interact with the product daily, a champion within the organization who is personally invested in seeing the purchase succeed, an economic buyer who controls the budget and cares primarily about return on investment, and a technical evaluator or gatekeeper — often from IT or security, echoing Lesson 72's Rung 3 concept directly — whose approval is required regardless of how enthusiastic anyone else on the committee is.
This lesson introduces the Stakeholder Compass, this lesson's core mental model, to give you a structured way to identify who actually needs to be satisfied for a B2B deal to close, and what "satisfied" concretely means for each of them.
Learning Objectives
- 1
Explain why B2B purchasing decisions typically involve multiple distinct stakeholder roles rather than a single "customer."
- 2
Apply the Stakeholder Compass to identify the champion, economic buyer, technical evaluator, and end user in a given B2B deal.
- 3
Distinguish each stakeholder role's distinct definition of success and primary concern.
- 4
Identify the risk of over-relying on a single stakeholder, particularly a champion with no budget authority, to carry a deal forward.
- 5
Evaluate a stalled B2B deal for which stakeholder role may be inadequately engaged or unsatisfied.
This lesson assumes the Enterprise Adoption Ladder and the concept of Rung 3 gatekeepers from Lesson 72, since this lesson names and elaborates those gatekeeper roles specifically as part of a broader stakeholder map relevant across the entire B2B sales and adoption process, not only at the organization-wide rollout stage.
Why B2B Purchases Involve Multiple Distinct Roles
Why B2B Purchases Involve Multiple Distinct Roles
In a consumer purchase, one person typically experiences the product, decides whether it's worth the money, and completes the transaction, all in a single, largely private decision. In a B2B purchase of meaningful size, these functions are routinely distributed across different people within the buying organization, each of whom has their own incentives, success criteria, and constraints, and none of whom can unilaterally complete the purchase alone. A product that delights the person who will use it daily can still fail to be purchased if the person controlling the budget doesn't see a clear return, or if a technical reviewer identifies a security concern the daily user has no visibility into or authority over.
The Stakeholder Compass
The Stakeholder Compass
This lesson introduces the Stakeholder Compass, mapping the four most common distinct roles in a B2B buying process:
The Champion is someone inside the buying organization, often but not always an end user themselves, who is personally invested in seeing the purchase succeed — sometimes because it solves a problem they're accountable for, sometimes because their own reputation is tied to advocating for the change. The Economic Buyer controls the budget and evaluates the purchase primarily in terms of cost, return on investment, and opportunity cost relative to other uses of the same budget — and critically, may have limited or no firsthand exposure to the product itself. The Technical Evaluator, directly connected to the Rung 3 gatekeeper concept from Lesson 72, assesses security, compliance, integration, and technical risk, and typically has veto power regardless of how compelling the product is to everyone else on the committee. The End User is the person who will actually interact with the product daily, and whose primary concern is whether it genuinely fits and improves their actual workflow.
The Stakeholder Compass's core discipline is recognizing that a deal requires, at minimum, adequate engagement across all four roles — not necessarily unanimous enthusiasm, but at least no unaddressed veto-level objection from any one of them — and that strong performance with one role does not substitute for engagement with the others.
The Champion-Without-Authority Trap
The Champion-Without-Authority Trap
A specific and extremely common B2B failure mode is over-relying on a single, genuinely enthusiastic Champion, particularly one who is also an End User, to carry a deal forward without ever directly engaging the Economic Buyer or Technical Evaluator. A Champion's enthusiasm is a genuinely valuable asset — often the reason a deal exists at all — but a Champion without formal budget authority or technical sign-off authority cannot, by themselves, complete a purchase, and treating their strong internal advocacy as equivalent to deal progress risks the sales-and-product team investing significant effort in an account that stalls the moment it needs sign-off from stakeholders who were never engaged directly.
Distinct Success Criteria by Role
Distinct Success Criteria by Role
Each stakeholder role's definition of "this product is good" differs meaningfully, and a product or sales narrative optimized for one role's success criteria may fail to resonate with, or even actively concern, another. The End User evaluates task fit and day-to-day usability. The Economic Buyer evaluates return on investment and total cost relative to alternatives, often with limited patience for feature-level detail that doesn't connect to a business outcome. The Technical Evaluator evaluates risk exposure, compliance, and integration burden, largely independent of how well the product performs its core function. The Champion, depending on their own role, may care about all of the above simultaneously, but their success is also frequently tied to their own internal credibility — meaning a Champion needs not just a good product, but a good, defensible story they can personally tell to the other stakeholders on their own behalf.
Common Mistakes to Avoid
Treating a single enthusiastic stakeholder's feedback as representative of the whole buying committee
Strong Champion or End User enthusiasm says little about whether the Economic Buyer or Technical Evaluator have been engaged or satisfied.
Assuming a Champion has more internal authority than they actually do
A Champion without budget or technical sign-off authority cannot unilaterally close a deal, however strong their advocacy.
Pitching every stakeholder with the same narrative and the same level of detail
A pitch optimized for an End User's task-fit concerns may fail to address an Economic Buyer's ROI concerns or a Technical Evaluator's risk concerns at all.
Engaging the Technical Evaluator only late in the process, after significant momentum has already built with other stakeholders
Given the veto-level authority Technical Evaluators typically hold, per Lesson 72's Rung 3 discussion, late engagement risks a costly, momentum-killing stall at exactly the point a deal seemed closest to completion.
Assuming all four roles are always occupied by different individuals
In smaller organizations, a single person may occupy multiple roles simultaneously (for example, a founder who is both Economic Buyer and Technical Evaluator), and failing to recognize this can lead to either redundant or entirely missed stakeholder engagement.
Ready to test your product judgment?
Take the interactive practice quiz for Lesson 73 and build your skill radar dashboard.