We Just Acquired a Company. Now What Happens to Their IT Spend?

The Question

My company just acquired another company, and leadership wants their IT spend in our TBM model. How do I do that, and how fast can I realistically do it?

What's Going On

Leadership wants a combined view of IT spend, but their data lives in different systems. Data integration rarely makes the synergy list, so it tends to lag, sometimes for years.

What I'm Afraid Of

I'm afraid the patched-together model becomes permanent and impossible to manage, because it works just well enough that nobody funds the real integration.


You can only move as fast as the data.

That's the short version, and it's what I told someone who asked me this in person. You can build a model that bridges the two companies with spreadsheets and manual mappings. It works, but it's a short-term fix on the way to getting their data into the CMDB and the other systems of record.

Here's how I'd approach it in practice.

1. Build the bridge, and label it a bridge. I worked with a very large acquirer that had a long habit of buying companies and letting IT integration drag on. The acquired company's CIO wanted to see their spend in the parent's cost model. So we built what was effectively a model within a model. The acquired company's data lived in its own lane, with its own sources, and we were explicit about where each piece came from. For example, the application list came from an Excel spreadsheet.

2. Build an automated switch. We created automated levers for each data source. When the acquired company's applications eventually landed in the parent's ServiceNow CMDB, we could flip that slice of the model from the spreadsheet to the real source. The model itself showed what had transitioned and what hadn't. That visibility gives you an integration completeness measure almost for free: how much of the acquired company's spend is mapped through real sources versus manual workarounds.

3. Agree on definitions before you flip anything. One of the first things this surfaced was a disagreement about what an application even is. The acquired company defined it one way. The acquirer's ServiceNow team defined it another. Neither switch could flip until both sides agreed on one definition, and that debate opened the door to a broader conversation about managing IT like for like, instead of the acquired company staying on an island and producing misaligned readouts that confused everyone.

4. Put dollars on the integration delay. At some point leadership will ask for application rationalization or budget cuts across the combined estate. If you've done the work above, you can give leadership a straight answer: Here is what we can decide today because the data is integrated and trusted, here is where we have less confidence, and here is where we have little to no visibility. Putting dollars against each category turns data hygiene into a funded priority.

This is where a TBM capability serves an organization after an acquisition. It does more than consolidate reporting. It makes the integration gaps visible, puts a number on them, and gives leadership a reason to close them.

Hope that helps!
Gboyega Adebayo


Have a question of your own? Submit here.

Want next week's answer in your inbox? Subscribe here.

Next
Next

How hard is it to switch TBM tools?