← All insights
James Hayward-Zhu5 min read

CS During M&A: The Questions You Need to Answer Before the Deal Closes

CS during M&A
A paper collage on green. A cut-out figure stands astride two sheets of lined paper crudely taped together, the seam obvious and misaligned beneath their feet. Newspaper scraps, a child's drawing of houses, vintage halftone figures, a modern photograph and an engraving surround them.

Acquisitions are one of the highest-stakes moments in a SaaS company's relationship with its customers, and CS teams are consistently underprepared for them. Not because CS leaders don't care, but because M&A preparation happens in finance, legal, and product, and CS gets looped in late, if at all.

I've been in or around enough of these to know that the customers who churn in the 12 months after an acquisition are rarely the ones who had problems with the product. They're the ones who felt like the relationship changed (who suddenly found themselves dealing with different people, different processes, different commercial terms), and decided that the uncertainty of switching was worth it.

Most of that churn is preventable. But preventing it requires CS to be involved before the deal closes, not after.


The two-sided problem

When an acquisition is announced, CS teams on both sides face a different version of the same problem: what do I tell customers, when, and how do I manage the relationship during the uncertainty?

For the acquired company's CS team, the immediate instinct is often to reassure customers: "nothing is changing for you." That's almost never true, and customers usually know it. What they want isn't false reassurance. They want a credible answer to the question: "Is this product still going to exist in 18 months, and is the team that understands my business still going to be here?"

For the acquiring company's CS team, the challenge is different: you're suddenly responsible for a customer base you don't know, often on a product you haven't used, with a legacy of commitments and context that lives in the heads of people who may or may not be staying.

Neither side is usually given the information they need to have these conversations well.


What CS needs to know before the deal closes

If you're going to manage the transition well, these are the questions that need answers in the pre-close period, ideally with CS leadership involved in the conversation:

Roadmap alignment. Are there features or integrations in the acquired product that are on the acquiring company's roadmap, or do they create duplication? Customers who have bought based on specific roadmap commitments need to know if those commitments are still live. CS should have visibility into this, because the alternative is CSMs hearing about roadmap changes from customers.

Commercial terms. Will pricing change at renewal? Are there grandfather clauses? What happens to multi-year deals? These questions come up in the first customer conversation after announcement. CSMs who don't know the answers lose credibility with the customers who notice.

Team continuity. Which people are staying, and in what roles? Customers with long-standing CSM relationships care about this. The honest answer is often "we're still working it out," which is fine, but there should be a plan for how you communicate when roles are confirmed, not just when they're uncertain.

Product timeline. If there are two overlapping products, what's the migration path and timeline? This doesn't need to be fully resolved before announcement, but CS teams need enough information to set realistic expectations rather than non-answers.


The communication cadence that actually works

The mistake most CS teams make in the immediate post-announcement period is treating communication as a one-time event: the announcement email, the executive briefing for top accounts, and then waiting for customers to ask questions.

What works better is a tiered, active outreach model in the first 30 days:

Tier 1 (strategic accounts, renewal within 12 months): Personal phone call from a senior CSM or CS leader within 48 hours of announcement. Not a pitch. An honest conversation about what's changing, what isn't, and what the customer's biggest concerns are. This is the conversation that prevents churn, and it needs to happen before the customer has had time to take a meeting with a competitor.

Tier 2 (growth accounts, coming renewal): Personalised email with a structured follow-up call within two weeks. The email should acknowledge the news directly rather than burying it in reassurance. Customers who feel like the communication was designed to manage them rather than inform them carry that feeling into the renewal conversation.

Tier 3 (long-tail accounts): Scalable communication with a clear FAQ and a feedback mechanism. The long tail doesn't need personal outreach, but it does need accurate information and a way to escalate if their concern is specifically about their account.


The retention risk nobody talks about

The most underappreciated retention risk in an acquisition isn't the customer who calls you the day after announcement. It's the customer who doesn't call, who quietly starts evaluating alternatives over the next six months and shows up at renewal with a competitor comparison they've been building since the deal was announced.

The signal is usually there in the data: reduced product engagement, declining executive sponsor responsiveness, support tickets that start asking about data export and API documentation. By the time that pattern is visible, you're in a reactive position.

CS Ops can help here by building an explicit acquisition-retention flag into the health score model for the 12 months following close, tracking engagement drift and sponsor stability specifically in the context of the transition, not just the baseline churn indicators.

It's a specific, bounded problem. And it's the kind of problem that benefits from being named explicitly rather than absorbed into the general "at-risk accounts" bucket, where it competes for CSM attention with everything else.


What changes, what doesn't

The fundamentals of good CS don't change in an acquisition: customers want to know you understand their business, that the product is going to keep working, and that someone is accountable for their success. An acquisition creates uncertainty about all three of those things simultaneously, which is why it's hard.

What changes is that the relationship capital CS teams have built becomes disproportionately valuable, and disproportionately fragile, in a short window. The teams that protect it are the ones who treat the transition as an active programme, not a communication exercise.


Questions worth sitting with: If your company announced an acquisition tomorrow, how quickly could you produce a segmented customer list with renewal dates, health scores, and primary contacts, and how confident would you be in its accuracy? Do your CSMs have enough relationship depth with their accounts to have a direct conversation about the acquisition, or has the relationship been primarily process-led? And what's your current health score model missing that an acquisition-specific risk flag would help you catch?

Share this

Email

Working on this in your business?

We help UK SMEs and scale-ups turn this kind of thinking into action.

Bring us the problem. Leave with a path.

Request a free 30-minute strategy call