Ask The Analyst: When your HR technology vendor is acquired, what questions should you be asking?

Every week for The Briefing, UNLEASH’s weekly intelligence email for senior business decision-makers, we ask our community of analysts – the true HR experts – to solve the biggest workplace challenges.

This week we asked: When your HR tech vendor is acquired, what questions should you be putting to the new owner, and whose answers should you trust?

Here’s the analysts’ perspectives.

Cheney Hamilton, Research Director – FusionWork, Bloor Research:

Start with the question nobody asks until it’s far too late: who now carries the liability when your tool gets it wrong?

A US federal court has already ruled that a vendor can face discrimination claims over its AI hiring tools, so that carefully negotiated accountability clause is now a live legal asset. Does it survive the acquisition, or did it just become row 400 of somebody’s integration spreadsheet?

Then three more:

• Does our data now train the new owner’s models?
• Which products actually survive, because acquirers buy customer bases and sunset platforms, and your roadmap was promised by people who may no longer work there.
• And do our audit rights, bias testing evidence and exit terms transfer unchanged, in writing?

As for whose answers to trust: nobody’s, if they arrive as reassurance. The “nothing changes for our valued customers” email is a press release with your name mail-merged into it. The account manager promising continuity is often finding out about their own future on the same call as you.

So, trust three things:

• The contract, as amended and countersigned by the new entity, because warm words are not legally binding.
• The acquirer’s track record, because what they did to the last three companies they bought is the actual roadmap.
• And your own General Counsel’s reading of both.

An acquisition doesn’t change what your vendor promised you. It changes who is bound by the promise, and that’s the only question worth your meeting time.

Erika Oliver, Managing Director, NewtonHaus & Executive Analyst, Aptitude Research:

Most of the important questions apply regardless of company size. What tends to change with scale is emphasis and leverage, not the list itself.

Questions worth asking at any size:

• Does the product continue as sold, and for how long?
• Will pricing and packaging hold through renewal?
• Do our security certifications and data-processing agreements carry over, and will our data be used to train the acquirer’s models?
• Which integrations are being maintained versus rebuilt?
• Does the change-of-control clause give us an exit, and in what format does our data come back if we take it?
• Who, by name, is accountable for this product now?

In our experience, a joint review by HR, IT, Legal, and Procurement is useful at almost any scale; the difference is whether it takes an afternoon or a quarter.

Where emphasis tends to shift:

• Smaller organizations (roughly 200–1,000 employees) are often most exposed on support continuity and whether the acquirer already owns a competing product it may steer them toward.
• Larger organizations (5,000 and above) will likely want to probe the acquirer’s capital structure, engineering retention, and contingency planning if the product were to be sunset.

At the upper end, it is probably reasonable to treat the acquisition as a renewal that has arrived early and reopen commercial terms accordingly.

Whose answers to trust: We would suggest some caution with the acquirer’s sales and communications functions, whose role is retention. More reliable signals usually come from the acquired vendor’s long-tenured staff, peer customers, and the acquirer’s record with its previous purchases.

Jess Von Bank, Co-Founder, Now To Next:

HR technology acquisitions often look like gap-fillers: a missing capability, a broader suite, a more complete offering. But the buyer may also be buying market share, cross-sell access, workforce data itself, or margins to improve. Those are legitimate business objectives. They just aren’t necessarily *your* objectives.

Customers and prospective buyers need to understand whether the new entity will still serve what they’re trying to achieve, and "accelerated innovation” in the press release doesn’t answer that.

Three questions worth asking:

• Where are the engineering dollars (and headcount) going? How much of the core team will remain dedicated to the product you bought, versus parent-platform integrations? What roadmap commitments will that investment support?
• What could trigger a migration? Ask about product consolidation, module retirement, and pricing changes. Get meaningful protections in writing: notice periods, price commitments, and transition support.
• How will our data be used? Clarify changes to storage, access, and model training. What requires your consent, and what can you decline?

Then check the answers against the acquiring company’s track record. As in, talk to customers living with its previous acquisitions. Did investment follow the announcement? Did roadmaps survive? Were customers given meaningful choices, or gradually priced and nudged toward another platform?

An acquisition can create real value. But the transaction itself proves nothing about whether that value reaches you. Your business case doesn’t transfer automatically with the ownership paperwork. Make the new owner re-earn its place in your stack.