Patent Pilot · Prosecution & litigation
Hear the rejection before the examiner writes it.
Pilot is an examiner sounding board for attorneys. It reads your application against millions of USPTO outcomes, tells you which rejections it would draw and why, and helps you shape the claims and the response. When it is time to enforce, it finds infringing products and builds the evidence-of-use chart you can send.
Click any step to jump to it
The problem
Prosecution got more adversarial, and enforcement is slow to build.
FY2026 production quotas pushed examiners toward boilerplate rejections, capped interviews, and ended AFCP 2.0, while RCE and appeal fees climbed. And when a patent finally issues, proving infringement still means weeks of manual product hunting and claim charting. You're asked to manage both on budgets that don't forgive wasted effort.
Office Actions increasingly arrive as copy-pasted, boilerplate rejections that don't engage your claims, and the next round is hard to see coming.
Pilot predicts the rejections your filing is likely to draw, §101 through §112, with the reasoning behind each, so you engage the real issues instead of the boilerplate.
With one compensated interview hour, AFCP 2.0 gone, and RCE fees up as much as 43%, every avoidable rejection eats a fixed-fee budget.
Pilot forecasts the rejections a filing is likely to draw and flags §101 exposure by Art Unit, so you draft around them before the first action.
When a client asks who is infringing, the answer still takes weeks of manual product hunting and claim charting.
Pilot searches the market for products that read on your claim, scores each element by element, and assembles the evidence-of-use chart for you.
In prosecution
Forecast the rejection, then plan the response.
From the application you're shaping to the Office Action on your desk, Pilot reads the case against millions of USPTO outcomes and the full prior-art record.
Office Action response
See the rejection before it arrives.
You're shaping claims for a filing, or staring at a fresh Office Action. Pilot reads the application against millions of USPTO outcomes and tells you which rejections it is likely to draw, §101 through §112, with the reasoning behind each. You draft around the weak spots instead of finding them on the next action.
- Predicted §101 / §102 / §103 / §112 rejections, scored
- The reasoning and claim language behind each risk
- EPO Articles 52 / 54 / 56 / 83 / 84 for European filings
- A response posture before the first action lands
- Connects to Draft to turn each suggestion into a claim edit
Prior art, every source
One search across patents, papers, and the web.
When you need the art that reads on a claim, Pilot searches USPTO, EPO, and Google Patents internally, and reaches the open web and non-patent literature behind security layers that keep your IP from leaking. Every reference is mapped against your claim elements in a heat map, so you see which limitations are exposed and which references to cite or design around.
- USPTO, EPO, and Google Patents searched internally
- The open web* and non-patent literature* added in one pass
- Element-level heat map across claims and sources
- Severity score, reasoning, and one-click add to an IDS
* External searches run behind security layers that prevent IP leakage. Every other search stays internal.
Connects with
Never get surprised by an IDS fee.
IDS preparation lives in Toolbox, and Pilot plugs straight into it. As disclosure obligations pile up across a portfolio, Pilot tracks the cumulative references per application, shows the fee tier you are in, and projects what the next batch of citations will cost before you file, so the disclosure call is a budget call you can defend.
- Cumulative reference count per application
- Current fee tier and the next threshold
- Projected cost before you add references
- Filing history in one place
IDS preparation and SB/08 filing run in Toolbox; Pilot supplies the references and the fee picture.
In litigation
Find who infringes, build the evidence, and keep watching.
When it's time to enforce, Pilot turns a patent into a list of accused products and a claim chart you can send, then keeps watching for new conflicts long after the matter is open.
Infringement audit
Find the products that read on your claim.
Enforcement starts with a question: who is infringing? Pilot takes your patent, breaks the claims into limitations, searches the market for candidate products, and scores each one element by element. The War Room lays the claim tree beside the evidence, so you see which products actually read on the claim and which to set aside.
- Automated product discovery across marketplaces and the web
- Claim tree mapped to per-product evidence
- Match score and infringement level per candidate
- Exclusion rules for licensed or owned products
Evidence of use
Export a claim chart you can send.
When a product reads on the claim, Pilot builds the evidence-of-use chart litigators actually use: each limitation in the left column, the verbatim product evidence and its source in the right. Every quote is grounded in real product text, never fabricated, and it exports to DOCX ready for a demand letter.
- Two-column limitation-to-evidence mapping
- Verbatim quotes with source locators
- Coverage marked met, disputed, or not met
- Export to DOCX, PDF, or CSV
Connects with
Get alerted the moment a conflict publishes.
Pilot keeps searching after the matter is open. It re-runs your prior-art and infringement searches on a schedule against newly published patents and non-patent literature, and notifies you the moment something conflicts with a patent you are watching. The watch list works while you do not.
- Scheduled re-searches across newly published patents and NPL
- Per-patent watch lists across your portfolio
- Conflict and infringement alerts routed to you
- A documented trail for every new reference
Monitoring runs on Scout's prior-art search; new conflicts surface as alerts in Pilot.
The outputs
The deliverables you actually want to see.
Concrete artifacts you can put in front of a partner, a client, or an opposing party. Not another dashboard to interpret.
Office-action forecast
The §101/§102/§103/§112 rejections a filing is most likely to face, with the reasoning, before you file.
Prior-art report and heat map
Patents, papers, and web references mapped against your claim elements, ranked by threat.
Evidence-of-use claim chart
A litigation-ready, two-column claim chart with verbatim product evidence, exportable to DOCX.
Who it's for
Built for both sides of the patent's life.
Prosecution associates
Respond with the data partners expect, without the 40-hour research dig that flat fees no longer pay for.
Partners & practice leads
De-risk fixed-fee work and set a prosecution strategy your team can defend to the client.
Litigation & enforcement teams
Go from "who infringes?" to a defensible evidence-of-use chart without a month of manual claim charting.
In-house IP counsel
Forecast prosecution outcomes and scope enforcement across a portfolio before you commit outside-counsel spend.
FAQ
Common questions.
Yes. The same product forecasts rejections and plans responses during prosecution, then finds infringing products and builds evidence-of-use claim charts when it is time to enforce.
From public USPTO prosecution data across millions of applications and Office Actions, a multi-source prior-art search (USPTO, EPO, Google Patents, web, and non-patent literature), and product data gathered from the open market for infringement work.
Every quote in an evidence-of-use chart is taken verbatim from real product text, with its source. Pilot never fabricates a citation; if it cannot ground a limitation, it marks it unmet.
No. Pilot gives you the patterns, the odds, and the evidence; the strategy call stays yours. It just makes that call defensible to partners, clients, and opposing parties.
No. Under our zero-data-training governance, your applications and client data are never used to train models.
Work the whole lifecycle with Pilot.
Forecast your next Office Action, or build the claim chart for your next enforcement matter.