Where to Start
by Braden Kelley and Art Inteligencia
Every M&A announcement talks about synergies, market position, and combined capabilities. Almost none of them talk about the fact that, on day one, you now have two customer bases who each learned to expect something different from the companies they chose — and neither of them signed up for the other company’s version of the relationship.
The assumption that quietly sinks post-merger CX
The default assumption in most integrations is that the better-resourced or larger company’s experience simply becomes the standard, and the other customer base adjusts. I’ve watched this assumption cost companies real customers, because it skips a step that matters enormously: nobody has actually compared the two experiences at the touchpoint level to know which one is genuinely better, versus just louder or more familiar to the leadership team making the call.
Two journeys, two sets of expectations, one deadline
Integration timelines are usually set by finance and legal milestones — closing conditions, systems cutover dates, reporting deadlines — not by how long it actually takes to understand two customer journeys well enough to merge them intelligently. That mismatch is where the damage happens. Support processes get unified before anyone’s mapped where they genuinely differ. Pricing and billing experiences get standardized before anyone’s identified which parts of each were actually working. By the time customer complaints start flagging the problems, the systems decisions are already locked in, and unwinding them costs far more than getting it right the first time would have.
Start by mapping both journeys independently, before merging anything
The instinct in an integration is to move fast toward one unified experience, because ambiguity feels risky to the deal’s momentum. I’d argue the opposite is true here: the riskiest move is unifying before you understand what you’re unifying. Mapping both customer journeys independently — validated personas, current-state touchpoints, the data each company has been collecting, and, critically, walking both journeys firsthand rather than trusting either side’s internal narrative about how good their own experience is — gives you an honest picture before any integration decision gets made instead of after.
Whose employees explain the friction matters as much as whose customers report it
In an acquisition especially, frontline employees from the acquired company often sit on institutional knowledge about their customers’ real pain points and workarounds that never made it into any deck during diligence. They also, often, feel like their side of the business is being absorbed rather than genuinely evaluated — which makes them less likely to volunteer that knowledge unless someone specifically goes looking for it. An audit that treats both organizations’ frontline teams as equally credible sources, rather than defaulting to whichever side is running the integration, tends to surface friction neither leadership team knew existed.
Benchmark both experiences against the market, not against each other
The other trap is treating this purely as an internal comparison — which company’s process wins. The more useful question is how each one stacks up against what customers in the combined market now expect, especially if the merger changes your competitive position or brings you into contact with a new set of competitors either customer base is now implicitly being compared against.
What this actually buys you
Getting this right doesn’t just avoid a bad integration story — it turns the merger into a genuine opportunity to build a better combined experience than either company had running independently, using the best of what each side was actually doing well. That’s a very different outcome than the default of one side’s process quietly winning by default and both customer bases losing something in the process.
If you’re heading into an integration and want an independent, evidence-based read on both customer experiences before any systems or process decisions get locked in, a Customer Experience Audit scoped to both organizations is exactly the kind of diagnostic this moment calls for. And if you want a rough sense of what experience misalignment could cost during an integration before you scope that engagement, the CX ROI Calculator is a fast place to start.
Image Credits: Pexels
Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Claude to clean up the article.
Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.