The Real Reason Mergers Break Down

Mergers don’t usually fail because of a single bad system. They fail because people, process, and technology are pulled in different directions at the same time.

Tom Amburgey, CEO of Unit Solutions, shares a practical view of what it takes to bring companies together after multiple acquisitions. His perspective matters for technologists and business leaders because it cuts past the buzzwords and gets to the hard truth: integration is a human problem first.

Start with the Why, Not the Tools

Culture Comes Before Systems

When organizations merge, the instinct is often to unify the software stack fast. But Tom makes a strong case for starting with culture and clarity: why does the business exist, what does it do, and how should people behave together?

That framing helps teams understand why change is happening instead of assuming it is just cost-cutting or control. In a merger or digital transformation, the “why” can reduce resistance more than any technical roadmap.

Listening Beats Mandating

One of the most useful leadership moves Tom described was a listening tour. He spent the first 90 days talking to hundreds of employees so people could raise concerns before decisions were finalized.

That matters because change often feels like loss. A new tool, a new process, or a new org chart can trigger anxiety about identity, status, and belonging—leaders who acknowledge that reality earn more trust than leaders who hide behind policy.

Key takeaways

• Define the purpose of the change in plain language.

• Listen before you standardize.

• Treat resistance as a signal, not a problem to silence.

The Hidden Cost of “Simple” Tech Changes

Slack, Email, and Other Everyday Friction Points

It’s easy to assume the hardest part of integration is the big enterprise system. In reality, teams often fight hardest over familiar tools like Slack, email, file storage, and expense reporting.

Why? Because those tools become symbols of identity. Losing them can feel like losing the old company itself. Tom’s approach was to explain the reason for each change, admit mistakes, and keep leaders visible and accountable.

Data and CRM Migration Need Real-Time

Technology integration is where many mergers stall. Tom shared that email and file migration went fairly well, but CRM consolidation took much longer than expected.

That’s a familiar lesson for any business leader: don’t force an artificial six-month deadline on a complex migration. ERP, CRM, and data mapping projects need realistic timelines, third-party support, and room for cleanup after launch.

AI Transformation Works the Same Way

Adoption Depends on Trust

Tom’s team is now rolling out enterprise AI across the organization, and the playbook is surprisingly similar to merger integration. The biggest success factor is still transparency: explain the value, show the workflow impact, and be honest about what will change.

That’s especially important because employees are reading headlines about AI replacing jobs. Leaders need to address fear directly and show how AI can augment people, not just automate them out of a job.

Lead by Example

Tom also uses the tools himself and tracks adoption from the top down. That sends a clear signal: if the CEO is using AI to work smarter, everyone else has permission to learn.

For technologists and executives, that’s the real lesson. Transformation sticks when leaders model the change they want to see.

Listen to the Full Conversation

If you want more practical lessons on mergers, culture, and AI-driven change, listen to the full episode and subscribe to Embracing Digital Transformation for more leadership insights.