Customer Contract Diligence Before Investing in Indian SaaS Companies
Customer contract diligence is where a SaaS company's revenue story meets the documents that actually bind customers. A strong ARR chart can still hide weak renewals, short termination rights, unsigned order forms, heavy credits or customer terms that do not match the investor presentation.
For VC, PE and strategic investment teams, the practical question is whether the company's customer paper supports durable revenue, clean product control and a credible exit path.
Why This Matters
Indian SaaS companies often grow through a mix of standard online terms, negotiated enterprise agreements, statements of work, reseller-led orders and old side letters. That mix can work commercially, but it creates diligence risk when the company raises capital or prepares for a sale.
The starting point is the Indian Contract Act, 1872, because enforceable obligations, breach, compensation and restraint questions sit inside the customer contract stack. Where customer agreements are accepted through electronic workflows, the Information Technology Act, 2000 is relevant to electronic records and electronic contracting. If customer terms cover software, implementation work, documentation, integrations or commissioned materials, the Copyright Act, 1957 also matters because the contract must preserve ownership and licence boundaries.
The Companies Act, 2013 is relevant where customer contracts include unusually large obligations, related-party arrangements, security, guarantees or board-level approvals.
What Counsel Should Review
Start with the contract population, not the template. Counsel should collect the standard customer terms, signed order forms, statements of work, amendments, renewals, side letters, reseller orders and support commitments for major accounts. The review should identify which version governs each customer and whether execution evidence is complete.
Revenue quality comes next. Investors should compare management's recurring revenue numbers with term length, renewal mechanics, cancellation rights, payment timing, usage limits, price-escalation rights, refund rights and disputed receivables. A customer counted as durable recurring revenue may have a short termination right or a pending implementation dispute.
Transfer and exit flexibility deserve a separate pass. Customer contracts may restrict assignment, merger, change of control, subcontracting or migration of services. A provision that looks harmless during growth can become expensive during an acquisition, especially if a top customer can delay consent or use the moment to renegotiate price.
Counsel should also review product commitments. Service levels, support hours, implementation milestones, roadmap promises, customer acceptance criteria, audit rights, suspension rights and service credits should match how the SaaS company actually operates. If sales teams promised bespoke outcomes outside the standard terms, the investor needs to know whether those promises are isolated or systemic.
Ownership and licence language should be mapped to the product. Customer contracts should make clear that the company retains its platform, background technology, know-how, documentation, improvements and reusable tools. Customer-specific deliverables, feedback rights and integration materials should be defined precisely so that a large customer contract does not quietly limit future product development or transfer.
Finally, review liability architecture. Warranties, indemnities, exclusion of indirect loss, aggregate caps, carve-outs, customer remedies, dispute forums and governing law should be summarized by customer value. The point is not to reject every non-standard term. The point is to understand whether a small number of accounts carry exposure disproportionate to their revenue.
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 how express contractual terms should be read. Paragraph 41 of the official judgment is useful for the limited point that business efficacy cannot be used to contradict clear contractual wording.
For customer contract diligence, that means investors should not assume a court, buyer or counterparty will later reconstruct the commercially sensible answer on renewals, service credits, transfer rights, licence scope or liability. If a term affects valuation, it should be explicit in the executed contract set.
Typical Timeline and Cost Range
A focused red-flag review for an early-stage SaaS company with one main template and a limited set of negotiated enterprise accounts can often be completed within 1 to 2 weeks after the full contract set is available. A deeper investor or acquisition diligence review across major customers, historical templates, reseller orders, side letters and dispute records usually takes 2 to 4 weeks.
Fees should be scoped by number of customer contracts, level of negotiated variation, revenue concentration, assignment review, liability mapping and whether counsel must prepare only an issues list or also draft remediation language.
Common Mistakes
- Relying on ARR without reading the underlying contract terms. Renewal, termination, refund and service-credit clauses can change the quality of reported recurring revenue.
- Reviewing only the latest standard customer terms. Older signed forms, side letters and enterprise amendments may govern the contracts that matter most.
- Leaving transfer restrictions until exit diligence. Assignment and change-of-control language can affect deal structure, customer communication and buyer leverage.
How KAS & Co. Can Help
KAS & Co. helps investors and Indian SaaS companies review customer contract portfolios for revenue quality, transfer risk, ownership language, liability exposure and transaction readiness. For customer contract diligence before an investment or acquisition, contact KAS & Co..
FAQs
1. Which customer contracts should investors review first?
Start with top revenue accounts, long-term enterprise customers, contracts with unusual pricing or credits, reseller-sourced customers, disputed accounts and any contract that needs consent for assignment or change of control.
2. Does a signed order form prove recurring revenue quality?
No. A signed order form helps, but diligence should also test the governing terms, renewal rules, cancellation rights, payment history, service commitments and any customer-specific amendments.
3. Should customer contract diligence cover product ownership?
Yes. Customer terms can affect platform ownership, deliverable rights, feedback use, integration work and restrictions on future development. Those points are material for SaaS valuation and exit planning.
4. When should founders prepare customer contracts for diligence?
Founders should organize and review customer contracts before institutional fundraising or sale outreach. Early cleanup gives the company time to fix missing documents, inconsistent terms and consent issues before leverage shifts.
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