How do I handle a buying committee where two stakeholders disagree?

Identifying the Economic Buyer and Dissenter Archetypes

Before any tactical move, classify the conflict by identifying the economic buyer and the specific archetype of disagreement. The economic buyer controls the budget line and signs the order form — they are your ultimate alignment target. Bridge Group's 2024 SaaS Sales Benchmark shows the median enterprise SaaS deal now involves 6.8 buying-committee members, up from 5.4 in 2019, making disagreement the default rather than the exception. Gong's 2024 deal-intelligence research, based on analysis of over 1 million B2B sales conversations, found that deals with unaddressed objections from a single dissenting stakeholder close at only 23% the rate of deals where every committee voice is explicitly addressed in writing. The five primary archetypes include: Economic Buyer vs. End User (CFO loves ROI, users say "too complex"), Business vs. IT/Security (VP Sales wants speed, CISO wants SOC 2 review), Two Peer Stakeholders (VP Sales wants pipeline tooling, VP Ops wants reporting), Champion vs. Skeptic (champion sold internally but skeptic blocks at finance review), and Incumbent Bias (one stakeholder defends the legacy tool due to sunk cost and relationship). Each archetype demands a different first move and micro-script. For the Economic Buyer vs. End User scenario, reframe complexity as an onboarding plan with a named CSM and ramp timeline. For Business vs. IT/Security, pre-empt with a security packet including SOC 2 Type II and pen-test summary. For Two Peer Stakeholders, find the shared metric both teams roll up to. For Champion vs. Skeptic, have the champion walk the ROI model one-on-one with the skeptic. For Incumbent Bias, acknowledge what the incumbent solved well, then show where the buyer has grown past it.

Reframing the Same Solution in Each Stakeholder's Success Metric

The most effective technique for resolving committee disagreement is to present the identical solution through two different lenses, each framed in the stakeholder's own success metric. When a user says "this is too complex," your response to the buyer should not defend the user's concern but rather reframe: "The user team has a 2-week ramp window; our CSM completes onboarding in 3 days with a 94% week-2 adoption rate. Here is the timeline and the named CSM." Same product, two framings, two wins. Salesforce's 10-K calls this "value engineering" and discloses it as a named go-to-market function. This approach works because it never forces either stakeholder to lose face — each hears their own language and sees their own priority addressed. When the CTO wants horizontal scalability and the CFO wants cost predictability, the shared win is a tiered usage pricing model that caps overage at 110% of contracted volume. The CTO sees architecture grow without re-provisioning; the CFO sees a hard budget ceiling on the purchase order. Carta's 2024 SaaS Pricing Report shows usage-based contracts with explicit overage caps close 31% faster than pure-seat contracts in committees with both finance and engineering signers. The key discipline is to never re-litigate the disagreement in a group meeting — pulling dissenters aside in one-on-one calls within 48 hours allows you to ask directly: "What would have to be true for you to be comfortable signing?" Address that specific concern in writing before the next group call, usually as a one-page brief sent to the entire committee. Never reveal that someone disagreed, as this undermines both your champion and the dissenter.

The Escalation Decision Matrix and Mutual Action Plan

Escalation is a one-shot weapon and must be used only when impasse demonstrably blocks the deal. The escalation decision matrix requires picking the row that matches reality, not the row you wish were true. When two C-suite executives disagree and both are engaged, escalate to their mutual boss (CEO or COO). When one C-suite executive has been silent for 21 or more days, do not escalate — pull the deal from forecast first. When your champion asks you to escalate, do so to the executive the champion names. When procurement adds a delay tactic, work it through the champion rather than escalating. When a security objection remains unresolved, send the security packet and schedule a direct CISO call. The escalation script should be: "We have broad support but one open item is blocking the timeline. Could we get a 15-minute sync with [mutual boss] this week to confirm priority? I'll send a one-page brief in advance." Before any C-suite escalation, read public DEF14A proxy statements — Snowflake's 2024 DEF14A, for example, reveals which executives report to which board committee, which is the real org chart for purchase authority above $1 million. The Mutual Action Plan (MAP) is the single most important document for locking alignment. After every committee call, send a written MAP listing every stakeholder, their concern, the agreed resolution, and the owner. SaaStr's deal-velocity research shows MAPs cut average enterprise sales cycles by 19%. Each dissenter must get a concrete, named win written into the MAP — for example, "Reduce onboarding time by 20% within 90 days" or "Achieve first-month ROI report to share with the board." This gives them a tangible outcome to champion internally. Never treat verbal alignment as commitment without converting it to a written MAP and a procurement intake within five business days.

Worked Example: CFO versus CRO Split on a $480K ARR Deal

Consider a $480K ARR, three-year term ($1.44M TCV) with a nine-person committee where the CRO wants the platform live by Q3 to hit a board-promised pipeline target and the CFO wants to defer to Q4 for budget reasons. This is a Two Peer C-Suite Stakeholders archetype with value asymmetry — the CRO is measured on pipeline, the CFO is measured on cash conversion. The shared win is a Q3 go-live with a deferred-billing schedule: 10% paid in Q3, 45% in Q4, and 45% in Q1. The CRO gets the timeline; the CFO gets the cash profile. Same TCV, same logo, faster start. The tactical execution requires a 30-minute one-on-one with the CFO before the next group call, pre-sharing the deferred-billing schedule and a one-page memo so the CFO walks into the group meeting already aligned. The MAP should be seven lines, every stakeholder named with owner and date attached. The generalizable pattern is that when two peers disagree on timing or cash, never renegotiate price — reshape the billing schedule. Same total contract value, different cash curve, both stakeholders win. This approach works because it preserves the deal economics while solving the structural disagreement. Discounting to buy peace trains the committee to disagree harder at next renewal, and net retention compounds against you. Reframing the deal structure — deferred billing, tiered usage caps, phased rollout — preserves total contract value while solving the disagreement cleanly.

CRM Triggers and the Five-Day Reset Protocol

Configure three CRM triggers today to catch committee disagreement before it kills the deal. First, a 21-day stakeholder silence trigger that auto-flags the opportunity and requires manager review before it stays in commit — Pavilion's 2024 GTM Compensation & Productivity Report shows reps who pull at 21 days beat plan 1.7 times more often. Second, a champion-meeting cadence trigger that fires if your champion has not met with the dissenter inside 14 days — if your champion cannot get a 30-minute meeting with the dissenter inside their own company, your champion is not powerful and you have a coach, not a champion. Third, a MAP age trigger that fires at 10 days without dissenter sign-off — escalate to your manager, not the customer. Additionally, treat any verbal yes as worthless if a procurement intake has not been opened by Day 30, regardless of committee enthusiasm. When the committee is fully stuck and the deal is otherwise alive, run a five-business-day reset. On Day 1, send a written one-page "deal status" email to the champion only, listing every stakeholder, their stated concern, and the proposed resolution. Ask the champion: "Is this accurate? Anything missing?" On Day 2, the champion confirms or corrects and you revise. On Day 3, the champion forwards the revised one-pager to the full committee with a three-question survey: (1) Is your concern listed accurately? (2) Does the proposed resolution work? (3) What blocks your sign-off? On Day 4, aggregate the responses — if you get 80% or higher engagement, you have a deal you can close; if you get below 50%, you have a deal that has already silently died. On Day 5, either book the close call or pull the deal from forecast and tell your manager cleanly with the survey data attached. Forecast hygiene over hope.

When to Walk and the Bear Case

Knowing when to walk is as important as knowing how to align. Walk when the disagreement is value-based rather than business-logic-based — for example, "we don't trust AI vendors" cannot be resolved with a SOC 2 Type II report. Walk when one stakeholder has implementation veto but will not engage, such as IT refusing meetings but possessing the ability to block rollout. Walk when the deal timeline expires waiting for alignment and your forecast hygiene depends on calling it. The bear case reveals that most reps lose committee deals by doing exactly what feels collaborative. First, you triangulate but the dissenter is not actually the blocker — RepVue's 2024 enterprise quota-attainment data shows 41% of "lost to internal disagreement" deals were actually lost to a silent CFO who never spoke in meetings, meaning you spent six weeks reframing for a VP Ops who could not sign anyway. The dissenter who talks the most is rarely the one with veto. Second, your champion is selling internally and losing — if your champion cannot get a 30-minute meeting with the dissenter inside their own company, you have a coach, not a champion. Third, you are being slow-rolled, not deliberated — a buying committee that will not meet for three weeks is not disagreeing; they have already chosen a competitor or the status quo and are letting you down easy. Fourth, you escalated and got the meeting but lost the relationship — escalating to a mutual boss is a one-shot weapon, and if you misuse it, your champion is humiliated and the dissenter becomes an active enemy. BVP's 2026 State of the Cloud notes that the median public SaaS company's net retention drops 8 points when post-sale relationships start with a forced executive escalation. The deal you save in Q2 you lose in Q6. Fifth, compensation benchmarks lie about your leverage — Levels.fyi enterprise AE data shows the top decile of enterprise reps walk away from 28% of qualified deals while the bottom decile walks from only 4%. If you cannot walk, you cannot negotiate alignment; you can only beg for it. Sixth, you confused consensus with commitment — a committee saying "yes" in the room and "no" in the contract is the textbook failure mode. Get the verbal alignment converted to written sign-off within five business days or treat the verbal yes as worthless. Seventh, you assumed the org chart from LinkedIn — public DEF14A filings show that executives with real signing authority on enterprise software purchases above $1 million frequently sit on the Audit or Risk committee, not the function you would guess. Eighth, you discounted to buy peace — reframing the deal structure preserves total contract value while solving the disagreement, whereas discounting trains the committee to disagree harder at next renewal and net retention compounds against you. The uncomfortable truth is that a divided committee is usually telling you the deal is not real yet. Your job is to either make it real this quarter or move on.

Related questions

How do I identify the economic buyer without offending other stakeholders?

Ask directly about budget authority in a one-on-one conversation, framing it as a need to understand the approval process. Most executives will volunteer who holds the final say.

What if the two disagreeing stakeholders are both powerful and entrenched?

Focus on finding a shared business outcome both can claim as a win, then document it in the Mutual Action Plan. Escalate only to a mutual boss they already report to when impasse blocks progress.

How do I write a concrete win for a dissenter in the MAP?

Ask each stakeholder what success looks like for them personally, then phrase it as a specific milestone or metric in the plan, such as "Reduce onboarding time by 20% within 90 days."

When should I escalate a disagreement to a higher authority?

Only escalate when the impasse has clearly stalled the deal for more than a week or two and after you have tried multiple alignment strategies. Escalate to a mutual boss the dissenters already report to.

Can I ever pick a side between two stakeholders?

No, never pick sides in the room. Doing so alienates the other stakeholder and risks losing the deal. Act as a neutral facilitator ensuring each person's concerns are heard and addressed in the MAP.

FAQ

How do I identify the economic buyer without offending other stakeholders? Ask directly about budget authority in a one-on-one conversation, framing it as a need to understand the approval process. Most executives will volunteer who holds the final say. Avoid making assumptions based on titles, as the economic buyer is often a senior leader outside the immediate team.

What if the two disagreeing stakeholders are both powerful and entrenched? Focus on finding a shared business outcome that both can claim as a win, then document it in the Mutual Action Plan. Avoid mediating their conflict directly; instead, facilitate a conversation around measurable goals. If they still cannot align, escalate only to a mutual boss they already report to, and only when the impasse is blocking progress.

How do I write a concrete win for a dissenter in the MAP? Ask each stakeholder what success looks like for them personally, then phrase it as a specific milestone or metric in the plan. For example, "Reduce onboarding time by 20% within 90 days" or "Achieve first-month ROI report to share with the board." This gives them a tangible outcome to champion.

When should I escalate a disagreement to a higher authority? Only escalate when the impasse has clearly stalled the deal for more than a week or two, and after you have tried multiple alignment strategies. Escalate to a mutual boss the dissenters already report to, not a random executive. Premature escalation can damage trust, so reserve it for genuine roadblocks.

How common is disagreement in buying committees today? Very common. The median enterprise SaaS deal now involves around 6 to 7 buying-committee members, up from about 5 in recent years. Disagreement is the default, not the exception, so expect it and plan for it rather than trying to avoid it.

Can I ever pick a side between two stakeholders? No, never pick sides in the room. Doing so alienates the other stakeholder and risks losing the deal. Instead, act as a neutral facilitator, ensuring each person's concerns are heard and addressed in the MAP. Your role is to guide the group toward consensus, not to choose winners.

Sources

• https://www.bridgegroupinc.com/blog/sales-development-report
• https://www.gong.io/resources/
• https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001108524&type=10-K
• https://carta.com/blog/saas-pricing/
• https://www.saastr.com/
• https://www.joinpavilion.com/compensation-report
• https://www.repvue.com/
• https://www.bvp.com/atlas/state-of-the-cloud-2026
• https://www.levels.fyi/
• https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001640147&type=DEF+14A

Related on PULSE

• [Should I Hire a Fractional CRO If My Two Co-Founders Disagree on GTM Strategy?](/knowledge/q15914)
• [How Do I Dispute a CAM True-Up Bill I Disagree With?](/knowledge/q13832)
• [What's the founder's role in setting the actual discount-policy numbers vs delegating to the CRO — and what happens when the CRO and founder disagree on risk tolerance?](/knowledge/q9527)
• [How Should RevOps Measure AI Tool Adoption Rates Across Disjointed Buying Committee Stakeholders?](/knowledge/q16251)
• [How does a buying committee of 18 stakeholders in 2027 align on purchase decisions when AI-generated product demos replace human-led presentations?](/knowledge/q13563)
• [What are the top RevOps metrics for tracking buying committee engagement across a 12-month enterprise sales cycle?](/knowledge/q103)