If your outsourcing provider was acquired in a share sale, your contract carries on unchanged, so nothing is forced this week. What changes is who controls your engineers and your rate. We'd stay while the contract holds and the people stay. Use the moment to get named-engineer and rate-lock terms in writing, and move only on a trigger you can point to. Start exit prep now, because exits take months.
Does my contract still apply after the vendor is acquired?
In a share sale, yes, and you don't have to do anything on day one except read. The company you signed with is often still the company that invoices you, the same engineers still show up in standup, and the same subprocessors still touch your data. A change of ownership shifts who sits above all of that.
This is general information, not legal advice. The governing law and exact wording of your contract decide, so talk to counsel before you send any notice.
The legal frame is short. A change of control is a different mechanism from an assignment of the contract. UK law firm Sprintlaw's guidance for startups says a change in control can happen even when the contracting entity stays the same. That's why clauses on it exist at all. A clause can give you termination, renegotiation, consent or a triggered payment.
Whether a share sale triggers anything depends on the wording and the jurisdiction. Aird & Berlis, a Canadian firm, notes that under Canadian law a general anti-assignment clause will not normally be caught by a share purchase. A clause that bars a change of control can turn the same share purchase into a deemed assignment needing consent. Same deal, different clause, different result. Asset sales and mergers are different again, so ask your counsel which one you're looking at.
Which clauses in my contract decide my options?
Pull the contract and the latest statement of work, and find these eight.
| Clause | What to look for |
|---|---|
| Change of control | Definition, trigger, notice, consent, termination right, fee |
| Assignment | Whether the vendor can pass the contract to the buyer |
| Key people | Named engineers, approved successors, replacement deadline |
| Termination for convenience | Notice period and any fee |
| Rate lock or escalator | Fixed until when, and what a renewal resets |
| Subprocessors and data location | Notice of changes, where data is held |
| Non-solicit | Whether it blocks hiring the vendor's engineers directly |
| IP assignment and repo ownership | Whose account holds the code, and who owns the work |
The non-solicit clause matters more than people expect. If you're thinking of making a direct offer to an engineer who's unhappy with the new owner, read it first.
Here is what a change of control clause can look like. Example wording, not a standard clause: "If the Supplier undergoes a change of control, it will notify the Customer in writing promptly, and the Customer may terminate on notice without fee." Your contract may say less, or charge a fee. Sprintlaw's guidance mentions options such as termination only when the new owner is a competitor, and continued service during a transition. Its examples use notice periods of 60 to 90 days, a useful range to ask for if your clause gives you none.
If you can't find a change of control clause, the assignment and termination for convenience clauses carry your options. Read them together.
What do I ask the new owner?
Ask in writing, within the first week, and ask for answers in writing. Six questions:
- Which of our named engineers are covered by retention terms, and for how long?
- Will our rate card stay as it is for the rest of the term?
- Is any work moving to another delivery centre or another legal entity?
- Will the list of subprocessors change?
- Who is our account lead now, and who do we escalate to?
- Will new tooling or reporting mandates apply to our team?
We'd ask in the window between announcement and close, while the buyer still wants a quiet handover. Site Selection Group's April 2026 piece on acquired BPO providers says integration can last anywhere from six months to two years. Acquirers may consolidate or relocate delivery centres, and account teams often change. Renewals may bring pricing pressure. Track swaps and the rate card yourself while you wait for answers.
What changes for my data when the vendor changes owner?
This matters only if the vendor processes your personal data in its own environment, which makes it a processor. Under GDPR Article 28(2) a processor may bring in another processor only with the controller's prior specific or general written authorisation. The EDPB's Guidelines 07/2020 on controllers and processors explain how that authorisation and the duty to inform about changes work. Check that your agreement's sub-processor notice clause gives you time to object before a new hosting setup or group tool goes live.
A new owner often brings new infrastructure, a new hosting arrangement or a group-wide tool. Each is a possible subprocessor change, and you should be told, or asked to approve, through the channel your agreement sets up. Check what your agreement requires, starting from what a data processing agreement must contain.
Contractors working inside your own tooling and accounts usually aren't processors in this sense, so for most staff-augmentation-style setups this section is a quick check, not a project.
What should I watch over the next 90 days?
Track these signals weekly and write them down. One signal is noise. A repeat is a pattern.
| Signal | Points toward |
|---|---|
| One of your engineers resigns | Invoke key-people clause, then watch for a second |
| Unannounced swap of an engineer | Renegotiate, or move if it repeats |
| Rate card "harmonised" upward | Renegotiate, using your rate lock |
| Delivery work moves to another site or entity | Ask for approval rights, move if refused |
| New tooling or reporting mandates | Stay, but cost it |
| Account manager changes twice | Escalate, then renegotiate |
| Invoices stop naming the people who did the work | Renegotiate, move if refused |
For the rate signal, audit one agency invoice against the rate card before you answer any letter from the new owner. Invoices that name each person and their hours are your best evidence in every row above.
Should I stay, renegotiate or move?
The rule we'd use:
- Stay when the contract holds, your engineers stay and the rate is stable.
- Renegotiate when a right exists or renewal is near. Offer a longer term in exchange for key-person terms, a rate lock and an exit window.
- Move when named engineers leave, a clause trigger fires, or the same signal repeats twice.
Moving is slow. A 2006 Computerworld article said many contracts include change-of-control provisions that release customers, but quoted a Forrester analyst that termination often carries a fee and switching can mean months of disruption. Site Selection Group says exits take many months, sometimes over a year, and that termination for convenience is not a complete safeguard. You can't start the exit on the day you decide.
So start while you're staying. Put the repo in your own organisation, get the IP assignment signed, and keep an inventory of every access your engineers hold. If you do move, taking over a vendor's codebase covers the mechanics, and moving from an agency to an in-house team covers handover and IP.
Worked example: six named contractors at a vendor that was just bought
Hypothetical numbers and contract terms. A Series B company has six contractors at one vendor on a single SOW: a tech lead, four backend engineers and a QA engineer. A private-equity-backed group buys the vendor. The tech lead and four backend engineers bill at an illustrative blended €70/hr, 160 hours each a month, so those five cost €56,000 a month.
On day 1 nothing changes on paper. You send the six questions above and ask for answers within a week.
By day 30 a letter proposes a "harmonised" rate 10 percent higher. On these inputs, on the five priced contractors, that's €5,600 a month, €67,200 a year. The example contract fixes the rate until renewal in five months, so you decline and ask to extend the lock.
On day 60 the tech lead resigns. The example's key-people clause requires an approved successor within 30 days, so you invoke it and interview the proposed replacement yourself.
On day 90 a second engineer is swapped without notice. That's a second named engineer gone in 30 days, the "watch for a second" case from the signals table, so the decision is move. It costs little to act on, because the repo already sits in your organisation, the IP assignment is signed and the access inventory exists.
What this means for your next renewal
Sign nothing new at the old terms. Use the renewal for three asks: named engineers with approved successors, a rate lock for the full term, and an exit window with transition help. Trade a longer term for them if you're staying, and treat a refusal as information. Walk into that meeting with the written answers to the six questions and the 90 days of signals, so you negotiate from what the new owner has committed to, not from the announcement. If the CFO signs, the rate lock is the ask to explain first, because it caps the cost whatever the new owner's pricing plans turn out to be.
Where to go next: everything on engagement models sets out how contractor, outsourcing and dedicated team setups compare on exactly these terms.
Covering the work while you decide, through HighCircl
If your exit prep is running while the vendor's engineers are still mid-sprint and the new owner hasn't said who stays, you need a way to add capacity to cover the work while you decide and run that prep. HighCircl has no minimum hour commitment, and if an engagement isn't working, we replace the engineer at no additional recruitment cost. See how hiring through HighCircl works.
FAQ
What is a change of control clause in an outsourcing contract?
It's a clause that reacts when ownership of the vendor changes, even when the vendor itself stays the same company. It can require notice, require your consent, give you a right to terminate or renegotiate, or trigger a payment. It's separate from an assignment clause, which covers passing the contract itself to another party.
Can I terminate if my outsourcing provider is acquired?
Only if your contract says so. A 2006 Computerworld article said many contracts include change-of-control provisions that release customers, and quoted a Forrester analyst that termination often carries a fee. Whether yours does is in the contract: read your change of control, assignment and termination for convenience clauses together, and check the notice period before you act.
Does an acquisition change my contract with the vendor?
In a share sale the contracting entity stays the same and the contract continues. An asset sale or merger can change who the counterparty is, and the governing law and the wording decide. Canadian practice, per Aird & Berlis, shows how wording can flip the result, so ask counsel before assuming either way.
Sources
- Site Selection Group: What companies should prepare for when their BPO provider gets acquired
- Sprintlaw: Change in control clauses for UK startups and SMEs
- Aird & Berlis: Anti-assignment provisions and assignments by operation of law
- EDPB: Guidelines 07/2020 on the concepts of controller and processor
- EUR-Lex: Regulation (EU) 2016/679 (GDPR)
- Computerworld: Fight or flight (2006)
