Freedom to operate

A freedom-to-operate analysis answers one question: can you sell this product without infringing a live patent someone else holds? Patalyze gives that question a shape. Your product sits on one side, the patent landscape around it on the other, and a mapping between each patent and your product scores the overlap. The patents that read on your product and are still in force are the ones you have to deal with before you ship; everything else falls away.

This is the defensive direction: you start from the thing you are defending and work outward to the patents that could block it. The three steps below run the analysis from your product to a written verdict. If you want the shortest possible path into the product first, see the quickstart.

1. Define product#

Start from the thing you are defending: your product. The Defensive / Freedom-to-Operate workflow knows the shape of the work, so it builds a research database around that product, seeds a patent search around it, and lays out the pages you will read the result on. Give the research a name that pins down the question, such as the product and the market you are clearing it for, so the verdict stays easy to stand behind later. Keep one product, or one tightly related family, per research; a clean scope is what makes the conclusion defensible.

You can add products three ways from the Add menu, depending on how much you already have in hand. Search finds the product by its features and category when it is already in the wider catalog. Crawl pulls it straight from one or more product-page URLs. Upload lets you drop in a datasheet, brochure, or spec sheet directly. However it arrives, Patalyze reads the product's description, files, and images and learns its features: the concrete things each patent claim gets checked against. The richer the material you give it, the sharper every mapping that follows.

2. Filter patents#

With your product in place, gather the patents it has to clear. These come from the global patent corpus, and the workflow has already seeded a first search to get you started. Widen it from there: a boolean search pins down exact terms, assignees, and classifications, while a semantic search pulls in patents that describe the same idea in different words, the ones a keyword search would miss. Add anything promising by number when you already know it. Aim for recall here: it is better to pull a patent that turns out not to matter than to miss the one that does, because the scoring that follows is what separates the real risks from the noise.

Once your product has learned features and the landscape is in place, Patalyze creates mappings in the background: one for your product against each patent you gathered. Every mapping takes the patent's independent claims, breaks each into the elements that must all be present, and judges whether your product practices each one, with the evidence behind every call. The verdicts roll up into a per-claim score and a risk band, so a wall of claim language becomes a number you can sort on. You do not trigger this by hand.

3. Understanding results#

Now read the result on the pages the workflow laid out, working down from the verdict to the evidence beneath it:

• Read the executive summary first. When the analysis is done, Patalyze writes it to the top of a note: a rich-text verdict with live links back to the patents and your product and embedded charts, so the conclusion travels to whoever needs to sign off on it.
• Open the table of patents to check it. Sort by your product's mapping column and the patents it reads on rise to the top, where a Critical band on a live patent is exactly the result you came to find; filter to in-force patents so dead ones, which cannot block you, stop crowding the view. A dashboard gives the same landscape its shape: filings over time, the top applicants, and the classification breakdown show where the risk clusters and who holds it.
• Understand the mappings behind the scores. Open any one to see the patent's independent claims broken into the elements that must all be present, the verdict on whether your product practices each, and the evidence behind every call; override a verdict you read differently or omit an element you have ruled out, and the score updates. This is where a high score stops being a number and becomes a conclusion you can defend.