Patent Product Taxonomy: Revenue Behind Filing Decisions

Patent counsel justify filings to people who think in product lines and revenue. The committee that approves a filing budget runs on revenue reports, while the docket underneath every recommendation is organized by technology category. Each side is working from its own map of the company, and counsel translate between the two before every review. The translation means knowing how the business reports its segments and what each product line inside those segments earns, then placing the invention among them convincingly enough to hold up under questions from finance. A patent product taxonomy does that translation ahead of time, for the whole account, with the revenue already attached.

ArcPrime now generates a product taxonomy for every account. Filing arguments carry further with the people who approve them when they name the product line they protect and the revenue behind that line, so the platform builds that map first and keeps it current on its own.

What is a patent product taxonomy?

The taxonomy is a tree with two layers. Business segments sit at the top and the product lines inside each segment sit underneath, with every node carrying a revenue figure. On a public company account, the top layer follows the reportable segments in the company's own annual report, so the revenue at that layer is cited from the report itself. A general counsel reading a patent product taxonomy recognizes the structure because it mirrors how the company describes itself to investors.

Product lines within each segment come from research over the company's product pages and analyst coverage. Their revenue figures are estimates, held to one hard constraint: the children of a segment never sum past the total the parent reports. Tying every child estimate to a parent figure the company itself published keeps the whole tree inside numbers the business has already stood behind.

Every figure in the tree, reported or estimated, carries cited sources surfaced in the interface, on the figure itself. An estimate that cannot show its sources is not worth putting in front of a finance partner.

Private companies report no segments, so those accounts get a sensible product area breakdown in the top layer instead. The shape of the tree stays the same.

The tree is read only. It regenerates comprehensively every six months, so product lines appear when the company starts shipping them and drop away when a divestiture closes, with no reconciliation work landing on counsel in between.

How does a product taxonomy change filing recommendations?

Every new disclosure gets weighed against the product tree. When ArcPrime recommends a filing, the recommendation names the product line the invention protects and states that line's revenue, framed as core or adjacent to the business.

In a budget review, that framing answers the two questions a general counsel or finance partner asks first: which product does this protect, and how much does that product earn. Counsel still make the call on whether to file. The evidence behind the call no longer has to be assembled by hand from a segment report and a product page before each meeting.

Teams that rank incoming disclosures with a filing score get a second signal here, denominated in revenue instead of technical strength. The two signals together describe a candidate filing the way the business will evaluate it.

The revenue context helps most on the disclosures adjacent to the core business, where the judgment calls are hardest. An adjacent product line with real revenue behind it can still justify a filing, and the tree gives that judgment a stated commercial basis a committee can weigh. The same commercial logic extends past new filings. A continuation recommendation aimed at a product line with substantial reported revenue reads very differently from one aimed at a line the company is winding down. That difference is visible in the tree before any budget is committed.

How is a product taxonomy different from a technology taxonomy?

ArcPrime accounts already carry a technology taxonomy, and the product taxonomy sits beside it as a second lens on the same assets. The technology taxonomy answers what field an asset is in. The product taxonomy answers what that asset ships in. A patent attorney evaluating claim scope needs the first answer, while a chief financial officer reading a budget line needs the second.

Through the technology lens, a portfolio shows clusters of technical depth by field. The product lens shows which revenue is heavily defended and which product lines carry thin coverage relative to what they earn. Assets protecting products the company no longer sells stand out the same way. Portfolio management runs better on both views together because each lens surfaces what the other cannot.

A technology cluster that looks impressive on its own terms may map to a product line earning very little, while a modest cluster may sit under the segment that carries the company. Counsel who can move between those views in one platform spend the meeting on the strategy itself.

Where to see it

The patent product taxonomy is live in every ArcPrime account now, with cited sources attached to every figure. Patent counsel who want to look at their own company's tree, with its segments and product lines already mapped, can book a demo and walk through it on a live account.