Majority Acquisition Diligence for Indian Enterprise Software Companies

A majority acquisition of an Indian enterprise software company is not just a larger minority investment. The buyer is taking control of customer risk, product roadmap, employee base and post-closing liabilities. Legal diligence should answer one practical question: can the buyer own and operate the business it is pricing?

Enterprise software targets often look orderly because revenue is contractual and product delivery is repeatable. The hard points sit behind that surface: code ownership, customer exit rights, founder continuity and regulatory timing.

Why This Matters

The first issue is route and structure. A control deal may be structured as a primary investment, secondary share purchase, merger, asset acquisition or mixed consideration. Where a non-resident buyer is involved, RBI's Master Direction on Foreign Investment in India should be checked for entry route, eligible instruments, pricing, reporting and downstream investment issues. DPIIT's foreign direct investment materials should also be reviewed for sector conditions, investor-origin restrictions and approval-route questions.

The second issue is corporate authority. The Companies Act, 2013 is the baseline for board approvals, shareholder approvals, share transfers, private placement mechanics, registers, beneficial ownership records, charges, related-party transactions and post-closing governance. Counsel should reconcile the cap table with filings, articles, shareholder agreements, minutes, ESOP grants, side letters and prior financing documents before the buyer signs.

The third issue is business continuity. Enterprise customers may have assignment limits, change-of-control rights, termination-for-convenience language, audit rights, security addenda, exclusivity, most-favoured pricing, service-level credits or procurement conditions. These terms can affect revenue quality immediately after closing.

What Counsel Should Review

Start with ownership and control mechanics. A buyer should know which securities are being purchased, which consents are needed, whether drag rights can be used, whether dissenting shareholders can block closing, and whether founder, investor or lender consent is required. If fresh securities are used, valuation, pricing, private placement and filing steps should be mapped before signing.

Next, diligence software ownership. For source code, product documentation, UI assets and technical content, the official Copyright Act, 1957 is the statutory starting point. The buyer should review founder assignments, employee invention clauses, contractor agreements, open-source records, repository access, build documentation, escrow arrangements and customer-funded development. If the product uses patents, designs or trademarks, registry checks and assignment records should sit in the same file.

Then test customer and vendor durability. A top customer may need prior written consent, a reseller may control a key market, a cloud provider may have suspension rights, or a strategic customer may own bespoke product components. Counsel should separate consent-critical contracts from housekeeping issues.

Employment and founder continuity need a separate workstream. Majority buyers should review employment terms, retention promises, ESOP treatment, restrictive covenants, founder service arrangements and severance exposure. If founders roll over equity or stay as managers, their continuing rights should not conflict with the buyer's control rights.

Competition screening should happen early. The Competition Act, 2002, CCI's filing guidance for combination notices, and the Competition Commission of India (Combinations) Regulations, 2024 are practical starting points. A strategic buyer, platform roll-up or large fund group should test thresholds, deal value, control rights, portfolio overlaps and timetable risk before assuming signing can proceed without a filing.

Finally, convert findings into deal controls. Major issues should become conditions precedent, indemnities, escrow or holdback points, price adjustments, special covenants, founder undertakings, remediation schedules or walk-away rights. Minor issues should sit in a post-closing action list with owners and deadlines.

Typical Timeline and Cost Range

A focused red-flag review for an organized Indian enterprise software target can often be completed in 3 to 5 weeks after the diligence room is usable. A full control acquisition with customer-consent work, founder rollover, lender consents, IP cleanup or CCI analysis can take 6 to 12 weeks or more.

Fees are best scoped by workstream: corporate and foreign-investment review, IP and software ownership, customer and vendor contracts, employment and founder continuity, competition screening, and closing documentation. This keeps the review aligned with control risk rather than a broad checklist.

Common Mistakes

1. Assuming control solves old document problems. The buyer may control the company after closing, but pre-closing defects in approvals, ownership, consents and filings can still reduce value.
2. Treating customer contracts as revenue proof only. The same contracts may contain consent rights, termination triggers, audit obligations, liability exposure and pricing commitments.
3. Separating IP diligence from operating diligence. Source-code ownership, open-source use, product documentation, cloud dependencies and customer-funded work should be reviewed together.

How KAS & Co. Can Help

KAS & Co. helps acquirers, investors and founders run India-linked technology acquisition diligence, structure control transactions, review IP and customer contracts, screen CCI risk and prepare closing documentation. For a focused review before signing a majority acquisition, contact KAS & Co..

FAQs

1. What is different about majority acquisition diligence?

The buyer is taking control, so diligence should test ownership, approvals, customer continuity, employee retention, IP control, filings and operating risk.

2. Does a foreign buyer need FDI review for an Indian software company?

Yes. The buyer should confirm entry route, pricing, reporting, sector conditions, beneficial ownership and any approval-route issue before signing.

3. Should customer consent checks happen before signing?

Yes. Key customer, reseller, vendor and cloud contracts should be screened before signing so consent conditions and timetable risk are built into the acquisition documents.

4. Does every majority acquisition need CCI approval?

No. The answer depends on thresholds, deal value, control rights, group links and India nexus. The analysis should be recorded rather than assumed.

Sources

• RBI - Master Direction on Foreign Investment in India
• DPIIT - Foreign Direct Investment
• Companies Act, 2013 - India Code
• Copyright Act, 1957 - Copyright Office
• Competition Act, 2002 - CCI
• Competition Commission of India - Filing of Combination Notices
• Competition Commission of India (Combinations) Regulations, 2024