Patent Annuities: Pay or Lapse Decisions That Track the Roadmap and the Deadlines
Thirty patents come up for renewal, and each one needs a pay or lapse call. Agents read the fee schedules and product roadmap in Box and outside counsel's reminders in Outlook, and IP counsel approves every decision before instructions go out.
Thirty renewal deadlines and a roadmap that does not sit still
Every patent in force carries a renewal fee on a schedule its jurisdiction sets, and every one of those fees is a small decision: keep paying because the patent covers a product that matters, or let it lapse because the product moved on or the company no longer sells in that market. A cycle of thirty patents is a few days of careful reading. The trouble is that the inputs move while the deadlines do not.
The official fee schedules and the product roadmap live in Box, each patent's family, product mapping and decision history sit on a Notion page, and outside counsel's deadline reminders arrive in the IP mailbox in Outlook. The paralegal's review report is a spreadsheet in Google Drive. When the roadmap shifts or a market exit is reversed, earlier decisions have to be revisited one by one, and a lapse that should have become a payment is easy to miss.
Who works in the room
People
IP counsel
Approves every pay or lapse decision, rules on grace-period cases and signs the cycle close-out
Product line leads
Confirm whether a patent still covers something on the roadmap when the mapping is in doubt
IP paralegal
Prepares the annuity review report and sends every instruction to outside counsel
Agents

MycoAnnuity coordinator
Reads each patent's Notion page, the fee schedule and roadmap in Box and counsel's reminders in Outlook, and proposes a pay or lapse decision with its deadline and fee

AdaReport checker
Checks the paralegal's review report line by line against the approved decisions and lists every patent where the two disagree
Google Drive
Notion
RyanCounsel and product liaison
Drafts pay and lapse instructions for outside counsel, and puts Myco's coverage questions to the product line leads
Annuities have their own Kylon room, with Myco as the default agent, so any question about a patent's decision reaches it unnamed. Questions about the review report go to Ada, and anything that needs an answer from outside counsel or a product lead goes to Ryan. Myco reads the Outlook mailbox through a lasting grant its owner approved for this room, and the room guidelines say that mailbox is read only: reminders are evidence, and nothing is filed, flagged or answered from it. When a decision is approved, Myco mentions Ryan in the thread with the patent, the fee and the deadline, and Ryan takes it from there.
A decision cycle, end to end
The annuity policy, with its pay and lapse criteria and its grace-period rules, sits in Google Drive and in the room guidelines. An automation opens each monthly cycle with every patent due in the next ninety days, and each stage stops at a person before anything leaves the team.
- Agent works
- Person decides
- Arrives or gets recorded
flowchart TD
cycle([An automation opens the monthly cycle])
first["<b>Myco</b> proposes pay or lapse for<br>each patent with deadline and fee"]
ok1["<b>IP counsel</b> approves each decision"]
report["<b>Ada</b> checks the review report<br>against the approved decisions"]
roadmap["<b>Myco</b> re-checks patents on a<br>product line that moved or ended"]
correct["<b>IP paralegal</b> corrects it,<br><b>IP counsel</b> confirms"]
coverage["<b>Product line lead</b><br>confirms coverage"]
exit["<b>Myco</b> reopens each lapse made<br>under the reversed market exit"]
decide["<b>IP counsel</b> decides<br>each reopened patent"]
fees["<b>Myco</b> recomputes costs under<br>the revised fee table"]
grace["<b>Myco</b> shifts deadlines only for<br>patents in counsel's batch"]
ok2["<b>IP counsel</b> approves<br>any changed decision"]
batch["<b>IP paralegal</b> confirms the batch<br>against counsel's notice"]
instr["<b>Ryan</b> drafts the instructions<br>for outside counsel"]
sign["<b>IP counsel</b> signs the close-out,<br><b>IP paralegal</b> sends instructions"]
cycle --> first --> ok1
ok1 --> report & roadmap
report --> correct
roadmap --> coverage
correct & coverage --> exit --> decide
decide --> fees & grace
fees --> ok2
grace --> batch
ok2 & batch --> instr --> sign
class first,report,roadmap,exit,fees,grace,instr agent
class ok1,correct,coverage,decide,ok2,batch,sign person
class cycle event
classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712
classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712
classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42| Stage | What happens | Who acts | Who decides |
|---|---|---|---|
| First pass | Each patent gets a pay or lapse proposal from its Notion page, the roadmap and fee schedule in Box and counsel's reminder in Outlook | Myco | IP counsel approves each decision |
| Report review | The paralegal's review report is checked line by line against the approved decisions | Ada | The paralegal corrects the report and counsel confirms |
| Roadmap update | Patents mapped to a product line that moved or ended are re-checked | Myco, then Ryan for the coverage questions | The product line lead confirms coverage |
| Market exit reversed | Every patent set to lapse because of the exit is reopened and re-decided against where its deadline now stands | Myco | IP counsel decides each reopened patent |
| Fee table revision | Costs are recomputed under the revised fee table, and decisions near the policy's cost line are re-checked | Myco, checked by Ada | IP counsel approves any changed decision |
| Grace-period extensions | Deadlines shift only for the patents named in counsel's extension batch | Myco | The paralegal confirms the batch against counsel's notice |
| Close-out | Pay and lapse totals by jurisdiction are tallied from the current Notion pages and instructions are drafted for counsel | Myco, then Ryan for the instructions | IP counsel signs the close-out and the paralegal sends the instructions |
Reversals reopen settled decisions
The hardest change is the one that undoes an earlier call. When leadership reverses a market exit, the patents set to lapse under it are not simply switched back to pay. Each one is re-decided against where its deadline stands now: still open, inside the grace period with a surcharge, or already past. Myco reopens exactly those patents, notes on each Notion page which decision it replaces and why, and leaves every other patent as it was.
Extensions and fee revisions work the same way. A batch of grace-period extensions from outside counsel shifts deadlines for the patents it names, not for every patent in the same country, and a revised fee table can move a patent across the policy's cost line, most often one already paying a grace surcharge. The thread shows each old deadline and fee next to the new one, so counsel decides from current figures.
What the checks catch
- A lapse decision made under the market exit that is still on record after the exit was reversed
- A deadline on a Notion page that disagrees with counsel's latest reminder in Outlook
- An extension applied to every patent in a jurisdiction when the batch named only some of them
- A patent now inside its grace period whose cost under the revised fee table crosses the policy's line
- A review report line that still shows a decision counsel has already changed
What stays with people
- Every pay or lapse decision, approved by IP counsel
- Confirming whether a patent still covers a planned product
- Sending instructions to outside counsel, which Ryan prepares as a draft in Gmail
- Signing the cycle close-out
Integrations in this workflow
Kylon is not an IP management system or an annuity payment service, and it replaces neither. It works across the documents, pages and mailboxes the IP team already keeps, and carries the coordination from one to the next.
- Notion holds a page per patent with its family, product mapping, deadline and decision history
- Box keeps the official fee schedules and the product roadmap
- Outlook is the IP mailbox where outside counsel's reminders and extension notices arrive, read only for the agents
- Google Drive holds the annuity policy and the paralegal's review report
- Gmail carries instructions to outside counsel, each a draft the paralegal sends
- Slack is where product line leads answer coverage questions and post roadmap news
Where to start
Begin with the next quarter's deadlines in one group of jurisdictions. Connect the Notion database that holds your patent pages, point the room at the Box folder with the fee schedules and roadmap, and put the rule that matters in the room guidelines: agents propose pay or lapse decisions, IP counsel approves every one, and no instruction reaches outside counsel until a person sends it.
“A lapse is hard to take back, so every reopened patent gets a fresh decision before its deadline arrives.”
Set it up with your agent
Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.
Set up our patent annuity pay or lapse desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Box, Gmail, Google Drive, Notion, Outlook and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the IP counsel, the IP paralegal and the product line leads. Help me invite them to this Room. 3. Build an Annuity Decisions App with Patent, Country, Decision and Status columns, one record per patent. Fill it from the patents due in the next ninety days using their Notion pages, the fee schedules and roadmap in Box and counsel's reminders in Outlook. 4. Check each proposed pay or lapse decision against the approved decisions in the Annuity Decisions App, the paralegal's review report in Google Drive and counsel's latest reminder in Outlook. List every patent where any two of those disagree. 5. Draft pay and lapse instructions for outside counsel as Gmail drafts, and put coverage questions to the product line leads in Slack. Hold every draft until the IP paralegal sends it, and hold every decision until IP counsel approves it. 6. Write our rules and who approves what into this Room's guideline, so every cycle follows it. 7. After one clean cycle, offer to turn the monthly ninety-day opening into an Automation. Before you start, ask me for our rules one at a time.
Your first company harness. Where humans and agents run your business together.
More Use Cases
View allRecords Retention: A Disposition Cycle Where Every Date Traces to Its Source
Each quarter, every in-scope Box record is dispositioned against the retention schedule, its classification, open legal holds and its own closure date in one Kylon room. Agents walk the records and check the certificate, and the records desk lead approves each write.
Brand Abuse Takedowns: Lookalike Domains and Fake Accounts Handled by Policy
Reports of lookalike domains and impersonating accounts are classified under the takedown policy in one Kylon room, using evidence from X and LinkedIn. Agents propose each disposition and filing, and the brand protection lead approves before anything is filed or sent.





