I have been inside three acquisitions at Salesforce. Different teams, different decades, different products, across the Marketing Cloud, Quip, and Slack-era waves. The autopsy reads the same every time. If you have ever watched a sharp acquired team go quiet eighteen months after the deal closed and wondered what happened, here is the pattern, and it is more predictable than anyone in corp dev wants to admit.
Step one: the constraint disappears
A startup is fast for reasons people misremember. We tell ourselves it is the talent, the passion, the mission. The underrated engine is the constraint. A startup has too little money, too few people, and not enough time, and that scarcity forces brutal prioritization. You cannot build the wrong thing for six months because you will be dead in four. The day the acquisition closes, the parent removes the constraint. Suddenly there is budget, bodies, and effectively infinite runway. This feels like a gift. It is the first cut, because without the constraint the ruthless prioritization that made the team fast loses its reason to exist. Nobody decides to slow down. The forcing function just quietly switches off.
Step two: the parent's process moves in
Now the team inherits the parent's operating system: reviews, planning cycles, security and legal and brand gates, cross-functional alignment, a quarterly cadence built to coordinate thousands of people. Each individual piece is defensible. But the aggregate is a system designed for a ten-thousand-person organization, and you just dropped a forty-person team into it. The team that used to decide and ship in a week now waits three weeks for alignment, two for review, a planning cycle to even get on the roadmap. The loop that made them fast was short, on a timescale of days. The parent's process stretches it to quarters. Same people, same talent, a loop that is now ten times longer, and output is a function of loop length.
Step three: it stops shipping
Constraint gone, process inherited, the third step is automatic. What confuses leadership is that by every visible measure things look fine. The team is staffed, the people are still talented, they are busy, in meetings, producing documents, attending reviews. High activity, low output is the signature of a team that has lost its loop. Nothing happened to the team. Something happened to the system it lived in. Velocity was never a property of the people alone. It was people plus a short loop plus a hard constraint plus the authority to decide, and integration broke all three.
What the parents who get it right do, and the AI version
This is preventable. The acquirers who prevent it treat velocity as the asset they paid for. They keep the team small enough that it still has to make hard tradeoffs, give it a clear outcome to own, and assign a senior sponsor whose actual job is to stand between the forty-person team and the ten-thousand-person operating system and take the process tax personally. The parent's instinct is to integrate, standardize, and support. The right move is often to isolate, protect, and constrain, because the resources were never the asset. The loop was.
AI-native acquisitions will fail the same way, sharper than ever. When build capacity is no longer the bottleneck, the bottleneck becomes approval latency. A team that can go from customer outcome to shipped prototype in a day is fast because nothing sits between the decision and the build. Drop it into a heavyweight review process and the AI advantage evaporates, because you reintroduced the only bottleneck AI removed. If you are about to acquire a team, name the team's loop before you touch anything else, and for every piece of parent process you apply, ask one question: does this lengthen the loop? Defend the loop like it is the asset, because it is.