How do you discover and map the "power dynamic" before it kills your deal?

How do you discover and map the "power dynamic" before it kills your deal?

Power dynamic is who wins an internal disagreement when stakeholders conflict. One buyer wants ROI; another wants feature parity. One wants to move fast; another demands 6-week security audit. If you don't know the power order, you'll pitch to the wrong person and lose to internal misalignment.

The Four Power Dynamics (Types)

How to Uncover Power Dynamic (Diagnostic Questions)

Don't ask: "Who has power?" (Prospect won't answer directly.) Instead, ask about past conflicts:

1. Test scenario question: *"If your team wanted to move fast but IT wanted 3 weeks for security review, who wins that debate?"*

• If prospect says "IT always wins," = Technical buyer has veto power (matrix/distributed).
• If prospect says "My boss overrides IT," = Autocratic (one exec wins).
• If prospect says "We compromise," = Democratic (slow, consensus-driven).

1. Anchor in past decision: *"Walk me through the last vendor change in this space. How long from pitch to signature? Who caused the delays?"*

• If "Legal always drags it out," = Legal has veto power.
• If "Finance ran an RFP process," = Finance is gate-keeper.
• If "It went fast, everyone agreed quickly," = Minimal governance (faster deal).

1. Escalation question: *"If the three of you disagreed on whether to move forward, who'd make the final call?"*

• Name reveals the true Economic Buyer (may not be the CFO; might be COO or CEO if they override CFO).

Apply Power Dynamic to Your Strategy

If Financial Gatekeeper Wins (Centralized):

• Demo for them on ROI metrics first (payback period, cost per use).
• Address their objections (price, budget) before you pitch to others.
• Have them vouch for fit to their team. Their blessing = quick approvals.

If Technical Buyer Has Veto (Matrix):

• Get IT on discovery call early. Don't wait until proof phase.
• Document integration timeline + security requirements in writing.
• Schedule a tech deep-dive with IT before you demo to end-users (they'll veto if not comfortable).

If Autocratic Decision-Maker Exists (Autocracy):

• Find them in discovery. Ask: *"When your VP of Sales makes a call, does the team fall in line?"*
• Build relationship with autocrat first. If they're sold, other objections won't kill deal.
• Frame your story in their language (e.g., VP Sales cares about quota impact, not feature depth).

If Democratic / Consensus (Distributed):

• Expect long cycle (120+ days). Budget gate, plus technical gate, plus user adoption gate = 3 separate votes.
• Build multiple value stories: ROI for Finance, ease for Users, integration for IT.
• Each stakeholder must individually see win. No "trust me" shortcuts.

Pavilion's Power Dynamic Research

Pavilion's 2024 deal analysis found:

• Centralized power (Finance dominates): 68-day average cycle, 62% win rate (clear path; Finance says yes, done).
• Democratic power (consensus): 109-day average cycle, 47% win rate (slow; any stakeholder can delay).
• Autocratic power (one exec): 54-day average cycle, 71% win rate (fast; if autocrat says yes, others follow quickly).
• Matrix/distributed power: 94-day average cycle, 51% win rate (moderate speed; each gate different, sometimes contradicts).

Lesson: Autocratic orgs close fastest and have highest win rates. Consensus orgs close slowest and lose most deals (to inertia). Knowing power dynamic in week 1 lets you set realistic timeline expectations and avoid deals destined to stall.

Operator Move: Power Map Exercise

After every discovery, create a 1-page power map:

Fill this out, and you'll know who to sell to first and where deal bottlenecks will happen.

TAGS: power-dynamic,decision-committee,stakeholder-influence,pavilion,autocratic,consensus-based,deal-velocity