Finding the Hidden Veto Players in Enterprise Deals

Most enterprise deals do not die because the economic buyer said no. They die because someone the deal team never properly engaged, often in risk, compliance, security, data, or a parallel business line, raised an objection late that nobody was equipped to answer. This guide sets out how to identify those hidden veto players before they become the reason your deal slips a quarter or disappears entirely.

Start from the approval path, not the org chart

Champions give you a stakeholder map that reflects who they talk to, not who can stop the deal. In regulated buyers, particularly banks, insurers and asset managers, approval almost always routes through functions the champion does not sit with daily: second line risk, operational resilience, data protection, procurement, vendor risk, information security, model risk, financial crime, and in some cases the board risk committee or a designated SMF holder.

Ask the champion to walk you through, in order, every sign-off the contract will physically need before signature. Not who they think should be consulted. Who signs. If they cannot answer precisely, that is your first finding. The gap between what a champion thinks the process is and what it actually is, is where hidden vetoes live.

Map veto power across three dimensions

For each stakeholder surfaced by the approval path, assess three things.

First, formal authority: can they refuse sign-off, and is that refusal binding or advisory? A vendor risk team that issues a red rating usually binds procurement even if the business sponsor disagrees.

Second, informal authority: whose objection, even without a formal gate, causes the deal to pause? A respected senior engineer, a longstanding compliance officer, or a group CRO can halt momentum without ever filling in a form.

Third, precedent sensitivity: who will be asked whether this deal sets a precedent they will have to live with on the next twenty vendors? These are often the quietest voices and the most dangerous when ignored.

Test for hidden vetoes through specific signals

Several patterns reliably indicate a veto player you have not yet met.

The champion starts hedging on timeline without a clear reason. Legal redlines arrive with comments from a function you were not told was reviewing. A meeting gets rescheduled with no replacement date. A technical question appears that is clearly not from your current contacts. Someone asks for documentation you were not told would be needed, particularly on sub-processors, model governance, exit plans, or operational resilience under the relevant regulatory regime.

Each of these is a signal that a function has entered the review and formed a view before you knew they existed.

What good engagement looks like

Once identified, do not try to sell to a veto player. Their job is not to be sold to. Their job is to protect the firm. Offer direct access to the equivalent function on your side: your CISO to their CISO, your DPO to their DPO, your head of resilience to theirs. Provide the artefacts they need, SOC 2 reports, pen test summaries, DORA mapping, sub-processor lists, exit testing evidence, in the format they will actually use. Ask what would cause them to object, and treat the answer as the specification for your response.

The firms that win complex enterprise deals do this early, before procurement formally engages. The firms that lose do it in the final two weeks, under time pressure, with incomplete evidence.

The next action

Take your three largest open enterprise opportunities. For each, write down every function that will need to sign off, name the individual, and write the one sentence objection they are most likely to raise. If you cannot complete that exercise today, you have your week's work.

Frequently Asked Questions

How is a veto player different from a detractor?

A detractor dislikes the deal but cannot stop it. A veto player can stop it, whether or not they dislike it. Confusing the two leads teams to over-invest in persuasion and under-invest in evidence.

Should we ask the champion directly who could block the deal?

Yes, but phrase it around process, not politics. Ask who has to sign, what evidence they will require, and what has caused similar vendor approvals to stall in the last twelve months. Champions answer process questions honestly more often than political ones.

What if the champion resists introductions to risk or compliance functions?

That resistance is itself a finding. It usually means the champion is not confident the deal will survive those reviews, or does not have the standing to broker the introduction. Both are material to your forecast.

How early should second line functions be engaged?

As soon as the buyer has confirmed commercial intent in principle. Waiting until contract stage compresses the review into the period where slippage is most expensive and least recoverable.

Does this apply to renewals as well as new business?

Yes, and arguably more so. Renewals often fail because a risk function that was not involved at original purchase has since formed a view, and the account team is still engaging only the original champion.