Latest / The Acquisition Talk with Fexingo: Mergers, Buyouts, and Business Sales for Operators / The Indemnification Basket Trap That Cost a Seller 12 Million
Transcript
- Lucas: We've spent a lot of episodes on the big, splashy M&A traps — the kind that kill a deal or leave a seller holding a massive bill years later. But today I want to talk about a clause so routine that most sellers barely give it a second look. Luna: The indemnification basket. Everyone's seen it. Everyone thinks they understand it. Lucas: Exactly. And that's exactly where it bites you. There's a software company — let's call them DataVault — that got acquired by a larger enterprise software firm back in 2024. The seller was a family office that had built the company from scratch. Purchase price: $75 million. Indemnification cap: 15 percent of purchase price, about $11.25 million. Luna: Standard stuff so far. What was the basket? Lucas: The buyer proposed a $500,000 basket. The seller's lawyer flagged it, said 'standard threshold, no problem.' But the seller's team — and I want to be clear, this was a sophisticated family office — they assumed that meant the first half million was on the buyer. That's how an 'excess' basket works. You pay losses above the threshold, and the buyer eats the first chunk. Luna: But that's not what the contract said, is it? Lucas: It said the opposite. The clause specified a 'deductible' basket — meaning the seller indemnifies from dollar one once the total hits half a million. In legal terms, it's a 'tipping' basket. The first $500,000 is borne by the buyer, but after that, all losses — including that first half million — shift to the seller. The seller never noticed the difference. Luna: And that cost them $12 million? How? Lucas: Post-closing, the buyer found a set of revenue recognition issues — about $8 million in overstated recurring revenue. Plus a data privacy claim that cost another $4 million. Total losses: $12 million. Under an excess basket, the seller would have paid $11.5 million. Under the tipping basket, they paid the full $12 million. The extra half million stung, but the real cost was the $500,000 they thought was safe. Luna: So it's not just about the number — it's the structure of the basket. And that change alone cost them half a million they never expected to pay. Lucas: Right. And it gets worse. The buyer's claim exceeded the cap, so the seller paid the full cap: $11.25 million. But because the basket tipped, they also had to eat the first $500,000 — total $11.75 million. That's $500,000 more than they would have paid if they'd negotiated an excess basket. And for a family office, half a million is not nothing. Luna: It's amazing how many sellers don't catch this. And honestly, it's a reminder that even routine legalese deserves a close read. You know, a listener recently told me that our episode on the non-compete trap saved them from signing a ten-year restriction. That kind of thing keeps me going. Lucas: That's exactly the kind of impact we hear about. If these episodes have given you an edge in your own deal-making, a couple of dollars a month at buy me a coffee dot com slash fexingo keeps it going. It's how we stay ad-free and focused on the specific, actionable stuff. Luna: Yeah. And we're back to the basket. So what should a seller look for in that clause? Lucas: Three things. First, the basket type: the contract should say 'excess' or 'deductible' — and you want excess. Some contracts use ambiguous language like 'the buyer shall bear the first $X of losses,' which sounds like excess but might be interpreted as tipping if you read the definitions. Luna: So actually read the definition of 'Losses' and 'Basket.' Don't just rely on the heading. Lucas: Exactly. Second, the calculation mechanism. Some baskets are applied on a per-claim basis; others are aggregated. A per-claim basket means each individual claim has to exceed the threshold before you indemnify. That's usually better for the seller because smaller claims fall through. The DataVault basket was aggregated — all claims added together, so even small ones counted toward the tipping point. Luna: So they hit $500,000 faster. And once they tipped, every penny counted. Lucas: Right. Third, and this is the one nobody talks about: the 'net loss' versus 'gross loss' basis. Some baskets exclude insurance recoveries or third-party indemnities. If the buyer gets reimbursed by their cyber insurance for part of the data privacy claim, does that reduce the losses that count toward the basket? In the DataVault case, the buyer's cyber policy covered $2 million of the $4 million claim. But the contract defined losses as 'gross losses' — so the $4 million counted toward the basket and the tip, even though the buyer only actually lost $2 million. Luna: That's brutal. The seller essentially overpaid by $2 million because of a definition. Lucas: And that's the real trap. The basket is a small clause — maybe three paragraphs in a hundred-page agreement. But it can shift millions. The family office learned that the hard way. They tried to negotiate post-close, but the contract language was clear. Luna: So what's the lesson for our listeners? If you're selling, what's the one thing you should do? Lucas: Bring a checklist. Or better yet, have your lawyer model the indemnification under two scenarios: an excess basket and a tipping basket, using your best estimate of potential claims. If the difference is more than a rounding error, fight for the excess. And never assume 'standard' means 'safe.' Luna: Or at least make sure you know which standard you're dealing with. Lucas: Exactly. The M&A process is full of these small print traps. The indemnification basket is one of the most common — and one of the most misunderstood. Don't let a few lines of text cost you half a million. Luna: Alright, next episode we'll talk about another hidden clause: the 'materiality scrape' and how it can wipe out your protections. Thanks for listening. Lucas: We'll see you then.