The deal was done. I know I keep starting stories that way, but this time I really believed it.
Eight-figure managed services deal, global scope, eighteen months of work. The CIO had signed off on the business case. The CFO had blessed the commercial terms. Our champion had already started planning the internal announcement. My forecast said “commit” and for once, it wasn’t optimism. It was arithmetic.
Then legal got the paper.
Three weeks of silence, and then a redline document came back that looked like it had been through a shredder. Forty-seven comments. But one of them stopped everything cold: unlimited liability for data breaches, with no cap, no carve-outs, no sunset. Our legal team took one look and said no. Their legal team said it was non-negotiable. The deal, which had been done, sat untouched for six weeks while two legal departments stared at each other across a clause neither side fully understood.
I’d spent eighteen months selling to the business. I had spent zero minutes selling to legal. That was the mistake, and it nearly cost me the biggest deal of my career.
Legal Is a Stakeholder, Not a Step
Here’s the mental error most reps make, and I made it for years: we treat legal as a step at the end of the process. Business terms first, paper last. Signatures are a formality.
They’re not. In enterprise deals, legal is a stakeholder with its own priorities, its own fears, and its own veto. And unlike your champion, legal has no emotional investment in your solution. They don’t care that the CIO loves it. They care about risk, and risk is a language most salespeople never learn to speak.
The unlimited liability clause wasn’t their lawyers being difficult. It was their lawyers doing their job. A data breach in their industry meant regulatory exposure, customer lawsuits, and board-level consequences. Their legal team was protecting the company from a scenario that kept their general counsel up at night. Once I understood that, I stopped being frustrated and started being useful.
The lesson is embarrassingly simple: if legal can kill your deal, legal belongs in your buying committee map from day one. Not week forty. Day one. Ask your champion early: “Who reviews the paper on your side, and what do they usually care about?” Then go meet those people before there’s anything to negotiate. When the redlines arrive, and they will, you’ll be a known quantity instead of a stranger asking for an exception.
The Clause You Never Discuss Is the One That Kills You
Here’s the part that still bothers me. In eighteen months, across dozens of meetings, nobody ever mentioned liability. Not the CIO, not procurement, not our champion. Everyone talked about scope, price, timelines, and service levels. The deal-breaker lived in a document nobody had read yet.
That’s normal, and that’s the trap. The terms that kill deals are almost never the ones you negotiate in the room. They’re liability caps, indemnities, data processing terms, termination rights, and audit clauses. The fine print that nobody loves and everybody skips.
I now run a simple exercise on every serious deal, usually around the midpoint: I ask both sides’ legal teams for their standard paper, early, before the business terms are even final. Not to negotiate it. Just to read it. The goal is to find the three clauses most likely to cause a fight, while there’s still time and goodwill to solve them. On that big deal, the liability clause would have surfaced in month three instead of month eighteen, when we had leverage and patience instead of a deadline and panic.
Bring the paper forward. The redlines you find early are problems. The redlines you find late are crises.
Translators Win Deals
The breakthrough on that deal didn’t come from a lawyer. It came from me, reluctantly learning to translate.
Our legal team spoke in risk exposure and precedent. Their legal team spoke in regulatory obligation and board accountability. Both sides were saying reasonable things in languages the other side couldn’t hear. So I started carrying messages in plain English. “They’re not asking for unlimited liability because they want to punish you. They’re asking because their regulator fined a competitor last year and their board is terrified.” And back the other way: “We’re not refusing because we don’t care. We’re refusing because our insurers literally won’t underwrite it, so a yes here is a promise we can’t keep.”
Once both sides understood the why behind the positions, the solution took about a week: a liability cap with a higher tier specifically for data breaches, plus joint security commitments that gave their board something real to point to. Nobody got everything. Everybody got enough.
That translation skill, business to legal and back again, has saved more of my deals than any closing technique ever will. The rep who can sit between two legal teams and make each side legible to the other is worth more than the rep with the best pitch deck. I didn’t know that before this deal. I build my whole late-stage process around it now.
The Happy Ending, With a Scar
We closed the deal. Seven weeks late, slightly smaller in scope, but closed. The CIO got his program. My champion got her announcement. And I got a permanent scar in the shape of a lesson: the deal isn’t done when the business says yes. It’s done when the paper is signed.
Now, on every deal over a certain size, I have a rule: no deal reaches “commit” in my forecast until I’ve seen the other side’s standard terms. Not the negotiated version. The standard one, with all its landmines intact. My managers thought I was being paranoid the first time I did it. Then they watched a deal survive legal in three weeks instead of three months, and paranoia became process.
The biggest deal of your career will not die in a bake-off. It will die in a clause nobody discussed, in a document nobody read, at a stage everyone assumed was a formality. Read the paper early. Meet the lawyers early. Translate constantly. The business case gets you to the table. The paper gets you paid.
What clause nearly killed your biggest deal? Tell me in the comments.





Leave a Reply