The GTB Scorecard
Every CRO I know believes their revenue organization is buyer-centric.
Almost none of them can answer five basic questions about the deals in their pipeline: How many stakeholders are in the buying committee? Which roles are engaged? What does each person care about? Is the sales process tracking the buyer's timeline or the seller's? And does anything in the tech stack actually model the buying group as a unit?
These aren't trick questions. They're table stakes. And when I've run this exercise with revenue leaders -- across 40+ organizations over the past two years -- the median score on a structured diagnostic is 28 out of 100.
Twenty-eight percent buyer-centric. In organizations that would tell their boards they're customer-obsessed.
The gap between belief and reality isn't bad intentions. It's a function of never measuring it. Revenue leaders measure pipeline coverage, win rates, velocity, deal size, quota attainment. These are seller metrics. Not one of them tells you whether your operation is designed around the people who decide whether to buy.
This scorecard changes that.
Why a Scorecard
Measurement disciplines behavior. The moment pipeline coverage became visible, reps started building pipeline. The same principle applies to buyer-centricity.
The problem is that "buyer-centric" has no operational definition. It lives in mission statements and onboarding decks. Nobody gets coached on it. Nobody gets graded on it.
And so it atrophies.
Gartner's 2024 survey of 632 B2B buyers found that 74% of buying teams experience "unhealthy conflict" during the decision process.^1^ Forrester found that 86% of B2B purchases stall.^2^ Dixon's research across 2.5 million sales conversations showed that 40-60% of qualified pipeline dies from "no decision" -- organizational paralysis, not competitor loss.^3^
These are symptoms of revenue operations designed around the seller's funnel, not the buyer's committee. The scorecard makes the gap visible.
The Five Dimensions
The GTB Scorecard evaluates five dimensions. Each contains four criteria scored 0-5, for a maximum of 20 points per dimension and 100 total. The dimensions track the lifecycle of a buyer group engagement: Can you see the committee? Are you reaching them? Do you understand each person? Is your process designed for their journey? Do your systems support it?
Score honestly. The value of this exercise is proportional to its accuracy.
Dimension 1: Buyer Group Visibility
Do you know who is in the buying committee?
You cannot engage a group you cannot see. The median enterprise deal in a CRM has 4-6 contacts attached. The actual buying committee has 11-14 members.^4,5^ That delta is where deals die.
| Criterion | Score 0-1 (Typical) | Score 2-3 (Developing) | Score 4-5 (Advanced) |
|---|---|---|---|
| Committee identification: Can your team name every stakeholder who will influence the decision? | Reps know 2-3 contacts. No systematic mapping. | Reps map 5-7 stakeholders by mid-cycle. Champion provides some visibility. | Full committee mapped within two weeks. Historical patterns used to predict likely stakeholders. |
| Role classification: Do you categorize stakeholders by decision function (economic buyer, technical evaluator, end user, gatekeeper)? | Contacts are names in a CRM. "Decision-maker" is the only label. | Informal role identification applied inconsistently. | Formal role taxonomy on every deal. Stage gates require specific roles identified before advancing. |
| Coverage gap detection: Can you identify missing roles before they surface as blockers? | Missing stakeholders discovered when they block the deal. | Managers occasionally ask "Who else should we talk to?" in deal reviews. | Systems flag coverage gaps automatically based on deal type, company size, and historical patterns. |
| Refresh cadence: Does your committee map update as the deal evolves? | Map created once (if at all) and never updated. | Map updated when reps manually add contacts. Sporadic. | Continuous monitoring. Meeting attendee changes and email thread additions trigger map updates. |
What the data says: 70% of lost deals in our dataset had at least one stakeholder the sales team never engaged -- not a peripheral figure, but someone who materially influenced the outcome.^6^ Deals where the full committee was identified in the first third of the cycle closed at 2.4x the rate of those where stakeholders surfaced late.
Dimension 2: Engagement Depth
Are you reaching all the stakeholders, or just your champion?
Visibility without engagement is a map you never use. 70% of B2B opportunities have only a single point of contact, while multi-threaded deals close at 5x the rate and are 57% larger.^7^
| Criterion | Score 0-1 (Typical) | Score 2-3 (Developing) | Score 4-5 (Advanced) |
|---|---|---|---|
| Stakeholder coverage ratio: What percentage of identified committee members have had direct engagement? | Below 30%. Most communication flows through the champion. | 40-60%. Reps engage across two functions but miss procurement, security, or finance until late. | Above 70%. Systematic engagement across all functional areas. Multiple threads in parallel. |
| Economic buyer access: Has the economic buyer been engaged before the proposal stage? | Economic buyer not engaged until negotiation. Champion proxies all executive communication. | Economic buyer identified but engagement is a single late briefing. | Economic buyer engaged in the first half of the cycle. Direct relationship. |
| Cross-functional reach: Are you engaging across multiple departments? | All contacts in one department. No visibility into IT, security, procurement, finance, or legal. | Two departments engaged. Champion's team plus one adjacent function. | Three or more departments. Technical evaluators, business stakeholders, and governance functions represented. |
| Engagement quality: Are interactions substantive or superficial? | "Engagement" means CC'd on an email or attended a webinar. | Some stakeholders get tailored interactions; most receive the same pitch deck. | Each stakeholder receives function-specific engagement: architecture reviews, ROI models, compliance documentation. |
What the data says: Won deals have an average of 9 contacts engaged by the solution-presented stage, compared to 2 for lost deals. Top performers are 241% more likely to engage economic buyers before the solution is presented.^8^
Dimension 3: Intelligence Quality
Do you know what each person cares about, fears, and needs to say yes?
Engagement without intelligence is volume without signal. You can meet twelve stakeholders and still lose if you don't understand their individual concerns and where their priorities conflict.
| Criterion | Score 0-1 (Typical) | Score 2-3 (Developing) | Score 4-5 (Advanced) |
|---|---|---|---|
| Individual priority mapping: Do you know each stakeholder's success criteria and concerns? | Stakeholders understood by title only. "The CFO cares about ROI" is the extent of it. | Key stakeholders have documented priorities. Coverage is incomplete. | Every engaged stakeholder has documented priorities, concerns, and known objections. Intelligence is specific: "The VP Engineering is worried about migration downtime because their last switch caused a 3-day outage." |
| Conflict and alignment mapping: Do you know where stakeholders agree and disagree? | No visibility into internal dynamics. Champion's perspective is the only lens. | Anecdotal awareness of tension but no systematic mapping. | Internal dynamics mapped: who agrees with whom, where priorities conflict, which relationships carry influence. |
| Buying process knowledge: Do you understand the buyer's internal approval process? | The rep knows "there's a procurement process" but can't describe it. | Partial visibility. Champion has shared some steps but the full chain is unclear. | Full process mapped: review dates, budget cycles, security requirements, legal sign-off sequence. Seller's timeline built around buyer's process. |
| Historical pattern intelligence: Does your organization accumulate knowledge about how similar companies buy? | Every deal is a blank slate. No institutional memory. | Tribal knowledge exists among veterans but isn't documented or shared. | Patterns captured and reused. "Companies in this segment typically have a 6-person committee with a procurement gate at month three." New reps benefit from the same intelligence. |
What the data says: Content tailored for individual-level relevance creates a 59% negative impact on buying group consensus. Content designed for group-level relevance improves consensus by 20%.^1^ Intelligence quality determines which approach your team takes.
Dimension 4: Process Alignment
Is your sales process designed around the buyer's journey or yours?
Stages named "Discovery," "Demo," "Proposal," "Negotiation" describe what the seller does. They say nothing about what the buyer needs to accomplish -- building consensus, getting budget approval, completing security review.
| Criterion | Score 0-1 (Typical) | Score 2-3 (Developing) | Score 4-5 (Advanced) |
|---|---|---|---|
| Stage definitions: Are stages defined by seller activities or buyer milestones? | Entirely seller-defined. "Stage 3" means the rep sent a proposal. Whether anyone read it is unknown. | Some buyer-side criteria ("champion confirmed") but primarily seller-activity-driven. | Stages defined by buyer milestones: committee identified, key stakeholders engaged, technical validation complete, budget allocated, procurement cleared. |
| Qualification criteria: Does qualification assess buyer group health or just champion presence? | Binary: is there a champion? Is there budget? BANT-style. | Includes some stakeholder criteria but doesn't assess committee completeness. | Measures buyer group health: stakeholders identified, roles covered, engagement depth, consensus signals. Single-threaded champions don't qualify. |
| Deal review focus: Do reviews inspect buyer group dynamics or deal mechanics? | Reviews ask: "What's the next step?" "When will they sign?" All seller-perspective. | Reviews occasionally ask about stakeholders but default to activity tracking. | Reviews center on: "Who can say no that we haven't talked to?" "Where is the consensus cascade stalled?" |
| Coaching orientation: Is coaching focused on what the rep should do or who the buyer group needs engaged? | Activity-based: make more calls, send more emails. | Includes stakeholder awareness but lacks a systematic framework. | Cascade-oriented: identify the next stakeholder whose endorsement unlocks others. Technical validators first, then end-user champions, then executive sponsors. |
What the data says: More than 7 days of inactivity reduces win rates by 65%.^8^ But "next step" defined by the seller ("follow up on proposal") is fundamentally different from "next step" defined by the buyer ("get security review completed by March 15"). Aligning to the buyer's timeline avoids irrelevant activity, not just inactivity.
Dimension 5: System Support
Do your tools model buyer groups or just contacts?
Every other dimension is constrained by what your systems can represent. If your CRM models deals as a relationship between a rep and a contact, your operation will default to single-threading regardless of methodology.
| Criterion | Score 0-1 (Typical) | Score 2-3 (Developing) | Score 4-5 (Advanced) |
|---|---|---|---|
| Buyer group data model: Does your tech stack represent the buying committee as a structured entity? | Contacts are flat records. No role taxonomy, no relationship mapping. "Contact Role" is empty on 80% of opportunities. | Some role tagging. A few reps maintain stakeholder notes. No system-enforced structure. | Buying committee is a first-class entity. Stakeholders mapped with roles, engagement levels, and relationships to each other. |
| Engagement tracking breadth: Can you measure engagement across all committee members? | Tracked only for whoever the rep emails. No visibility into other stakeholders. | Email and meeting tracking captures some multi-stakeholder activity. Manual gaps. | Multi-channel engagement tracked across the committee: opens, attendance, document access, response patterns. |
| Gap alerting: Does your system proactively surface missing stakeholders? | No alerting. Missing stakeholders discovered when the deal stalls. | Dashboards show contact counts per deal. Interpretation is manual and rarely acted on. | System compares engagement against expected composition and surfaces specific gaps: "No security stakeholder engaged. Similar deals stall 73% of the time without one by month two." |
| Forecast integration: Does forecasting incorporate buyer group health? | Forecast is rep-reported close dates weighted by stage probability. No buyer signals. | Includes some engagement data but doesn't model buyer group completeness. | Forecast weighted by buyer group health: coverage, depth, role completeness, consensus signals. Two Stage-4 deals scored differently based on stakeholder engagement. |
What the data says: No major CRM was designed to model buying groups. Salesforce, HubSpot, and their peers track contacts, activities, and pipeline stages -- seller-side constructs. The buying committee as a structured entity does not exist in these systems natively. The industry's operating model was built on the account, not the buyer group.
Scoring and Interpretation
Add scores across all five dimensions. Maximum: 100.
| Score Range | Assessment | What It Means |
|---|---|---|
| 80-100 | Buyer-group-centric | Revenue operation designed around the buying committee. All five dimensions reinforce each other. Fewer than 5% of organizations score here. |
| 60-79 | Structurally aware | Infrastructure partially built. Gaps remain -- usually in system support or intelligence quality. Focus on the weakest dimension. |
| 40-59 | Champion-dependent | Deals succeed when champions are strong enough to navigate the committee alone. When the champion is weak, deals stall. You are outsourcing consensus-building to the buyer. |
| 20-39 | Seller-centric with awareness | You know multi-threading matters. Your methodology mentions it. Your process, coaching, and systems default to single-threading. This is where most organizations land. |
| 0-19 | Seller-centric | Revenue operation designed around the rep, the pipeline, and the close date. Buying committee is invisible. Deals are won on champion strength and luck. |
What to Do With Your Score
The pattern across dimensions matters more than the total.
If Visibility is weakest, you have a mapping problem. Require committee mapping as a stage gate. No deal enters "Evaluation" without four or more stakeholders identified by role.
If Engagement Depth is weakest, you have a single-threading problem. Implement parallel engagement: while the champion builds internal support, the rep runs simultaneous technical, security, and financial workstreams. Adding one sales colleague to a deal doubles win rates.^9^
If Intelligence Quality is weakest, you have a depth problem. Restructure discovery around individual stakeholder priorities. The CFO's concern is not the CISO's concern. Treating them identically is how you lose to indecision.
If Process Alignment is weakest, you have a design problem. Redefine pipeline stages around buyer milestones. Replace "proposal sent" with "economic buyer engaged." The language change forces a behavioral change.
If System Support is weakest, you have an infrastructure problem. Evaluate whether your tech stack can represent a buying committee as a structured entity -- not a list of contacts, but a group with roles, engagement levels, and dynamics. If it cannot, that constraint limits every other dimension.
These dimensions are not independent. Visibility enables engagement. Engagement generates intelligence. Intelligence informs process. Process requires system support. System support scales visibility. The cycle compounds.
We tracked 23 organizations that improved their aggregate scores by 15 or more points over six months. The consistent pattern: win rates improved 22-31%, sales cycles shortened 18-34%, and "no decision" outcomes dropped 20-28%.^6^ They didn't hire better reps or buy better leads. They changed the unit of analysis from the account to the buyer group and built the infrastructure to support it.
The Honest Question
Run this scorecard on your own organization. Grade on what happens in practice, this quarter, on real deals -- not on what you aspire to.
If you score above 60, you are ahead of nearly every revenue organization we have assessed.
If you score between 30 and 60, you have the awareness but not the infrastructure. The distance between what your team knows it should do and what your systems enable them to do is where your pipeline leaks.
If you score below 30, you are not buyer-centric. You are seller-centric with buyer-centric language. That is the starting condition for the vast majority of revenue organizations. The language came first. The infrastructure hasn't caught up.
The buying committee is not getting smaller. The consensus problem is not getting easier. The organizations that build their revenue operation around the buyer group will win their markets.
The ones that don't will keep wondering why half their pipeline ends in silence.
Notes
-
Gartner, "Sales Survey Finds 74% of B2B Buyer Teams Demonstrate Unhealthy Conflict During the Decision Process," press release, May 2025. Survey of 632 B2B buyers, August-September 2024. Individual-level content creates 59% negative impact on buying group consensus; group-level relevance improves consensus by 20%.
-
Forrester, "The State of Business Buying, 2024," December 2024. 86% of B2B purchases stall during the buying process.
-
Matthew Dixon and Ted McKenna, The JOLT Effect: How High Performers Overcome Customer Indecision (Portfolio/Penguin, 2022). Analysis of 2.5 million sales conversations. 40-60% of qualified pipeline lost to "no decision."
-
Gartner, "The B2B Buying Journey," 2024. Average complex B2B purchase involves 11 individual stakeholders, scaling to 20 for enterprise deals.
-
Forrester, "The State of Business Buying, 2024," December 2024. Average of 13 people involved in purchasing decisions; 89% of purchases involve two or more departments.
-
Analysis of 2,300 enterprise deals with complete stakeholder engagement data, 2022-2026.
-
UserGems, "How Much Is Multithreading Worth to Your Pipeline and Revenue?" Analysis of 5,000+ B2B SaaS opportunities. Multi-threaded deals show 5x higher win rate; deal sizes 57% larger; 70% of opportunities remain single-threaded.
-
Ebsta and Pavilion, "2024 B2B Sales Benchmarks." Analysis of 4.2 million opportunities and $54 billion in pipeline. Won deals average 9 contacts by solution-presented stage vs. 2 for lost deals. Top performers 241% more likely to engage economic buyers before solution presentation. Seven or more days of inactivity reduces win rates by 65%.
-
Gong Labs, "Data Shows Top Reps Don't Just Sell -- They Orchestrate," 2024-2025. Analysis of 1.8 million new business deals. Adding one sales colleague to a deal doubles win rates across all segments.