Patent granted, now what? The first ninety days for a security, identity, or trust patent

Maintenance fees are the first deadline. The windows open years after issue and close on fixed dates, and the patent lapses if the fee is missed. Your counsel will usually docket them, but the company should hold its own copy of the dates, because counsel changes, small companies change hands, and the person who filed the application is often gone by the time the second window opens.

The second is mail. Within weeks of a grant, owners receive official-looking letters offering to record the patent, register it, publish it, or pay its fees. Some are simply overpriced. Some are fraudulent. The USPTO warns about both. A one-line rule works: nothing about the patent gets paid unless counsel confirms it first.

The third is ownership of the commercial question. In a small company the patent belongs to the inventor emotionally and to nobody operationally. Name one person who will own the next ninety days, and give them the authority to spend a little time and money answering the questions below.

We raise marking because it is the one paperwork question with direct commercial consequences. A company that ships an unmarked product and later wants to license or enforce may find the value of past use smaller than it expected. We never advise on how to mark, and we never advise on enforcement. We make sure the question gets asked before the first shipment, not after.

If you do not ship anything yet, the question still belongs on the list, because the first product, the first OEM build, or the first licensee's product will raise it.

Founders usually want all four. That is fine as an ambition and useless as a plan, because the four jobs pull in different directions. A patent that protects your product is one you want to keep exclusive in your market. A patent you license wants broad, non-exclusive deals in other markets. A patent you sell leaves the company. A patent that supports a raise has to be explained to investors who do not read claims.

The cheap test is a single sentence: this patent exists to do X, for buyer Y, in market Z. If nobody in the company can finish that sentence, the first commercial task is not outreach. It is defining the product the claims protect, in words a non-engineer can repeat.

Security, identity, and trust patents are hard to explain because the inventive step usually sits deep in a protocol, a key-handling scheme, a sensor, or a verification flow. The claims describe that step precisely. They do not describe a product. Somebody has to turn the claims into a named product family, map its components back to the claims that cover them, and write the pitch in the language of the buyer's problem.

A useful exercise is to write a four-beat pitch: the problem the buyer has today, what the product does about it, why it is hard to copy, and what the buyer should do next. If the third beat is the only one you can write, you have a patent and not yet a product.

For this technology the buyers fall into a handful of categories: vendors who would build the claimed method into their own product, OEMs and platform companies who would carry it to their customers, operators who would use it inside their own systems, and standards-adjacent groups who care whether it reads on a specification. Each category buys for different reasons and through different people.

Grade each candidate as Confirmed (someone in that seat told you in writing), Verbal (someone told you in a conversation), or Inferred (you reasoned your way there). An early list that is all Inferred is normal. A plan built on it without saying so is how companies spend a year pitching the wrong buyers.

Run the conversations as validation, not as sales. Share only what is public: the granted patent itself, a plain description, and the product as you now describe it. Anything confidential, including unfiled variants and the roadmap, waits for a mutual NDA, and counsel should see what you plan to share before you share it.

Write down what each conversation confirmed, what it contradicted, and what it left open. At the end of the quarter you should have a product description people repeat back correctly, a short list of buyers graded by evidence, a list of questions for counsel, and a plain statement of what you still do not know.

We would add one more: do not mistake activity for an answer. A listing on a marketplace, a press release about the grant, or a long market report can each feel like progress. None of them tells you who will pay. The test of the first ninety days is whether you can name the buyer, the reason, and the next step, in writing, with the evidence behind each one graded.

Patenture works the commercial side of a granted patent in security, identity, and trust technology. Where nobody outside engineering can yet explain the product, the Patent to Product Read turns the claims and the engineering into a named product family mapped to the claims, a pitch, and a deck your CEO can present without the inventor in the room. Where the product is clear and the market answer is not, the Claim to Market Read comes next. Your patent counsel's access is a condition of every engagement.