Key Takeaways
- HiddenLevers shipped code at two to three times the speed of legacy teams at Orion Advisor Solutions prior to its acquisition.
- Imposing corporate project management and tracking systems caused an acquired startup's engineering velocity to plummet by 70%.
- Bundling an acquired product as a free suite add-on turns standalone software into a loss leader, gutting revenue-tied earnouts for founders and sales reps.
- Buyers routinely purchase fast-moving engineering units for their technical edge, only to suffocate that speed by forcing legacy enterprise compliance onto them.
The Cost of Corporate Standardization
When Orion Advisor Solutions bought wealthtech platform HiddenLevers, they acquired an engineering engine operating at peak output. Founder Praveen Ghanta tracked output metrics directly: “We haven't fully integrated the team into Orion processor, but we can measure our own velocity. You know, we know where that is. Apples to apples with sort of the rest of Orion and it was somewhere between two and three times higher than the average team at Orion as of when we were acquired.”
That execution gap did not last. Rather than letting the acquired team operate autonomously or adopting their lighter engineering practices, the corporate buyer absorbed the startup into legacy bureaucracy. Corporate tracking software, extra layers of approvals, and standard enterprise workflows entered the daily routine. The outcome was swift. Ghanta recalled: “to my dismay, by the time I left, they had succeeded or perhaps shortly there after they had succeeded in dragging us down by 70%. They had succeeded in slowing the pace of innovation down.”
Packaging Shifts Destroy Earnout Math
Operational drag was only the first friction point. The second emerged in go-to-market execution. Strategic acquirers buy standalone software tools to strengthen an existing product suite, but bundling often clashes with standalone financial incentives.
At HiddenLevers, the commercial model disintegrated once the product became an add-on. “Pricing it became much more of a like okay this is part of a suite now you can just give it away for free if you want,” Ghanta explained. “And part of the problem there was that our sales team and even my co-founder still in theory had targets tied to certain revenue goals and things like that that became completely unattainable because the product was being used as a loss leader of sorts.”
When software turns into a free incentive to defend a core platform, revenue credits for the target vanish. If deal contracts tie earnout hurdles to standalone product revenue rather than total contract value or platform retention, the founders and sales staff bear the full downside of the buyer's packaging decisions.
When Control Overrides the Deal Thesis
Strategic acquirers frequently justify premium deal multiples by citing product speed and modern software architecture. Yet middle management defaults to procedural control, forcing agile units onto the same slow tracks as legacy systems. Host Kison Patel summarized the core failure point: “Fair as much as you can, but the key thing is don't destroy the company you're buying.”
Protecting velocity requires active defense against standard integration playbooks. Ghanta pointed out the missed opportunity: “I think if I were on the other side, I would look at, okay, I'm buying innovation. I'm buying kind of that kind of talent. How can I let that prosper a little bit and not drag it down to the speed of like, you know, there's times when you got to move slow, but hey, we're trying to do this for innovation reasons. How do we keep that?”
Why It Matters
This case highlights why strategic software acquisitions fail to produce post-deal platform value despite hitting early engineering milestones. When corporate buyers treat acquired software as a loss leader, standalone financial earnouts break down, driving away top technical talent. Mid-market sponsors and corporate acquirers who fail to insulate acquired product units from parent-company overhead consistently destroy the operational efficiency they paid to acquire.