Ojja Watch, your company's living AI register.
What you have, what you pay for, what everyone can use. Your tools are read every day or every week, depending on the tool; an alert on five events as soon as they are read; a dated snapshot every week to decide.
The readout and Ojja Watch are in French for now.
AI register
Arvenne, a fictional company
Left to decide12
| Feature | Origin | Paid | Enabled | Used | Decision |
|---|---|---|---|---|---|
| Copilot ChatMicrosoft 365 Copilot Chat | Set up by an administrator | no | yes | usage not read | Adopt |
| Meeting recapsMicrosoft Teams | Set up by the vendor, by default | no | yes | usage not read | No decision |
| PurchasingCopilot Studio | unknown | yes | yes | usage not read | No decision |
| ChatGPTChatGPT | Set up by your employees | no | yes | yes | No decision |
| Notion AINotion AI | unknown | yes | yes | usage not read | Reclaim |
| AI companionVideo conferencing tool | unknown | no | yes | usage not read | No decision |
Example on a fictional company. In the workspace, each line shows where its facts come from.
Feature by feature
The AI register
Each AI feature has its line, its status and its source.
The AI fact sheet
What each feature does, what it reads, where the data goes.
Worth its price
The time each tool must save.
Decide
Five verbs, a register, a snapshot that records.
Your feed and alerts
What changes at your vendors, filtered on your tools.
The employee portal
What everyone can use, and an answer within a day.
Your AI plan
What your teams ask for, what you already have, what you decide, what is actually used.
See
- The AI register. Each AI feature has its own line: vendor, software, date enabled, cost, status (paid, enabled, used), where the fact comes from. Filter by vendor, department, type of AI, usage, model or source.
- What's left to decide. A counter that is always visible. Every week, a dated snapshot: what changed, what has been idle for a month, what overlaps.
- Worth its price. For each tool and each agent, the time it must save to be worth its price, against the usage read in your company. Four answers: worth its price, worth its price if usage follows, not worth its price, too early to tell. Benchmarks published elsewhere are labeled as such, never mixed with what is read in your company.
Decide
- Five verbs. Adopt, regularize, reclaim, turn off, consolidate. Each decision carries its author, its date and its reason; the register keeps the history.
- The activation circuit. Nothing new arrives without going through a decision: an announced feature goes on hold in the register, you can defer it as long as the vendor allows, you decide, the portal announces it with its rule, and the next snapshot records that it is done.
- Ojja executes nothing. Your administrator applies the decision in the tool; the next snapshot records that it is done.
Anticipate
- Your feed. The public feed, filtered on your software: a feature turned on by default next month, a change in terms of use, a model replaced.
- Five alerts, as soon as the event is read: new AI application connected, usage billing turned on, vendor terms changed, new model behind a feature, new data access.
- Depending on the vendor, some events can only be read once a week; the Connections page of your workspace says so, tool by tool.
Connected to what you use
Microsoft 365
read from the free readout
- New AI application connected:
- read every day
- Usage billing turned on:
- read every week
- Vendor terms changed:
- on each publication
- New model behind a feature:
- read every day
- New data access:
- read every day
Console export of the usage report, provided by your administrator
Copilot Studio and Agent Builder agents
read with Ojja Watch
- New AI application connected:
- read every week
- Usage billing turned on:
- read every week
- Vendor terms changed:
- on each publication
- New model behind a feature:
- read every week
- New data access:
- read every week
CSV export of the inventory, provided by your administrator; without either, agents are marked “not read”.
For each connection, the data rule is shown before authorization: “we never have access to it” when the tool separates settings from content, “we never touch it” otherwise.
The employee portal
- What is available, what is allowed, what isn't. Each employee sees what exists for them and requests a tool in one click. You receive the request with its context and you decide. A tool request gets an answer within a day, and its fact sheet first shows the equivalent you already pay for.
- The rule next to the tool: for each piece of software, the data fact sheet says what it does with content and whether a protected version already exists.
The AI fact sheet
One fact sheet per AI feature, with the same template everywhere: what the AI does, the model, what it reads, where the data goes, whether it trains on your data, on by default or not, billing, frameworks the public catalog links to it, sources and date. Public on ojja.ai for each piece of software; in your workspace, with its status in your company and your decision as well.
Writing assistant
Fictional software, sample fact sheet
- What the AI does
- Drafts and summarizes documents
- Model
- Disclosed by the vendor
- What it reads
- The user's documents
- Where the data goes
- European Union
- Trains on your data
- No
- On by default
- Yes
- Billing
- Included in the license
- Frameworks the catalog links to it
- Data protection
- Sources and date
- Vendor's terms, September 12, 2026
Ready-made files
- A customer's AI questionnaire
- Before buying AI software
- An unexpected AI bill
- Works council (CSE) consultation: a fact sheet for the file of the deployment you are launching.
What Ojja Watch is not
- Not a consulting firm or an integrator: everything goes through the product.
- Not legal advice: Ojja Watch shows the frameworks the public catalog links to a feature and the points to review with your counsel. It never prescribes anything to you.
- Not an administration tool: it never writes to your software.