Your product uses the patent and your claims reach three other markets: what do you do?

Engineers read their own patents through the product they built, which can make the claims seem narrower than the language is. A claim to a method of binding a credential to a device, for example, may not name the kind of device. Your product might be a workforce authentication app; the same claim language might also describe a point-of-sale terminal, a vehicle key system, or a medical device that has to verify its operator. Whether it actually reaches those products is your counsel's call.

We map reach in three columns: what the claims require, the product categories that would meet those requirements, and which categories your company serves today or plans to. Whether a given product actually falls within a claim is a legal question for counsel. The map's job is to give counsel the right list of candidates to look at.

The obvious conflict is a licensee who competes with you. The less obvious ones do the damage: a licensee who sells to your largest customer and will now be in the same procurement meeting; a partner whose contract gives them rights you forgot about; a roadmap item nobody has announced that would put you in the very field you just licensed away; or an old license with a most-favored-licensee clause that changes your terms for everyone.

A good screen is a table, not a judgment call. Each candidate gets a row, each conflict type gets a column, and each cell gets an answer and an evidence grade. The roadmap column needs a straight answer from your own product leadership, and the existing-license column needs counsel.

Field-of-use licensing is the usual tool for containing that risk. The license is drafted to grant rights only within the defined field, so that a licensee in industrial controls gets nothing in banking. The definition of the field is where the risk lives, and drafting it is your counsel's work. Our job is to bring counsel a clear commercial description of each field, written from how the market actually buys, so the definition matches reality.

The first deal in a new field often starts smaller than a full license: an evaluation license, an option, or a limited first field that expands once the licensee ships. In our experience buyers who are unsure prefer a small first step. AUTM's survey of university licensing shows option agreements growing; treat it as a direction, not as evidence about your buyers.

This is why a company that already ships the technology has an advantage it rarely uses. You can show the engineers a working implementation, show the product people what customers do with it, and give the lawyers a clean picture of what you own. A lone inventor can do none of that. Your product is your best licensing material, provided you share it in a way that does not hand a future competitor your roadmap.

This example is invented for this page. It describes no client, product, or patent.

The three fields are car rental counter check-in, age verification for regulated online retail, and building access for secure facilities. The screen removes the first: a large rental platform turns out to be a customer of the company's biggest bank client, and the bank's procurement team would read a license there as the company entering travel. The second survives with one flag: the company's roadmap has a soft plan for retail age checks, so product leadership has to decide in writing whether to give that field up. The third survives cleanly: no customer overlap, no partner rights, nothing on the roadmap.

The result is a licensee ladder for building access, a decision memo for retail age checks, and a written note that rental check-in is off the table and why. Nobody has been contacted yet, and the company already knows which conversations are safe to have.

The order matters. Companies that contact licensees first and screen later find their conflicts in the worst possible way, in a customer's email or a partner's lawyer's letter. Companies that screen first can approach each licensee with a structure that already protects their own business, which also makes them more credible in the room.

None of this is assertion. Licensing reach you will never use, to companies who want to build with it, is a commercial deal between willing parties. If a candidate's response is that they would rather fight than license, that is a separate conversation for counsel and outside this work.

The commitment that surprises owners is relationship management. A licensee in another field will have questions, want updates, and sometimes ask for help. Somebody has to own that, and it should not be your sales team, whose job is your own market. Decide who owns it before the first deal, even if the answer is that the work is contracted out.

Patenture does this work for security, identity, and trust technology as the Licensing Reach Read: a claim reach map, a conflict screen against your customers, partners, roadmap, and existing licenses, a license structure for each opportunity, a ranked licensee ladder, questions for patent counsel, and a table of what the read did not settle. The Licensing Program follows where you want the outreach run for you. Patent counsel drafts and closes every license.