What running both sides of an acquisition taught me about operations
I sold the startup I ran, then delivered the integration from inside the acquirer. The deal was the easy part. Here's what the operational reality looked like.
Most writing about acquisitions is written by people who watched one from a single seat: the founder who sold, the corp-dev person who bought, the employee it happened to. I got an unusual view: I negotiated the sale of Learnium as its CEO, then moved across with our core engineers and ran the integration from inside Learnlight as a project manager.
Here’s what that route taught me.
The deal is a document. The integration is an operation.
Signing day feels like the finish line and is actually the starting gun. Everything the deal assumes (the IP transferring cleanly, the team staying, the product slotting into the acquirer’s roadmap) is an operational task someone has to actually do, usually while both companies keep running.
I prepared our diligence pack as the seller, so I knew exactly what had been promised. Then I became the person accountable for making those promises physically true: systems integration, training workshops, roadmap alignment. If you ever get the chance to staff an integration with someone who was on the other side of the table, take it. The information asymmetry disappears.
Culture shows up in tooling first
People talk about culture clash as if it’s about values posters. In practice, the first friction is operational: how decisions get made, what a “project” even is, which tool is the source of truth. A startup runs on speed and implicit context; a global company runs on process and explicit coordination. Neither is wrong. But the integration fails if nobody translates between them, and translation is a real job, not a thing that happens by osmosis.
Retention is won in the first ninety days
Our core engineering team came across in the acquisition and stayed. That wasn’t luck. It was deliberate, unglamorous work: making sure their first projects were real, their reporting lines made sense, and the acquirer’s process didn’t land on them all at once.
What this means if you’re buying, selling, or integrating
The pattern behind every acquisition problem I saw was the same: strategy, technology, culture and delivery treated as separate workstreams when they’re one system. Somebody has to hold the whole map. That’s the job.