How we work

Judgment you can audit.

Every claim we make carries an evidence grade, every deliverable ends with what it did not settle, and every finding is validated with the people who would buy the technology before it reaches your board. One senior operator, a named bench of counsel and specialist partners, and your patent counsel in the room.

First

Claims first.

The highest-value hour is reading the granted and pending claims against the use cases being pitched. A single limitation in an independent claim can kill a use case; a single pending claim can be the most valuable open item in the company. Nothing else starts until the claim explainer is written.

Then

From claims to a thing someone can picture.

Between the claim analysis and the market work there is a stage most firms skip: deciding what the product is. A claim set describes a mechanism. A buyer needs a thing with a name, components, a form factor where it is hardware, and a sentence that says why anyone would want it. We write that before we size anything. Every market question after it is a question about a product, and nobody can validate a mechanism with a buyer.

For a company with no chief product officer this stage is its own read, the Patent to Product Read. For a company that already has the product defined, it is a week inside the Claim to Market Read.

How the Patent to Product Read works.

Then

Six workstreams, run in concert.

The six workstreams run in concert, not in sequence, because a late finding in any one of them invalidates the others: a competitive finding undoes a locked use case, a regulatory gate undoes the sizing, a real price undoes the revenue model. The recommendation comes last and only last.

Claim to capability

The granted and pending claims read against what the technology can actually do, so every use case that follows has a claim basis or is marked as a roadmap item.

Use-case inventory and scoring

Every candidate use case scored on problem fit, buyer plausibility, willingness to sell, and the regulatory or revenue route, then tiered, with the bottom tier killed in writing.

Market gap and bottom-up sizing

The gap the top-tier use cases fill and an order-of-magnitude, bottom-up size for each, built from counts and prices rather than a top-down share of a published market number.

Competitive landscape and honest moat

Who already sells into the use case, how they would respond, and what the claims actually protect, written as a moat read a board can trust because it marks its own weak points.

Regulatory and legal gating

The certifications, standards, and procurement rules that gate each use case, and the questions patent counsel should answer before the continuation is drafted.

Business model and partner ladder

The pricing path, the licensing and OEM options, and a ranked ladder of the partners and licensees who fit, validated with the people who would buy.

Every deliverable

The standards every deliverable meets.

Claims first

The highest-value hour is reading the granted and pending claims against the use cases being pitched. A single limitation in an independent claim can kill a use case; a single pending claim can be the most valuable open item in the company.

A fixed rubric

Every candidate use case is scored on problem fit, buyer plausibility, willingness to sell, and the regulatory or revenue route, then tiered. A use case with no claim basis is a roadmap item, not a use case.

Evidence grades on every claim

Every factual statement carries a grade: confirmed by a public record, verbal from a named person, or inferred by the analyst. The grade distribution is published in an appendix. A document that marks its own weak points is the one a board trusts.

What this did not settle

Every deliverable ends with the open items and the single cheapest action that closes each one. The report becomes a work plan.

Every deliverable, by name.

Confidentiality

A mutual NDA and a written annex, before intake.

Every engagement starts with a mutual NDA and a written data-handling annex: what we receive, where it is kept, who sees it, and the deletion certificate you receive at close. Counsel can review the annex before intake.

What the annex covers

  • What we receive, and the rule that claim language and unfiled variants wait for the signed NDA.
  • Where it is kept, and who sees it: one operator and the named specialist partners the engagement needs, each under the same terms.
  • How long it is kept, and the deletion certificate you receive at close.
  • Counsel's review of the annex before intake, and counsel's access as a condition of the engagement.

Counsel in the room

Patenture is not a law firm. The claim explainer and the counsel question list are commercial analysis; claim construction, validity, and prosecution strategy stay with your patent counsel, whose access is a condition of the engagement.

See it on your own patent.

Twenty minutes is enough to tell which read fits, or whether none does yet.