Change-of-Control Clauses in Technology Acquisition Targets
A technology acquisition can stall when the target's revenue, product and team look attractive. The issue is contract wording: a customer, vendor, lender, licensor or platform partner may have a consent or termination lever when control changes.
For PE investors, strategic acquirers and founders preparing an India-linked technology company sale, change-of-control review protects closing certainty and value.
Why This Matters
The Indian Contract Act, 1872 is the starting point because the consequence of a control change usually depends on the contract actually signed. Some clauses prohibit assignment. Some treat merger, transfer of business or asset sale as a consent event. Others capture any direct or indirect change in shareholding or voting control.
The issue is sharper in technology targets because value may depend on a few enterprise customers, cloud vendors, payment providers, source-code escrow arrangements, reseller channels or inbound software licences. If one counterparty can block transfer or terminate after signing, the buyer may need a condition precedent, price holdback, specific indemnity or a different structure.
The Companies Act, 2013 also matters because board approvals, registers, charges and corporate authority may be tested alongside contract consents. Where contracts were accepted or amended electronically, the Information Technology Act, 2000 helps frame the evidence of electronic records and electronic contracting. If the target's contracts include software, documentation, implementation deliverables or commissioned material, the Copyright Act, 1957 is relevant to ownership and licence continuity.
What Counsel Should Review
Start with a contract map, not just the largest customer agreements. Counsel should review customer contracts, master services agreements, order forms, software licences, reseller agreements, hosting contracts, payment arrangements, lending documents, security documents, partner terms and settlement agreements.
Each contract should be coded for assignment, novation, subcontracting, change of control, merger, sale of assets, transfer of business, affiliate transfer and notice requirements. These labels should be separated. A clause that only restricts assignment may not behave like a clause that restricts a share sale. A clause that allows affiliate transfer may still fail if the acquirer wants to move customers into another group entity after closing.
Customer concentration deserves priority. A consent right in a dormant account is rarely deal-critical. A consent right in a top enterprise customer or multi-year implementation account can affect valuation. The diligence report should show contract value, renewal date, termination rights, consent timing, owner and communication risk.
Vendor and platform dependencies need equal attention. Cloud infrastructure, payment rails, analytics tools, development licences, app-store accounts, OEM arrangements and outsourced engineering providers may contain anti-transfer language. A buyer that inherits revenue but loses a core tool or licence may face transition cost immediately after closing.
Counsel should then connect the findings to structure. A share acquisition, asset transfer, merger or group reorganisation may trigger different provisions. The buyer should know before signing which contracts need prior consent, which require notice and which are silent.
Relevant Judicial Guidance
In Nabha Power Limited v. Punjab State Power Corporation Limited, Civil Appeal No. 8478 of 2014, reported as 2024 INSC 833, the Supreme Court considered express contractual wording and business efficacy. Paragraph 41 of the official judgment is useful for the limited proposition that commercial sense cannot be used to contradict clear contract language.
For change-of-control diligence, the lesson is practical. If the contract says consent is needed for an indirect control change, the buyer should plan around that wording. It should not assume that a court, seller or counterparty will later read the clause as if it only covered asset assignment.
Typical Timeline and Cost Range
A focused change-of-control review for a technology target with a clean contract repository can often be completed within 1 to 2 weeks after the full document set is available. A deeper review across legacy templates, enterprise amendments, reseller arrangements, lender documents and vendor licences usually takes 2 to 4 weeks.
Fees should be scoped by contract volume, material counterparties, execution records, consent planning, customer concentration and whether counsel must prepare only a risk matrix or also draft consent letters, closing conditions and remediation language.
Common Mistakes
- Treating assignment and change of control as the same issue. A share sale may avoid some assignment restrictions but still trigger clauses that expressly cover ownership or control changes.
- Checking only customer contracts. Vendor licences, payment arrangements, hosting contracts, reseller terms and loan documents can create the same closing risk.
- Leaving consent strategy until signing. Counterparty consent can affect deal structure, closing timetable, customer messaging, escrow, indemnity and price.
How KAS & Co. Can Help
KAS & Co. helps investors, acquirers and Indian technology companies review change-of-control clauses before investments, acquisitions and exits. The review can cover customer contracts, vendor dependencies, software licences, consent matrices, closing conditions and transaction-document risk allocation. For focused support, contact KAS & Co..
FAQs
1. Is a change-of-control clause the same as an assignment clause?
No. Assignment usually concerns transfer of contract rights or obligations, while a change-of-control clause may be triggered by a share sale, merger, parent-level sale or indirect ownership change.
2. Which contracts should buyers review first?
Start with top customer accounts, core vendor licences, hosting and payment providers, channel partners, lender documents, settlement agreements and contracts tied to critical software rights.
3. Can a buyer avoid consent by using a share acquisition?
Sometimes, but not always. The answer depends on the clause. Some provisions restrict only assignment, while others expressly capture shareholding, voting control, merger or indirect group-level changes.
4. What should a consent matrix include?
It should list the counterparty, contract value, clause trigger, consent or notice requirement, deadline, owner, business risk, proposed action and whether the item is a signing or closing condition.
Sources
Topics
Need legal advice on this topic?
KAS & Co. provides strategic legal counsel across technology law, data privacy, IP and commercial advisory.
Schedule a Consultation