You get an email, or read the news: the company behind a piece of software your business depends on has been acquired. The reassuring message says nothing will change. Sometimes that is true. Often it is not, and the changes — to support, to the product’s direction, to pricing — arrive over the following months in ways that affect you directly. A vendor acquisition is a moment to review your position quickly and clear-headedly, not to assume it will be fine.
What actually changes after an acquisition
Acquisitions change the equation in predictable ways. Support often shifts — the people you dealt with leave, response times change, the personal relationship that smoothed things over disappears. The product roadmap changes to suit the acquirer’s strategy, which may mean the features you relied on are deprioritised, or the product is folded into something larger, or quietly wound down. And pricing tends to move, because acquirers buy customer bases partly to monetise them, and the favourable terms you had are not guaranteed to survive. None of this is certain, but all of it is common enough to take seriously.
The worst outcomes happen to businesses that took the “nothing will change” message at face value, did nothing, and were then caught out a year later when the product they depended on was discontinued or repriced — with no plan in place.
Free · 4 minutes
If your most senior engineer left tomorrow, would anyone still understand the system?
Fourteen questions on documentation, dependencies, and the gap between how the architecture works and how many people know it. Banded finding on screen, full sheet by email.
Why this exposes your dependency
An acquisition is really a stress test of how dependent you are on a single vendor. If the answer is “completely, and we could not easily move,” then the acquisition has just transferred a chunk of control over your business to people you did not choose. That is the same underlying exposure as a vendor owning your roadmap — the acquisition simply makes the dependency visible and changes who is holding the other end of it. And if the product is also one your systems are tightly wired into, an eventual forced move can become the kind of untangling described in the compound problem.
What to do — quickly
The right response is a clear-headed review while you still have time to act, rather than after the changes force your hand. Establish how dependent you actually are — what would break, and how badly, if this product changed or disappeared. Read the signals from the acquisition: who bought them, why, and what that usually means for products like the one you use. Understand your realistic alternatives and what switching would actually cost, so you are negotiating and planning from knowledge rather than fear. And decide a position: stay and monitor, start preparing an exit, or move now — made deliberately, not by default.
If you do decide to move, do it for the right reasons and in the right way, so you do not simply leave for the next platform for the same reasons you left this one. An acquisition is a prompt to think, not a command to flee.
Vendor acquisition changes the support, roadmap and pricing equation immediately, even when the announcement says otherwise. A clear-headed review of your options is worth having quickly. We will work out how exposed you are and what to do about it.
Start a ConversationFree interactive tool
Interactive deadline calculator
Check which regulations apply to you and when
Regulation across the EU, UK, US and Asia-Pacific has moved considerably in the past eighteen months, and several headline dates have shifted more than once. Twelve questions, about three minutes.
Results are shown on screen — no email required. A dated summary is available to download, and can be sent on if that's more useful. What we do with your answers.
Governance is what happens when nobody is watching.
Policies are easy. Consistent decision-making is harder. Understand where governance exists and where it has quietly become assumed.
Full Governance by Sixteen Pillars
Govern your business. Prove your compliance.
A board assurance cockpit for EU-regulated financial firms — tamper-evident, hash-chained proof of governance across DORA, GDPR, NIS2, ISO 27001, the EU AI Act and MiCA. In development.
See what's coming