Freedom-to-Operate Review Before Launching Technology Products in India

A technology product launch can look commercially ready while still carrying patent infringement risk. For a founder, investor or strategic buyer, the practical question is not whether the company has filed its own patents. It is whether selling, importing, using or deploying the product in India may cut across someone else's granted patent claims.

That is the role of a freedom-to-operate review. It is a launch-risk exercise, not a vanity search. Done properly, it helps the team decide whether to proceed, redesign, license, delay, carve out a feature or reserve specific risk in an investment or acquisition document.

Why This Matters

The statutory starting point is the Patents Act, 1970. Section 48 gives a patentee exclusive rights in relation to patented products and processes in India, subject to the Act. For a launch team, that means the risk analysis must be tied to what the company will actually make, use, sell, offer for sale or import in India.

An FTO review is different from patentability or portfolio diligence. Patentability asks whether the company's invention can be protected. Portfolio diligence asks whether the company owns valuable patent assets. Freedom to operate asks whether third-party rights may constrain the product launch. A company can have a strong patent application and still face FTO risk from an earlier third-party patent.

What Counsel Should Review

Start with the product, not the database. Counsel should identify the launch geography, product variants, technical architecture, imported components, manufacturing steps, deployment model and the features that drive revenue. If the product will be sold in India but manufactured abroad, import and sale still need attention.

Then run targeted patent searches. IP India's public patent search system and Patent E-Register are practical starting points for published applications, granted patents, status and register details. They should be used with claim-focused search terms, assignee names, inventor names, classification searches and competitor mapping, not only broad product keywords.

The key legal work is claim mapping. A granted patent is relevant only if its claims read onto the product or process with enough specificity to affect launch decisions. The review should compare claim elements against the product architecture, bill of materials, workflow, process steps, firmware, cloud interactions and supplier-provided components. A title or abstract match is not enough.

Counsel should also review status and timing. Section 53 of the Patents Act addresses patent term, and the Patents Rules, 2003 and IP India's Manual of Patent Office Practice and Procedure support register and prosecution checks. Investors should ask whether the relevant right is a granted patent, pending application, lapsed patent, expired patent or family member in another jurisdiction that does not yet create Indian patent rights.

Finally, test statutory and commercial exceptions cautiously. Section 107A is relevant in limited contexts, but a launch plan should not rely on an exception unless the facts are clearly reviewed.

How Findings Affect The Launch Or Deal

The output should be decision-ready. A clean review may support launch, investment closing or customer rollout. A moderate-risk review may require design-around work, supplier warranties, field-of-use limits, launch sequencing, monitoring of pending applications or a reserve for enforcement correspondence. A high-risk review may require a licence, product redesign or a pause before the company signs large enterprise contracts.

For investors and acquirers, FTO findings should flow into the transaction documents. The deal team may need specific disclosures, patent-risk warranties, indemnities, redesign covenants, supplier pass-through rights or a condition tied to launch clearance.

Typical Timeline and Cost Range

A focused FTO screen for one product feature or product line can often be scoped within 1-2 weeks once technical documents, launch markets and competitor names are available. A deeper review involving multiple product variants, technical claim charts, supplier components or foreign patent families may take 3-6 weeks and may require coordination with patent agents and technical specialists.

The review should be staged: identify live rights, prepare claim charts for the patents that matter, then decide whether the answer is launch, redesign, licence, monitoring or transaction risk allocation.

Common Mistakes

1. Treating a patent search as an FTO opinion. Search results are only inputs; the commercial decision depends on claim mapping, status, geography and product facts.
2. Assuming the company's own patent filing gives launch clearance. Owning or filing a patent does not by itself create freedom to operate against earlier third-party patents.
3. Checking risk after customer commitments are signed. FTO issues are easier to manage before pricing, launch dates, supply obligations and investor warranties are locked.

How KAS & Co. Can Help

KAS & Co. helps investors, acquirers and technology companies structure patent FTO reviews around launch decisions, product facts, claim mapping and transaction risk allocation. For a focused review before an India-linked technology product launch, contact KAS & Co..

FAQs

1. Is freedom to operate the same as patentability?

No. Patentability asks whether your invention can be protected. Freedom to operate asks whether launching the product may infringe someone else's patent rights in the relevant market.

2. When should a startup run an FTO review?

Run at least a targeted review before public launch, large enterprise deployment, major import commitments, strategic investment, acquisition diligence or any launch where a patented technical feature is central to value.

3. Does a pending third-party patent application block launch?

Not in the same way as a granted patent, but it can still matter. Counsel should monitor prosecution, claim scope, publication status and whether the pending application may mature into a right that affects the product.

4. What documents are needed for an India FTO review?

Counsel usually needs product specifications, architecture notes, bills of materials, process flows, supplier details, launch markets, competitor lists, patent search results and any prior patentability or landscape work.

Sources

• The Patents Act, 1970 - India Code
• The Patents Rules, 2003 - IP India
• IP India - Manual of Patent Office Practice and Procedure
• IP India - Public Patent Search
• IP India - Patent E-Register