Software Freelance Contract Red Flags in India: Understanding Liability, SLA, and Exit Clauses

One of my clients recently had a case which I am explaining below and if you are stuck in such similar situation, here is what to do.

Note: Due to attorney-client privilege, I cannot disclose complete case details or identify the actual parties involved. However, I am sharing the essential facts and legal approach so that if you find yourself in a similar situation, you can understand the available solutions and legal remedies.

Two software developers based in Pune — Arjun Mehta and his colleague Sneha Iyer — had been taking on freelance projects steadily for about two years. In early March 2025, they were approached by a mid-sized company operating out of Gomti Nagar, Lucknow, dealing in logistics software solutions. The client, associated with a firm named Prudent TechVentures, sent across a draft service contract that, on first reading, seemed fairly routine. But certain clauses stopped Arjun and Sneha cold.

The contract proposed a liability of three times the fees paid to them for any losses the client suffered due to software bugs. It also granted the client a 15-day termination notice window while denying the developers any right to exit for convenience. And the SLA section demanded bug fixes within four hours for critical issues, eight hours for standard issues, and twenty-four hours for minor ones — with no distinction between response time and actual fix time.

Arjun initially consulted a general civil lawyer in Pune, who reviewed the document but couldn't provide clear guidance on whether these clauses were enforceable or negotiable under Indian contract law. Feeling unsatisfied, Arjun reached out to Advocate Sudhir Rao. The specialised review identified three clauses that were either unconscionable under Section 23 of the Indian Contract Act, 1872, or commercially imbalanced in ways that created disproportionate risk for the developers. Specific counter-drafting suggestions were provided, the SLA was restructured to separate response obligations from resolution obligations, and the liability cap was brought in line with standard industry practice. The contract was renegotiated before signing, saving Arjun and Sneha from significant future exposure.

Advice in Such Cases

Consult with Lawyer: The very basic and important step to start is talk to Lawyer / advocate. You should not hesitate in paying his consultation fee i.e. might be in range of Rs. 10,000 to 50,000 depends case to case. He is helping you in this situation to come out. He is expert in the domain and can help you explain the procedure which you might have never explored. A good lawyer can get the issues resolved much faster than you think.

Get the contract reviewed before signing — not after. Once both parties have executed an agreement, renegotiating unfavourable terms becomes legally and commercially difficult. A pre-signing review takes a fraction of the time and cost compared to resolving a dispute later.

Now, before you act — document everything. Every email, every WhatsApp message, every call record. If a clause's actual meaning gets disputed down the line, that trail is your primary evidence of what was genuinely agreed between the parties.

This category of matter involves procedural and evidentiary nuances around liability caps, SLA enforceability, and asymmetric termination rights that a general practitioner simply may not be familiar with. Engaging an advocate who regularly handles IT and commercial contract work can produce much sharper outcomes during drafting, negotiation, and, if it comes to that, dispute resolution.

Applicable Sections of Law

Several provisions of Indian civil and commercial law directly govern the clauses at issue in a software freelance contract dispute:

• Section 23, Indian Contract Act, 1872: A contract term is void if its object or consideration is unlawful, opposed to public policy, or immoral. Grossly one-sided clauses — such as punitive liability multiples — can be challenged on this ground.
• Section 74, Indian Contract Act, 1872: Where a contract stipulates a penalty for breach, courts award only reasonable compensation, not the full penalty. The three-times-fees liability clause is directly subject to this section.
• Section 16, Indian Contract Act, 1872: Deals with undue influence, relevant where a large company imposes terms on individual freelancers with unequal bargaining power.
• Order 39, Rules 1 and 2, Code of Civil Procedure, 1908: Applicable if injunctive relief is sought to prevent enforcement of an unconscionable contractual term or to preserve status quo during a contract dispute.

Jurisdiction — Where to File the Case

For civil disputes arising from a software freelance contract, the appropriate forum is the Civil Court having territorial and pecuniary jurisdiction over the place where the contract was executed or where one of the parties resides or carries on business. If the contract value falls within prescribed limits, the matter may be filed before a District Court or, for higher-value commercial disputes, before the Commercial Court under the Commercial Courts Act, 2015. And here's the thing — if your contract contains an arbitration clause, disputes may be required to be referred to arbitration under the Arbitration and Conciliation Act, 1996, before approaching a civil court. Always check the dispute resolution clause first. Always.

Limitation Period

Under the Limitation Act, 1963, a suit for breach of contract must ordinarily be filed within three years from the date on which the breach occurred or was discovered, as per Article 55 of the Schedule to the Act. For money recovery arising from a contract, the limitation is similarly three years from the date the sum becomes due. Missing this window can be fatal to your claim. Courts do have the power to condone delay under Section 5 of the Limitation Act, but this is discretionary and requires demonstrating sufficient cause — it's not a safety net you can casually rely on.

Interim Reliefs Available

Several interim reliefs can be sought at an early stage in a civil contract dispute. Under Order 39, Rules 1 and 2 of the CPC, a party can apply for a temporary injunction to restrain the other side from enforcing an unconscionable clause or invoking a penalty provision pending final adjudication. Where there's a real risk that a client may seek to recover amounts under an inflated liability clause, an application for attachment before judgment under Order 38, Rule 5 CPC can protect your interests. Status quo orders prevent either party from altering the factual position. Make no mistake, securing these reliefs early significantly strengthens a party's bargaining position during negotiations or trial.

If You Are the Victim

• Don't sign the contract under commercial or time pressure without legal review. Urgency manufactured by a client is rarely a genuine emergency.
• If you've already signed and the client is now invoking a punitive clause, immediately preserve all written communications, work logs, code repositories, and delivery records to demonstrate what was actually delivered and when.
• Send a formal legal notice through your advocate before the situation escalates to litigation. Many disputes are resolved at this stage.
• If the contract contains an arbitration clause, initiate arbitration proceedings as prescribed — approaching a civil court first without honouring an arbitration agreement can result in your suit being stayed under Section 8 of the Arbitration and Conciliation Act, 1996.
• Keep a contemporaneous log of all SLA-related communications, including tickets raised, response timestamps, and resolution records, as these become critical evidence in any SLA breach dispute.

Documents You Must Keep Ready

• Aadhaar card and PAN card (identity and address proof for both parties)
• Signed copy of the freelance / service contract, including all annexures and schedules
• All email and messaging correspondence with the client regarding project scope, deliverables, and timelines
• Invoices raised and payment receipts or bank transfer records
• Work delivery records — code commits, deployment logs, version control history (e.g., from Git repositories)
• SLA tickets, helpdesk records, and timestamps of bug reports and responses
• Any written amendment or variation to the original contract terms
• Bank account statements reflecting payments received under the contract

What Evidence Is Required?

• Primary evidence: The original signed contract is the foundational document. Any clauses in dispute must be read against the signed text, not drafts exchanged during negotiation.
• Email threads demonstrating the context in which specific terms were agreed, including any representations made by the client during negotiation.
• Technical work logs and version control records that establish what was developed, tested, and delivered — and when.
• SLA response and resolution records to demonstrate whether the developers met their contractual obligations or whether the SLA as written was technically impossible to comply with.
• Payment records to establish the contract value, which directly bears on Section 74 analysis of reasonable compensation versus penalty.
• Expert opinion, if required, from a qualified software engineer or IT professional on whether the SLA timelines were commercially reasonable for the type of bugs described.
• Correspondence showing any waiver or modification of contract terms by the client's conduct.

How Courts Typically Approach Such Cases

Indian courts approaching commercial contract disputes involving IT and software services generally apply the plain meaning rule to contract terms first. But where a clause is shown to be commercially unreasonable or unconscionable, courts rely on Section 23 and Section 74 of the Indian Contract Act, 1872 to limit or refuse enforcement. Frankly, this is well-settled law. In Fateh Chand v. Balkishan Das, AIR 1963 SC 1405, the Supreme Court firmly held that Section 74 applies to penalty clauses and courts will award only genuine pre-estimated loss, not arbitrary multiples. Courts also consider whether the parties had equal bargaining power when evaluating whether a clause should be enforced as written. Asymmetric termination rights and unilateral SLAs often attract judicial scrutiny in commercial disputes.

Timeline of Legal Process

• Step 1 — Legal Notice: Advocate drafts and sends a formal legal notice to the other party. Timeline: 1 to 2 weeks.
• Step 2 — Response or Negotiation: Other party may respond, negotiate, or ignore. Timeline: 2 to 4 weeks after notice.
• Step 3 — Filing of Suit / Arbitration: If unresolved, file civil suit or initiate arbitration as per contract. Timeline: 2 to 4 weeks for filing.
• Step 4 — Summons and Written Statement: Court issues summons; defendant files written statement. Timeline: 2 to 6 months.
• Step 5 — Framing of Issues: Court frames the legal questions in dispute. Timeline: 1 to 3 months after written statement.
• Step 6 — Evidence Stage: Both parties file affidavits, documents, and may examine witnesses. Timeline: 6 months to 1.5 years.
• Step 7 — Arguments: Final arguments by both sides. Timeline: 2 to 6 months.
• Step 8 — Judgment and Decree: Court delivers judgment. Timeline: 1 to 3 months after arguments.
• Step 9 — Execution / Appeal: Decree execution or appeal to higher court if required. Timeline: Variable.

Understanding the Costs

The total cost of a matter like this varies significantly from one case to the next — it depends on the complexity of the dispute, the forum involved, the number of hearings, and the specific facts of your situation. There is no single fixed figure that applies to everyone.

A professional advocate can give you an accurate estimate only after reviewing all your facts and documents in a consultation.

Can the Matter Be Settled Out of Court?

Yes. Most commercial contract disputes are capable of resolution without going through a full trial. Mediation under Section 89 CPC is one option, where a neutral mediator facilitates a negotiated settlement acceptable to both sides. Lok Adalats, organised under the Legal Services Authorities Act, 1987, can take up pre-litigation disputes and disputes pending before courts, and any award passed by a Lok Adalat is final and binding with no appeal. A compromise deed executed between the parties and filed before the court results in a consent decree, which is as enforceable as a litigated decree. And here's why this matters — settlement is almost always faster, cheaper, and less damaging to commercial relationships than full-blown litigation, and in contract disputes between business parties, courts actively encourage it.

Common Mistakes People Make

• Signing without legal review: Signing a contract under deadline pressure without having an advocate examine the terms is the single most common and costly mistake. Clauses that appear standard may not be.
• Assuming industry norms override written terms: What is "standard in the industry" has no legal weight once you've signed a document with different terms. Courts enforce what is written, not what you assumed was meant.
• Ignoring asymmetric exit clauses: A termination clause that gives only one party the right to exit for convenience creates serious commercial exposure. Many freelancers overlook this until they're locked into a project they can't exit.
• Failing to negotiate SLA fix times vs. response times: Agreeing to fix-time SLAs without separating response obligations from resolution obligations is a trap. Four-hour bug-fix windows may be commercially impossible depending on the nature of the defect, the environment, and the resources available — and you'll be in breach the moment you miss one.

Advocate Sudhir Rao, Supreme Court of India