The software that arrives in an acquisition and never leaves.

The IT Category Manager had been in post a month when he laid out his priorities: Microsoft renewal, rationalisation, visibility across entities acquired over the previous five years. Standard enough. Then he said something that stayed with me.

“When we acquire a company, there’s a due diligence process. Things get checked. But we don’t go into this kind of detail. We don’t really understand what the software coming in actually does, what we already have that overlaps, what we can exit. That analysis just doesn’t happen.”

He was right. And the pattern repeats across every industry that acquires.

What the lawyers actually check

Financials are scrutinised for months. Legal exposure is mapped. Headcount is modelled. Property is surveyed. Someone literally counts the desks.

But software? Someone exports a list. You get a spreadsheet of publisher names and product codes. That spreadsheet goes into a folder. The folder doesn’t get opened again until a renewal reminder arrives eighteen months later.

The problem is not that people don’t care. It’s that nobody has the capability to do anything meaningful with the list. Knowing you’ve acquired 400 software products tells you almost nothing. What do those 400 products do? Which overlap with what you already own? Which can be exited in 90 days versus which are load-bearing infrastructure that would take two years to unwind?

The questions nobody can answer

Nobody answers those questions at speed. Not without months of workshops and difficult conversations with team leads who are convinced their tool is irreplaceable. So the list stays in the folder. Duplicate tools compound. Budget grows. Eighteen months later, you’re renewing something you didn’t need to renew.

The same pattern appears across insurance, automotive, energy, pharma. The acquisition completes. The software comes in. Nobody has the intelligence to act on it. So they don’t.

The gap isn’t data. Most enterprises have data. Snow, Flexera, ServiceNow, spreadsheets. They know what they own. They don’t know what it does. Not at feature level. Not in context. Not compared against what they already own.

Knowing you own it versus knowing what it does

Knowing you’ve inherited 400 products is completely different from knowing which 40 can go immediately, which 80 overlap with your existing estate, and which six are candidates to consolidate your remaining stack around.

SAM tools track licences and entitlements. They can’t tell you what a product does, let alone where it overlaps with something you’ve owned for years. Procurement platforms sit in the workflow but carry no product intelligence. Generic AI can suggest answers, but it has no context on your estate and no accountability for what it gets wrong.

Feature-level intelligence is the missing piece. Not “you own Miro” but “you own Miro, you already own Lucidspark and Confluence diagramming, here is the overlap, here is the exit path.”

Turning a list into a consolidation roadmap

This is what Samplify does. You supply two columns: publisher and product. We return what each product does, where the overlaps sit, what the consolidation opportunities look like, and how long each exit would realistically take.

One client prevents $2-3M in wasted spend per month using this workflow. 330-plus hours saved monthly. 92% of a $120M-plus spend evaluated. Not through a new platform, not through months of workshops. Through knowing what the software actually does before the renewal reminder lands.

For any acquisitive business, this is due diligence. The kind you’d apply to anything else you’re spending millions on. See how the decision layer works, or start a 30-day proof of value with nothing but your software list.