The standard integration question is: how does the target operate?
The right question is: what do they have that we don’t?
These sound similar. They produce completely different integration programs.
The first question assumes you need to understand the target’s operating model before you can absorb it — their processes, their systems, their way of running things. The second assumes you already know how you’re running things, and the only thing worth studying in the target is what they bring to the table that you can’t build yourself. Capability. Market position. Customer base. IP. The reason you bought them.
The operational integration is already solved before you close. Your model is the answer. The question is just whether your model is strong enough to impose it.
Most acquirers can’t answer that question — which is why they spend 18 months studying the target instead.
The Map
Every software company runs on six processes: Lead to Cash, Procure to Pay, Application Lifecycle Management, Employee Lifecycle, Customer Lifecycle, Corporate Governance.
Every function maps to one of these. Finance is Procure to Pay and parts of Lead to Cash. Product is Application Lifecycle Management. HR is Employee Lifecycle. The org chart is how you’ve staffed these processes. It is not the same as owning them.
Ownership means end-to-end accountability. A named person. A built process. An output that doesn’t depend on any one person’s institutional memory. A process that survives personnel change because the process itself — not the person running it — is what holds it together.
Most PE-backed software companies own three and improvise three. The improvised ones are held together by people who are very good at their jobs and very difficult to replace. They will leave within 18 months of close. The clock starts at signing.
The Acquirer’s Model Is the Only Variable
Here’s what a strong acquirer looks like in practice: they can describe, process by process, exactly how the combined company will operate — before diligence is complete. Not aspirationally. Operationally. Lead to Cash by day 30. Employee Lifecycle by day 45. Procure to Pay by day 60.
The target’s existing processes become historical context. Their way of running Customer Lifecycle isn’t a factor in how the combined company runs Customer Lifecycle — because the combined company runs it the acquirer’s way. What the target was doing before is useful for transition planning and nothing else.
This is the version of integration that closes in 90 days or less, sometimes way less, instead of 18 months. Not because the acquirer is smarter or faster, but because there’s only one operating model on the table. There’s nothing to negotiate, bridge, or integrate. There’s just a model being extended to a new set of people and systems.
An IMO exists when there are two models. Strong acquirers don’t have two models.
What Each Process Controls
The six processes matter individually because each one represents a different failure mode when the acquirer doesn’t own it.
Lead to Cash — first marketing touch to collected revenue. An acquirer who owns this can hand the target’s sales team a process on day one. One CRM, one billing system, one set of revenue recognition rules. An acquirer who doesn’t own it discovers six months post-close that they now have two of everything and nobody with the authority to consolidate.
Procure to Pay — how money leaves the building. Vendor consolidation synergies are only real if someone runs this process end to end. Without a strong acquirer model here, the target’s vendor relationships persist indefinitely — not because anyone decided to keep them, but because no one has the process to shut them down.
Application Lifecycle Management — how software gets built, maintained, and retired. Two engineering orgs without a clear acquirer model produce a product roadmap that’s really two roadmaps stapled together. Technical debt compounds fastest here post-acquisition. The acquirer who owns ALM can tell the target’s engineering team how decisions get made, what gets deprecated, and what done means. That conversation takes a week. Without it, it takes years.
Employee Lifecycle — how people enter, develop, and exit. Packages get signed at close. The underlying process — promotion, development, performance management, offboarding — gets assumed from whoever had the stronger HR function, which is almost always the acquirer. If the acquirer doesn’t solidly own this process, you’ve just exported your improvisation to a larger team.
Customer Lifecycle — the arc from first touch to renewal to expansion to churn. This is the process most likely to be nobody’s job even at a mature company. Sales owns acquisition, CS owns some version of retention, product owns engagement, finance owns revenue recognition — and no one owns the full arc. Post-acquisition churn that appears without warning traces here almost every time. An acquirer with a built Customer Lifecycle process — one owner, clear handoffs, clear metrics — can absorb a new customer base without losing the thread.
Corporate Governance — decision rights, board cadence, reporting structure, escalation paths. This is last on every list and first to create friction. The symptom is two forecasts that don’t reconcile and a leadership team that’s nominally combined but practically running separate companies. The acquirer who imposes governance on day one doesn’t have this problem. The acquirer who assumes it works itself out usually gets a year of fog before anyone names it.
The Diagnostic
Before any acquisition, run this test: for each of the six processes, can you describe — owner, a process that runs, system of record — how you operate it well enough to hand it to a new team in 30 days?
If yes, go buy the capability gap. Go buy the customer base you don’t have, the market position you can’t build, the IP that would take you three years to develop. The operational integration is handled. You know what you’re imposing.
If no, fix your own operating model first. The acquisition will still be there.
The companies that exit at top-of-market multiples — the ones that close without surprises in diligence, that have the operating story to match the financial one — ran all six processes before they started acquiring. Not perfectly. But owned, built, and strong enough to absorb whatever they bought.
That’s the standard. It’s also the shortcut. Build the model once, use it on everything you buy.