The Diplomatic Veto: How to Kill a Lock-In Deal Without Creating Enemies

The “Standardization” Trap

The boardroom was air-conditioned and tense. The Global Account Manager stood at the front, proposing a “Strategic Partnership.”

“If the Municipality consolidates all 14 agencies onto our Single Platform,” he said, “you will achieve ‘Synergy.’ You will have one dashboard. One contract. One throat to choke.”

The City Manager nodded. “It sounds efficient, Sven. Why are you hesitating?”

I did not say “I hate this vendor.” I did not say “Their software is bloated.” Those are opinions. Opinions can be argued.

Instead, I adjusted my glasses and spoke with the weight of the institution. “The Municipality welcomes efficiency,” I said. “However, this proposal consolidates 100% of our critical infrastructure into a single jurisdiction. It violates our Strategic Autonomy Framework.”

The room went quiet. I had not rejected the software; I had cited the law of the land.

The Dependency: Monopoly Disguised as Harmony

Vendors use the word “Standardization” to mask Dependency. They want to create a monoculture where every department relies on their proprietary code.

Once we standardize on a single foreign platform:

1. We lose leverage: We cannot threaten to leave, because leaving is too hard.
2. We import risk: A single outage brings down the entire city, not just one department.
3. We stifle innovation: Local, sovereign vendors cannot compete with the behemoth.

This is not a technical architecture; it is a colonial administration.

The Sovereign Choice: The Three Kill-Switch Questions

To stop these deals without looking like a luddite, I use the Diplomatic Veto. I ask three questions that I know the vendor cannot answer, but which sound entirely reasonable to the Board.

1. The Jurisdiction Question:

“Can you guarantee contractually that no court outside of the EU/EEA can compel access to this data? If not, we cannot consolidate our sensitive social files here.” (They cannot. The deal stalls.)

2. The Exit Question:

“Since this is a 10-year commitment, we need a ‘Pre-paid Exit’ clause. Will you commit to converting all data to Open Standards (SQL/JSON) at your cost if we terminate?” (They want to charge us for the exit. The Board frowns at the hidden cost.)

3. The Continuity Question:

“If your cloud goes dark due to a geopolitical event, does the software function offline?” (It does not. The deal is framed as a resilience risk.)

By the end of the meeting, I have not killed the deal. The vendor has killed it with their own inadequacy. I simply held up the mirror of sovereignty, and the vampire could not see its reflection.

FAQs

What if the vendor offers a huge discount to standardize?

A discount on a monopoly is temporary. Once the competition is eliminated, the price will rise. We do not sell the future for a quarterly discount.

Does this veto work on non-technical leadership?

Yes, because you frame it as 'Legal Risk' and 'Fiscal Prudence,' which are languages they speak fluently.

What if the vendor agrees to all criteria?

Then they are a partner worth keeping. The Veto is also a filter for quality.