Choose patent AI by whether it is a workspace with evidence, jurisdiction handling, matter records, and human final review—not by who writes the prettiest paragraph. Fluent drafts are available almost anywhere. What splits practice tools is whether that draft is anchored to source passages, stays inside one matter, and is signed off by a person.
Humans own claim scope and response strategy. The criteria below are a pre-purchase checklist. They do not promise patentability or allowance.
Series map: Patent AI practice guides (I0).
General LLMs are useful for draft sketches, summaries, and translation outlines. In patent matters, four practice risks keep showing up:
This is not an argument against using AI. The question is whether the product is built around those four risks.
The market also splits along a real buying axis: Word-centric plugins versus browser matter workspaces. Both can be legitimate; they are not the same job. For shortlisting, four buckets are enough—named once as examples, not as a ranking.
| Bucket | Typical job | Example (once) |
|---|---|---|
| Browser drafting / prosecution workspace | Interactive draft + OA workflows | Solve Intelligence |
| Patent intelligence + drafting | Claim charts, invalidity/infringement, plus drafting | Patlytics |
| Word-centric drafting / prosecution | Attorney stays in Word; draft + prosecute | DeepIP |
| Established search / IP platform | Search, families, portfolio | Questel |
| Matter workspace | Prior-art compare + spec + review + audit + jurisdiction convert in one matter | Patenty |
The seven criteria below do not crown a winner. Any vendor can be run through the same 30-minute protocol.
Why it matters. Prior-art judgment is not “is this document similar?” It is which element maps where. A one-line similarity score is not practice evidence.
Check for:
“AI says similar” alone is close to a fail. The matrix itself is unpacked in element-by-element prior art (I2) (upcoming).
Why it matters. Drafting a claim in chat A and pasting the specification into chat B is how element IDs, defined terms, and dependencies drift.
Check for:
If paste-between-chats is the normal path, you effectively bought two systems.
Why it matters. Firms and in-house teams eventually ask who finalized a phrase. A final file with no history breaks the audit.
Check for:
Fluent rewrite is less important than reproducible change history.
Why it matters. If filing drafts and office-action work live in different tools or chats, cited passages and claim history must be rebuilt from scratch.
Check for:
Before/after checks live in the office-action response checklist (I3) (upcoming). Outsourcing response strategy to the model is not the premise.
Why it matters. Foreign-filing quality is not “does the English read well?” It is whether limiting language, numbers, dependencies, and figure references still line up 1:1 with the source.
Check for:
Do not invent “X% of conversions drop a number.” Omission types and a short review protocol are covered in US/PCT translation omissions (I4) (upcoming).
Why it matters. Specifications, prior art, and client materials are sensitive. Marketing copy matters less than what the policy documents say.
Ask the vendor (do not assume; treat this as a question list):
This article does not assert any vendor’s security posture or training practice. It only fixes what to verify before matter data goes in. For Patenty specifically, confirm the live site FAQ and policy pages at evaluation time; do not rely on second-hand summaries.
Why it matters. Messaging that implies auto-file, automatic patentability calls, or submit-without-review is a practice and ethics red flag.
Check for:
People own the final call on claim scope and response strategy. Tools only accelerate that judgment.
On any demo or trial, run one sample invention through the steps below. The protocol is brand-agnostic.
| Step | Do this | Pass signal |
|---|---|---|
| (a) | Split the invention into ≤5 elements | Elements persist inside the matter |
| (b) | Open 1–2 prior-art passages from a cell | Cell → source passage opens |
| (c) | One independent claim → spec draft | Continues in the same matter |
| (d) | Plant one intentional error; fix it; inspect the diff | Change + contributor remain |
| (e) | Open training / security policy pages | You leave with document links and wording |
Items that fail are not “coming later in the UI.” Treat them as holes in today’s workflow.
Here is only how the seven criteria can be checked inside a Patenty matter workspace. Competing brand names are not re-listed.
Screen evidence is fastest in a shared demo. The goal is not a feature dump; it is whether protocol steps (a)–(e) can be reproduced in one matter.
If your team is evaluating vendors, send the 30-minute protocol as written. To see the same judgment recorded in a matter workspace, request a product / plans demo. Filing and claim scope remain the attorney’s responsibility.