The objective part is narrow

A sliver of drafting quality is truly objective: the mechanical layer a rules-based proofreader checks — antecedent basis, whether each claim term appears in the spec, reference-numeral consistency, claim numbering. Regex and rules; a term has antecedent basis or it doesn't.

That's the floor, not the ceiling. Above it the judgment returns: whether the conventions are applied comprehensively, whether the disclosure truly enables the claims, where the right claim scope sits. Reasonable experts argue, and no proofreader can score it.

Quality and business value are different axes

Technical drafting quality is necessary, and we hold our work product to the standard of the great portfolios — the Qualcomms, Salesforces, and Microns of the world. But meeting that bar is about how the document is built, not about what the underlying right is worth. Business value turns on different questions: what you chose to claim, whether it reads on the product and on where competitors will go, and whether it holds up when tested. Excellent drafting is the price of admission — it doesn't, on its own, tell you the patent is worth anything to the business.

So grading the drafting tells you whether the work is good. Whether the patent has business value, you learn by watching it perform.

A patent performs every time it's scrutinized

And it gets scrutinized long before the courtroom. The inventors' technical review: does the spec actually describe how the thing works? The business review: do the claims read on the product and on where a competitor would design around? Prosecution: how many Office actions to allowance, on what grounds, and did the spec support amending toward novelty without surrendering scope?

The enforcement test may never come — which is exactly why weak patents hide — but the earlier tests almost always do, and they're just as telling. Performance isn't a far-off verdict; it's observable from the first read forward. And it's where business value shows up: a claim set earns its keep at the business review or fails quietly; a spec proves itself in prosecution or forces you to give away scope.

But performance is a lagging indicator

Here's the catch. Performance only reveals itself under scrutiny — much of it years downstream. So at the one moment you can shape the outcome, drafting time, you're blind to the very thing you're optimizing for.

The way to optimize a lagging indicator is to draft to the leading indicators that predict it. For patents, those already exist, in public: the prosecution record. How the relevant art unit reaches allowance, which rejections recur, which claim structures and amendments survive, where §101 and §112 cluster by examiner. In aggregate, that's the closest thing to a forward-looking signal of how a new draft will perform.

Drafting to the evidence

This is where Paximal is built to shine. We can feed USPTO prosecution data back into the drafting system, so each application is shaped by what actually gets allowed — by which art unit, against which art, through which amendments — instead of written in a vacuum and graded after the fact. Prosecution-aware drafting turns performance from a verdict you wait for into an input you design against.

And we hold to the standard we set, by publishing the outcomes. Across our early accelerated-examination cohort, most reached allowance within a single Office action, with no §112(a) enablement rejections and amendment-ready specs — at roughly four hours to filing-ready. "Born Strong™" isn't only about how the document reads; it's a measurable performance profile. Schedule a demo to see it on your own matters.