Latest / The Acquisition Talk with Fexingo: Mergers, Buyouts, and Business Sales for Operators / The Escrow Trap That Cost a Seller 40 Percent of Their Payout
Transcript
- Lucas: So you sell your company for twelve million dollars. You think you've done well. And then eighteen months later, you walk away with barely seven. That's the escrow trap, and it's more common than most sellers realize. Luna: I mean, escrow is standard in every deal. Usually ten percent, held for twelve to eighteen months to cover indemnification claims. How does it eat forty percent of a payout? Lucas: Same way most traps work in M&A — you sign a clause that looks like boilerplate, but the definition attached to it is a loaded weapon. In this case, a midmarket software company we'll call CloudMetrics — name changed — got acquired for twelve million by a larger strategic buyer. The escrow was twenty-five percent — three million — tied to a revenue performance target. Luna: Twenty-five percent is already aggressive. Most deals I've seen cap escrow at fifteen. But tying it to revenue — that's an earnout dressed up as an escrow. Lucas: Exactly. And the language was subtle. The escrow release condition said the company had to achieve 'earnings before interest, taxes, depreciation, and amortization consistent with the forecast provided in the disclosure schedules.' That forecast was a spreadsheet attached to the purchase agreement. But the spreadsheet had no methodology note. No definition of how EBITDA was to be calculated post-closing. Luna: So the buyer could just change the methodology? Lucas: That's exactly what happened. Eighteen months later, when the seller asked for the escrow release, the buyer's finance team had reclassified certain recurring revenue streams as non-recurring. They also started allocating a portion of shared corporate overhead to CloudMetrics — something that had never been done pre-close. Under the buyer's methodology, the company missed the EBITDA target by about two million dollars. Luna: And the contract didn't specify whose methodology would govern? Lucas: It said 'consistent with the forecast.' But the forecast was just numbers on a page. No footnote about GAAP or consistent accounting policies. The seller's lawyer argued the methodology should be the same as pre-close. The buyer said the contract didn't specify, and their application was reasonable. The dispute went to arbitration. Luna: And arbitration isn't cheap. Three million in escrow, but legal fees can eat a chunk. Lucas: Right. The seller ended up settling for sixty percent of the escrow — about one point eight million — and paid four hundred thousand in legal fees. So out of twelve million, the seller's net was seven point two. That's a forty percent effective haircut on the purchase price. Luna: And all because the escrow release condition wasn't nailed down to a clear, auditable metric. So what's the fix? Lucas: Three things. First, cap the escrow size. Anything above fifteen percent should be a red flag. Second, the release trigger must be tied to objectively verifiable financial statements — audited, or at least reviewed by a third-party CPA. Not a forecast. Not an internal spreadsheet. Luna: And third? Lucas: Mandatory release of the first tranche — at least half — immediately at closing, subject only to survival of reps, not performance. Performance-based escrow is really an earnout, and it should be negotiated separately with its own protections. Luna: So treat it like an earnout. Require clear definitions, an independent arbiter for disputes, and a cap on how much can be withheld. Lucas: Exactly. The CloudMetrics seller was a smart operator — great business, good margins. But they treated the escrow clause as boilerplate. They spent weeks negotiating the purchase price but maybe an hour on the escrow language. That hour cost them four point eight million dollars. Luna: And that's the lesson. In M&A, the money isn't in the headline number. It's in the mechanics of how that number gets paid out. Lucas: Speaking of mechanics — and I don't want this to sound like a plug — but if these kinds of deal-structure conversations have helped you think more clearly about your own negotiations, there's a way to support the show that keeps it independent and ad-free. It's a small gesture, but it genuinely helps us keep bringing these stories. Luna: Yeah, we don't run ads, and that's intentional. But it means the show relies on listeners who find value in it. If that's you, you can head to buy me a coffee dot com slash fexingo. No pressure at all. Lucas: And we mean that. Whatever you decide, we're glad you're here. So back to the escrow trap — the real takeaway is that any deferred payment tied to performance needs to be treated like a separate deal. Get a clear definition, an independent verification mechanism, and a cap on the holdback. Otherwise, you're handing the buyer a knife. Luna: A knife they might not even plan to use — but it's there, and if the relationship sours, they can. Lucas: Exactly. And in the case of CloudMetrics, the relationship didn't even sour. The buyer's finance team just applied a different interpretation. It wasn't malicious. It was ambiguous. And that ambiguity cost the seller millions. Luna: So the next time you see an escrow clause, ask yourself: who defines the metric? How is it calculated? And who decides if it's met? Lucas: If you can't answer those three questions in plain English, the deal isn't done. Thanks for listening to The Acquisition Talk with Fexingo. Luna: We'll see you next time.