The Landmine Criterion: Design One Test Only You Pass
Competitive POVs are won at criteria-design time, not execution time. Every criteria list needs one legitimate requirement that maps to your differentiated strength — and that the competitor structurally cannot meet.
Two vendors, one financial-crimes POV, identical data set. Six weeks later, both platforms clear every accuracy threshold on the criteria list. The customer's evaluation summary uses a phrase that should terrify any seller who reads it: "functionally equivalent solutions." The deal goes to procurement, procurement does what procurement does with equivalent solutions, and the contract signs at the other vendor's price — eleven percent below yours.
The seller's postmortem blamed the discount. Wrong autopsy. That deal was not lost in week six, at execution time. It was lost in week zero, at criteria-design time, when the team accepted a criteria list that both vendors could pass. A POV whose every criterion is passable by every vendor is not an evaluation. It is a price negotiation with extra steps.
Here is the discipline that prevents it: every success-criteria list your team signs must contain at least one landmine criterion — a legitimate, customer-relevant requirement that maps directly to your differentiated strength and that your competitor structurally cannot meet.
The battle is over before the kickoff call
Sellers pour their competitive energy into the wrong phase. They obsess over execution — the demo polish, the model tuning, the readout deck — and treat the criteria list as paperwork to get through so the real contest can begin. Elite sellers invert this completely. They know the criteria list is the contest. Whoever shapes it has usually already won.
Think about what a signed criteria list actually is: the customer's official, committee-endorsed definition of what matters. Once it is signed — by the champion, the EB sponsor, the technical gatekeeper — it becomes the constitution of the evaluation. Results that map to criteria are admissible; everything else is vendor noise. If your differentiation is not encoded in a criterion, then for the purposes of this evaluation, your differentiation does not exist. You can demonstrate it, present it, benchmark it — and the evaluation summary will still say "functionally equivalent," because the document that defines equivalence never asked the question you win.
Your competitor's best sellers know this, which leads to an uncomfortable corollary we'll return to: if you didn't design any of the criteria on the list you just signed, someone else designed them for you.
Anatomy of a landmine
A landmine criterion has three properties, and it needs all three. Two out of three is either a wasted criterion or a trick — and both lose.
1. It is genuinely valuable to the customer. This is the load-bearing property and the ethical line in one. The requirement must address a real risk or a real need in the customer's world — something that, eighteen months into production, they will be grateful was tested. A criterion that exists only to embarrass a competitor is a trick, and tricks fail twice: technical evaluators smell vendor-serving requirements from across the room, and the moment your landmine is exposed as a trick, you lose the asset the entire evaluation runs on — the gatekeeper's trust. The test I apply before any criterion goes on the list: if we were not in this deal, would a good consultant still tell the customer to test this? If no, cut it.
2. It maps to a differentiated strength. Not a strength — a differentiated one. "Model accuracy" is a strength; everyone credible has it, which is exactly why it produces "functionally equivalent." The raw material for a landmine lives at the intersection of two things you should already have on file: your win-loss history (why do customers who chose you say they chose you?) and your competitor's architecture (what did they bolt on that you built in?). Real examples from the field: explainability output that survives a model-risk-management review, because the regulator's clock is the customer's compelling event; retraining cadence under data drift, because the customer's alert patterns shift quarterly; in-database processing, because the customer's data cannot legally leave the country it sits in.
3. The competitor structurally cannot meet it. Structurally is the operative word. A landmine is not a criterion the competitor executes poorly — they might execute well that week. It is a criterion their architecture, their deployment model, or their operating history cannot satisfy no matter how good their SE team is. If they can close the gap with two weeks of effort, you have designed a speed bump, not a landmine. This is why landmine design is research, not brainstorming: you need to know the competitor's product the way their own SEs do. The C in MEDDPICC is not a name in a CRM field. It is this.
Placing it: through the champion, in the customer's language
You do not place a landmine by proposing it in a vendor meeting. A requirement arriving under your logo is discounted on arrival. The landmine travels through your champion, and the champion carries it because you have armed them with something better than a request: a reason.
The mechanics run through discovery, not persuasion. Somewhere in your A.X.I.O.M. loops, the customer told you about the pain your differentiation solves — the model-review process that killed the last three vendors, the audit finding, the data-residency constraint their counsel flagged. Your job is to connect that pain to a testable requirement and hand the connection to your champion in their own vocabulary: "Given what happened in the last model review, shouldn't any platform we evaluate have to produce documentation your MRM team will actually accept — as a pass/fail criterion, not a demo topic?"
Notice what that sentence is. It is not advocacy for your product. It is advocacy for the customer's own risk — which is why the champion can say it in a room you will never enter, and why the technical gatekeeper, the person most allergic to vendor games, will often become the criterion's strongest defender. The best landmine criteria get adopted because the skeptic reads them and says, "We should have been testing this all along."
And when the criterion goes on the list, it gets the full Template 5 treatment like every other row: specific and measurable, a target, a data set and method, a named customer owner, four signatures before kickoff. A landmine without a signature is a suggestion. A landmine with one is law.
You are standing in someone's minefield right now
Run the logic in reverse. If landmines win competitive POVs, your competitor's good sellers are placing them too — which means every criteria list handed to you deserves a sweep before your SE lead signs it.
The sweep is one question per criterion: whose strength does this test? Most criteria are neutral — accuracy, timeline, basic integration. But when you find a requirement that is oddly specific, arrived late, or maps suspiciously well to the incumbent's architecture, you have found their landmine. You then have three legitimate moves: reframe it (broaden a vendor-shaped requirement back into the customer-shaped problem it claims to address — "the goal here is auditability; let's define the criterion by what the audit requires, not by one implementation of it"), counterweight it (accept it, and place your own landmine on the same list — signed criteria cut both ways), or walk (a list you cannot influence at all is a verdict already rendered, and the cheapest time to lose a rigged evaluation is before it starts).
What you may not do is pretend the criterion isn't there and hope execution saves you. Week six does not rescue week zero. It never has.
Where to start Monday
- Sweep every active competitive POV's criteria list with two questions: Is there at least one criterion only we pass? Is there one that looks like it was written in our competitor's product docs? If the answers are no and yes, the evaluation is currently designed for you to lose it — renegotiate the list this week, while there is still a week to renegotiate.
- Build a landmine library per competitor. Take your top two rivals and write down, from win-loss data and their own documentation, three legitimate customer requirements each one structurally cannot meet — with the target, data set, and method pre-drafted in Template 5 format. This is an afternoon of work that your team will reuse on every competitive deal for years.
- Add one question to competitive deal reviews: "Which criterion on the signed list do we pass and the competitor doesn't — and who on the customer side owns it?" If the account team cannot answer in one sentence, the deal's competitive strategy is hope, and hope forecasts poorly.
The uncomfortable truth about competitive evaluations is that the fairest-looking phase of the deal — objective criteria, shared data, side-by-side results — is decided by whoever did the least glamorous work earliest. Design one test only you pass. Make it a test the customer genuinely needs. Get it signed before kickoff.
Then let the evaluation be exactly as objective as everyone wants it to be. You wrote the constitution.
Go deeper. The landmine criterion lives in Template 5 of the free Field Toolkit — "at least one business criterion; at least one landmine only you pass" — companion to The Value Engine: How Elite Enterprise Sales Teams Turn Buyer Pain into Forecastable Revenue by Rudy M. Celekli, where the full competitive POV is played out on one $8.9M enterprise deal. Get the book, download the template, and sweep your current criteria lists before your competitor's champion does.