On the day it’s built, a landscape is right.The next day, it starts to drift.
“The field doesn’t wait: competitors file, new players show up, a technology suddenly speeds up.”Dilip Shrestha · Technical Account Manager
Competitors
A batch of filings in an area they never touched. Often the first public sign of a new strategy, long before a press release.
New players
A startup, a supplier, a company from another industry, filing in your domain for the first time. Easy to miss when nobody is looking.
The technology
An early, slow technology can start improving fast. A mature one can flatten out. If you made a call on it six months ago, you want to know.
Every quarter, someone…
The same work, on a schedule you pick.
You don’t reopen anything. The update is waiting in the Monitoring tab.
What you and Dilip set up together
Pick the project
One you already have, recent or older. Dilip checks it’s ready: datasets with clear names and the saved filters you rely on.
Choose the rhythm
Monthly is the usual start. Weekly for fast-moving fields, quarterly for slower ones.
Set your questions
A scheduled Deep Dive asks the same question on every run, across the datasets you pick. For example: “What has this competitor changed in its technical focus since the last run?”
Pick the first run
The earliest is usually tomorrow. Dilip shows you where the results land and what to read first.
On the Strategic workflow, Dilip also sets up TRL × TIR tracking, so you see your technologies move between Monitor closely, Fund, Phase out and Ignore / watch over time. On the Research plan you get dataset monitoring and scheduled Deep Dives.
- 01One project you’d like to keep alive
- 02One question you’d want answered again every month
Questions we often get
Which rhythm should I pick?
Monthly is the usual starting point. Use weekly for fast-moving areas and quarterly for slower ones. Longer gaps mean more new patents pile up per run, so each run is heavier.
Can I use it on a project I built months ago?
Yes. Monitoring works per project folder, old or new. It works best when the folder is tidy: saved datasets with clear names, useful saved filters, and LLM-Filters where you need them.
When does the first run happen?
On the first run date you pick. The earliest is usually tomorrow.
How fast are the results?
Not instant. Runs are queued and processed in the background. Large projects take longer, and results that depend on an LLM-Filter wait until that filter has run.
Where do I see the results?
In the Monitoring tab of your project. Each scheduled Deep Dive gives one result per dataset after every run.
Can I pause it?
Yes. Disabling stops future runs and keeps all past results, and you can switch it back on later. Deleting removes everything linked to it, including TRL × TIR versions and Deep Dive results, so if in doubt, disable.
Why don’t I see TRL × TIR in my project?
It needs the Strategic-level Agentic Workflow, with an Agentic Chat file holding a clear Problem Statement in the folder. Without it, you still get dataset monitoring and scheduled Deep Dives.
Does TIR tell me which technology will win?
It gives a strong direction, not a guarantee. In the docs’ words: “TIR is a directional signal, not a guarantee of commercial success.”
