Continuation Drafter
Continuation claims, drafted on your own machine
A specification and the filed parent claims go in. Drafted continuation claims come out, with their defects already flagged, so you start from a marked-up draft instead of a blank page.
Free. Runs locally through Ollama, or through your own provider key. Nothing to activate.
Numbers you can check, not logos
Every other tool in this category proves itself with customer logos and testimonials. This one has none, so it proves itself the only way that is honest for a new tool: by publishing the method and letting you disagree with it.
Drafting quality
Wall-clock, a separate measurement
The timed runs are a subset: 15 of the 29 models, all remote, so local runs on your own hardware will be slower. This measures how long the tool takes, not how much time it saves you: that is a different claim, we have not measured it, and so we do not make it. The method, and what it does not tell you.
What it actually does
Three things, and it is honest about which of them is solid.
Drafts
Reads the specification and the parent claims, then drafts continuation claims aimed at what the disclosure supports beyond the parent's scope.
Critiques
Flags per-claim 112(a) and 112(b) defects, each with a proposed fix. In our own testing this was the most useful thing it produced.
Scores
Rates drafting craft across support, definiteness, form and differentiation. Read the spread rather than the rank: a single AI judge cannot separate near-equal drafts, and we say so on the benchmark page.
Twenty-nine models, ten real patent families, one table
We ran the same ten parent and continuation pairs through every model we could host, and the interesting gap was not the one we expected.
| Your machine | Model | Index | Corpus drafted |
|---|---|---|---|
| A server with 512 GB of memory | glm-5.2 | 88.3 | 10 of 10 |
| A workstation with 64 GB | gemma4:31b | 79.8 | 9 of 10 |
| A desktop or laptop with 32 GB | gemma4:26b | 65.0 | 10 of 10 |
| A laptop with 16 GB | gemma4:12b | 62.9 | 9 of 10 |
The gap between memory tiers is larger than the gap between open and closed weights. A firm running the top row sits about 3.3 points behind the strongest closed-weight model measured, with nothing leaving the building. How this was measured, and what it does not tell you.
And then it is back in Word, where you actually work
The drafted claims are text. One command puts them in a document you can edit, which since 2024 is the format the USPTO expects for the description, claims and abstract: filing those in any other format carries a surcharge.
Your claim numbering is preserved exactly as drafted and never renumbered, since a continuation's claims are commonly numbered on from the parent. LaTeX works too. The exported file carries the maturity notice inside it, because an exported document gets read by people who never saw the terminal that made it: it is a working draft for you to edit, not a submission.
Where your specification goes
On the local path, inference runs on your hardware and the specification is not transmitted anywhere. That property belongs to the local path, not to the tool as a whole: point it at a remote provider and the specification reaches that provider, which suits published material and is a decision you make per matter for anything unpublished.
Local inference is not unique to this tool. What is unusual is the shape: a binary you download and run today, rather than a deployment behind a sales cycle and a security review.