Three skills-data companies agreed to be acquired in the three weeks between September 17 and October 6. I think HR buyers should read that as a deadline: any contract that holds employee skills data needs exit and change-of-control terms before the next deal lands, not after it.
The record is the product
A skills platform stores something unusual. It holds the vendor’s inferences about what each employee can do, built from your HR systems, your job architecture and your people’s work. When SAP announced that it will acquire TechWolf, the release said TechWolf gives enterprises “a continuously updated view of the work their people do and the skills they have.” That sentence describes a data asset, and the asset sits on the vendor’s side of the contract unless the contract says otherwise.
It is the same pattern we have tracked in recent weeks. Phoenix Education Partners agreed to acquire Fuel50, and Pearson agreed to acquire Workera. Pay data is drifting into suites as well, as we saw when pay data vendors moved into talent suites. The buyers differ, and each is paying for a maintained record of what employees can do.
The case for relaxing
The strongest argument against my position is that acquisition is good for customers. A larger owner funds the product, keeps it supported and wires it into the systems HR teams already run. SAP’s own announcement leans on that logic, and it also makes a commitment: subject to closing and required consultation, SAP’s current plans are for TechWolf to remain an independent entity under its CEO and for the platform to remain available to both SAP and non-SAP customers. If that holds, a buyer on a non-SAP stack loses nothing.
I accept most of that. A funded, supported product beats an orphaned one, and independence plans are a real signal. They are also plans. The release calls them “current plans” and attaches them to closing and consultation. Nothing in it gives a customer a contract right to a data export, an integration guarantee or a notice period. A plan that sits in a press release can change after a quarter of integration work, and the customer who has no clause has no recourse.
What the clause should say
The goal is portability of the record, and it takes four terms:
- Ownership. Skills inferences about your employees belong to you, and the vendor may not use them to train models offered to other customers without your written consent.
- Export. You can pull the full skills and task record in a documented, machine-readable format at any time, at no extra charge.
- Change of control. If the vendor is acquired, you get written notice and a window to terminate without penalty, with your data returned or deleted on your instruction.
- Integration continuity. The connectors to your HRIS and talent systems stay supported for the contract term, and the vendor names the systems.
None of this is exotic. Most procurement teams already ask for data return and deletion terms on payroll and recruiting software. Skills platforms have been sold as analytics tools, so the same scrutiny has not followed them. The analytics label is out of date. TechWolf’s CEO, Andreas De Neve, said in the announcement, “We have spent eight years building the evidence layer to answer those questions.” Evidence about employees that an HR team may one day cite in a promotion, redeployment or layoff decision deserves a custody arrangement.
A second reason to act now
Skills data is moving into agent workflows. SAP’s chief product officer for its autonomous suite described the TechWolf model as a grounding layer for agent queries about work and skills planning, and said it lowers the cost of deploying workforce agents. Once agents read a skills record before they answer questions about who should move where, errors in that record turn into decisions. An HR leader who cannot see how the record was built, or cannot take it elsewhere, has little say in correcting it.
The practical step this quarter is small. Pull every contract that touches skills, task or work-pattern data, check each for the four terms above, and add the missing ones at renewal. Where a renewal is distant, send the vendor a short letter asking it to confirm its export format and its change-of-control notice policy in writing. A vendor that answers quickly has done the work. A vendor that stalls has told you something about the next acquisition.
Source: SAP News Center
