When Do You Need a Freedom‑to‑operate (FTO) Opinion in India (2026)?

Decision guide: for product managers, in‑house counsel and startups, when to commission an FTO in India for AI, software and telecom products, what the search and analysis involve, typical costs and timelines, and the practical triggers for hiring a patent lawyer.

Freedom to operate india is the question every product team must answer before a commercial launch: can you make, use and sell your product in India without infringing someone else’s granted patent? For AI, software and telecom products in 2026, where IoT, 5G and machine‑learning features often sit on top of patented technical building blocks, the short answer is that you should consider a freedom‑to‑operate (FTO) opinion whenever you plan a commercial launch that implements patented technical features, whenever patent risk affects deal pricing, or whenever an investor demands clearance due diligence. If none of those apply and you are pre‑prototype, a lighter screening will usually do.

This guide gives you the decision rules, the process, realistic cost and timeline ranges, and a clear framework for when to retain counsel.

This article is general information, not legal advice. An FTO is a reasoned legal opinion based on the facts and claim scope supplied, it is not a warranty against litigation. Engage qualified Indian patent counsel for product‑specific clearance.

What is a freedom‑to‑operate (FTO) opinion? Quick definition and legal context

A freedom‑to‑operate opinion is an evidence‑based legal assessment of whether your product, as actually designed and implemented, risks infringing third‑party patents that are in force in the market you intend to enter. The World Intellectual Property Organization frames FTO as a determination of whether a particular action, such as commercialising a product, can be done without infringing valid intellectual property rights of others. In India, the relevant rights are patents granted and in force under the Patents Act, 1970, administered by the Controller General of Patents, Designs and Trade Marks (IP India).

The core mechanic is a comparison between your product’s technical features and the claims of live patents. Patents protect what is claimed, not what is described in the specification generally. An FTO therefore maps each feature of your product against the independent claims of relevant patents and asks: does the product fall within the scope of any claim that is still in force?

A freedom to operate india analysis is a risk‑mitigation tool, not a guarantee. It cannot promise that no one will ever sue you, patents may be pending and unpublished, claims may be construed differently by a court, and new patents grant continuously. What a well‑scoped FTO opinion does is identify the patents that matter, rate the infringement risk, and give you concrete options to reduce exposure before you commit capital to a launch.

When is a freedom to operate india opinion recommended? Decision framework

The decision to commission an FTO is commercial as much as legal. The test is whether patent risk could materially damage your launch, your valuation or your contractual exposure. Below is a practical decision framework you can apply directly.

Choose an FTO when

• Commercial launch of a technical product. You plan to sell in India a product that implements patented technical features, an AI model with a distinctive inferencing method, edge ML in an IoT device, or telecom features that may implicate standard‑essential patents.
• Licensing, M&A, JV or supply agreements. You are negotiating a deal where patent risk affects price, indemnity exposure or representations and warranties.
• Fundraising. Investors require clearance due diligence before a round closes.
• Third‑party modules and SDKs. You integrate external components, libraries or SDKs that may embed patented technology you did not build.

Defer or skip an FTO when

• Pre‑prototype stage. You are at idea stage with no implementable claims and a limited budget, run a light freedom‑to‑operate screening or a patentability check instead.
• Non‑technical product. The offering is pure content or a business method with no implemented technical features, but validate that assumption with a short screening before you rely on it.
• No relevant patents and high risk tolerance. A rare case where the market has no relevant patent estate and you accept the residual risk.

Choose a focused screening when

• Early MVP. Limited claim mapping against three to five competitor patents and a short memo keeps cost low while surfacing the obvious red flags.
• Launch under time pressure. A rapid desk FTO on your core features now, followed by a full opinion post‑launch, buys time without flying blind.

In practice, most teams underestimate how early the right moment arrives. A good trigger rule: once your architecture is stable enough that a competitor could read your feature list and recognise their own patented method, you are ready for an FTO. Waiting until the week before launch removes your best mitigation options, design‑arounds and licensing both take time.

Product‑specific triggers, AI/ML, software and telecom (SEPs)

Different product categories carry very different freedom to operate india risk profiles. The search strategy, the patentability backdrop and the available mitigations all change depending on whether you are launching an AI model, a software platform or a connected telecom device.

AI patent clearance India, AI and machine‑learning products

AI and ML products rarely infringe on the abstract idea of “machine learning”; they infringe on specific technical methods, a particular training pipeline, a model‑compression technique, a distinctive inferencing architecture, or a hardware‑accelerated edge deployment. For AI patent clearance India, the search must therefore drill into method and system claims that describe concrete technical steps, not marketing‑level descriptions of AI capability.

The high‑risk zones in 2026 are edge ML in IoT devices, on‑device inferencing optimisations, and integrations with third‑party foundation‑model APIs where the licensing terms may not insulate you from downstream patent claims. If your AI product ships embedded in silicon or runs latency‑critical inferencing on constrained hardware, assume a real clearance need and budget for it.

Software FTO India and computer‑related inventions

A recurring question is whether software patents exist in India at all. The position is governed by Section 3(k) of the Patents Act, 1970, which excludes a “computer programme per se” from patentability. However, inventions involving computer programmes that demonstrate a genuine technical contribution or technical effect can be patentable in practice, and such claims are examined under IP India’s Guidelines for Examination of Computer Related Inventions (CRIs). This is why a software FTO India cannot assume the field is clear just because “software isn’t patentable”, plenty of computer‑related inventions are granted and in force.

For a software FTO, the analysis focuses on whether granted claims cover the technical architecture you have actually implemented, data structures, communication protocols, resource‑optimisation methods, security mechanisms, rather than the business outcome the software delivers. Non‑patent literature matters more here than in other fields: open‑source prior art, standards documents and academic publications frequently bear on both infringement scope and the strength of any patent you might need to design around.

SEP clearance India, telecom and standard‑essential patents

Telecom is the most distinctive FTO category because of standard‑essential patents (SEPs). An SEP is a patent that a company has declared essential to practising a technical standard, 4G, 5G, Wi‑Fi, video codecs. If your device implements the standard, you almost by definition use the SEP. You cannot “design around” an SEP without abandoning the standard, so SEP clearance India is fundamentally a licensing exercise rather than a pure clearance exercise.

That changes the deliverable. A conventional FTO ends with a clearance rating; an SEP‑exposed FTO ends with a licensing roadmap, an assessment of FRAND (fair, reasonable and non‑discriminatory) royalty exposure, and advice on which patent pools and bilateral licences you will need. Indian courts have, in recent years, actively adjudicated SEP and FRAND disputes, so for any 5G, IoT or connected‑device launch in India, treat SEP exposure as a separate workstream alongside the standard FTO.

FTO vs patentability vs validity, comparison table

These three opinions are often confused, and ordering the wrong one wastes budget. They answer different questions, run at different points in a product’s life, and serve different decision‑makers. The table below sets them side by side.

The roles are complementary. Patentability protects what you own; FTO protects what you ship; validity defends you once a dispute begins. If you are launching a product, prioritise the FTO. If you are filing to build your own estate, order patentability. If you have received a cease‑and‑desist or an infringement notice, you need a validity and non‑infringement analysis immediately.

How a freedom to operate india opinion is carried out, searches, scope and legal analysis

A rigorous FTO follows a disciplined sequence. Understanding the process helps you scope the engagement, control cost and judge the quality of the work you receive.

Step 1, Scoping call and feature breakdown

The engagement opens with a technical scoping session. Counsel works with your engineers and product owners to break the product into its constituent technical features, the elements most likely to read onto someone’s claims. A precise feature list is the single biggest driver of FTO quality: a vague product description produces a vague opinion.

Step 2, Claim mapping and search strategy

Each feature is translated into search concepts and classification codes. The search must cover the patent families that create risk in the Indian market. A robust search scope for freedom to operate india typically includes:

• Indian patents (IN), granted and in‑force rights enforceable in India.
• WIPO / PCT (WO), international applications that may have entered the Indian national phase.
• United States (US) and European (EP) families, because global applicants frequently file parallel protection in India; a US or EP hit often signals a corresponding Indian right.
• National‑phase and priority tracking, identifying which foreign filings have a live or pending Indian counterpart.
• Non‑patent literature, standards documents, open‑source repositories and academic papers, especially critical for software and AI features.

Patent applications in India are generally published on expiry of eighteen months from the date of filing or the priority date, whichever is earlier (subject to any request for early publication), which means recent filings may not yet be visible. A competent FTO flags this blind spot explicitly rather than implying certainty where none exists.

Step 3, Infringement analysis and claim charts

For each relevant patent, counsel constructs a claim chart, an element‑by‑element comparison between the independent claim and your product feature. The analysis asks whether every element of a claim is present in your product (the all‑elements approach). A simplified illustration of claim mapping looks like this:

• Claim element: “a processor configured to perform inference on a quantised model” → Product feature: edge device runs a quantised model on its NPU → Assessment: present; potential read‑on, examine further.
• Claim element: “transmitting results via a cellular 5G interface” → Product feature: device transmits over Wi‑Fi only → Assessment: absent; this claim likely not infringed.

Where a single claim element is clearly absent, infringement of that claim usually fails. Where every element arguably reads on, the patent becomes a red flag requiring mitigation.

Step 4, Legal opinion and risk rating

The output is a written opinion that rates each live patent as high, medium or low risk, explains the construction and non‑infringement arguments available, and sets out mitigation options. For software and AI, the opinion also considers whether a flagged patent is vulnerable under Section 3(k) and the CRI framework, a claim that may be “software per se” is a weaker threat than one with a clear technical contribution.

Costs, timelines and deliverables, India 2026 realistic ranges

Buyers want numbers. The figures below are illustrative market ranges for India in 2026 and vary significantly with scope, the number of patents reviewed, the firm, and whether SEPs are involved. Treat them as rough planning bands, not quotes, always obtain a written proposal from your chosen counsel.

The deliverables scale with the engagement. A screening gives you a rapid red‑flag memo suitable for an early go/no‑go decision. A standard FTO gives you a defensible written opinion, claim charts and a risk register you can show investors and acquirers. A complex or SEP engagement adds a licensing roadmap because, as noted, standard‑essential patents cannot be cleared by non‑infringement alone.

Engagements are typically offered in two shapes: a limited FTO, scoped to named core features and a defined patent set, which controls cost; and a full FTO, which covers the complete product and broader search universe. Many teams run a limited FTO before launch and expand to a full opinion as the product and budget mature.

When and how to hire a patent lawyer for a freedom to operate india opinion

Timing and scoping the retainer well is what separates a useful FTO from an expensive formality.

When to hire in the product lifecycle

Engage counsel once your architecture is stable but before you lock in manufacturing, marketing spend or launch dates, early enough that design‑arounds and licensing negotiations remain live options. For fundraising or M&A, bring counsel in before due diligence opens so clearance is ready when investors ask.

In‑house versus external, and who is qualified

In India, patent prosecution before the patent office is handled by registered patent agents, while litigation and legal opinions are typically handled by advocates; many practitioners are both. FTO work requires the technical background to read claims in your field. Registration as a patent agent is governed by the Patents Act, 1970 and the Patents Rules, and candidates must clear the Patent Agent Examination conducted by the patent office. For AI, software and telecom, insist on a reviewer with genuine domain expertise, claim construction in these fields is unforgiving of generalists.

Billing models and SLA items

• Fixed fee for a defined screening or limited FTO, best for budget certainty.
• Hourly for open‑ended or evolving scope.
• Blended / milestone billing tied to deliverables, search report, draft opinion, final opinion.

Build in scope‑limiting clauses (which features, which jurisdictions, which patent universe), a conflict check before you share confidential technical detail, and clear SLA items: turnaround per stage, update obligations if new patents surface, and the format of the final deliverable.

What to ask in an FTO RFP

1. What databases and family coverage (IN, WO, US, EP) will you search?
2. Who performs the analysis and what is their technical background?
3. Will you provide claim charts and a documented risk rating?
4. How do you treat the 18‑month publication blind spot?
5. How are SEPs and FRAND exposure handled if telecom standards are implicated?
6. What is the fee structure and what triggers additional cost?

Practical risk mitigation steps after an FTO (if red flags are found)

A red flag is not a stop sign, it is a prompt to choose a mitigation. The common options, in rough order of cost and complexity, are:

• Design‑around. Re‑engineer the feature to fall outside the problematic claim. Often the cheapest route if caught early, which is why FTO timing matters.
• Licensing. Negotiate a licence from the patent holder. Essential for SEPs, where FRAND licensing is the expected path.
• Carve‑outs. Launch without the infringing feature, or exclude the Indian market for that feature until cleared.
• Indemnities. Where risk originates in third‑party modules or SDKs, push the exposure back onto the supplier through contractual indemnities.
• Defensive filings. Where you have your own improvement, filing can strengthen a future cross‑licence position.
• Launch staging. Phase the rollout so lower‑risk features ship first while higher‑risk ones are cleared or redesigned.

Each option carries a cost‑benefit trade‑off: a design‑around spends engineering time but can remove the risk permanently; a licence preserves the feature but adds a recurring royalty. The FTO opinion should set out both sides so the business can decide with eyes open.

Sample engagement timeline and checklist (playbook)

A typical standard FTO runs over roughly twelve weeks, though a screening compresses to days. Use this as a planning guide:

• Week 0: conflict check, NDA, scoping call, feature breakdown.
• Weeks 1–2: search strategy built, patent and non‑patent searches run (IN, WO, US, EP).
• Weeks 3–5: relevant patents identified; claim charts drafted for flagged rights.
• Weeks 6–8: infringement and risk analysis; draft opinion circulated.
• Weeks 9–10: mitigation options developed; client review session.
• Weeks 11–12: final opinion, risk register and (if relevant) SEP licensing roadmap delivered.

Pre‑engagement checklist for your team:

1. Freeze a stable feature list and architecture document.
2. List all third‑party modules, SDKs and APIs you integrate.
3. Identify your target launch date and markets.
4. Confirm your risk tolerance and budget band.
5. Decide screening versus full FTO.
6. Run a conflict check with chosen counsel.
7. Agree scope‑limiting clauses and SLA.
8. Define who signs off internally on mitigation decisions.

Key takeaways and recommended next steps

Getting freedom to operate india right is a commercial discipline, not a box‑ticking exercise. The essentials:

• Consider an FTO before commercial launch of any AI, software or telecom product that implements patented technical features, and before licensing, fundraising or M&A where patent risk affects price.
• Match the engagement to the stage, a focused screening for an MVP, a full opinion as the product and stakes grow.
• Treat SEP exposure as a separate licensing workstream for connected telecom and IoT devices.
• Engage counsel early, while design‑around and licensing are both still available.

If you are weighing a 2026 launch, the next step is a short scoping conversation to decide between a screening and a full FTO, and to confirm whether SEPs are in play. Speak with a patent specialist through the Global Law Experts network to get an engagement scoped to your product and budget.

Sources

1. Office of the Controller General of Patents, Designs & Trade Marks, IP India
2. World Intellectual Property Organization (WIPO)
3. IP India, Guidelines for Examination of Computer Related Inventions (CRIs)
4. IP India, Patents (Act, Rules and Office Practice)
5. WIPO Lex, Legislative and Treaty Framework