Skip to content

Managed service provider: your clients' AI, read without touching it.

Licenses, settings and authorized apps, client by client: Ojja reads in read-only mode what your clients already have, dates what vendors turn on, and lets you apply what they decide.

Become a partnerWhat the administrator authorizes

A managed service provider's questions

  • What did the vendor turn on by default at my clients this month?
  • Which applications have their employees authorized on their data?
  • Which seats to reclaim, and before what date?
  • A client asks for a tool: what do they already have that does the same thing?

The processes you carry at your clients

  • Knowing what runs at each client.
  • Following what vendors turn on.
  • Spotting the applications connected by employees.
  • Handling tool requests.
  • Applying decisions.

What Ojja takes off your plate

  • Watching vendor announcements, client by client. Ojja estimate: 2 to 4 hours per week, for 10 to 15 software products.
  • The inventory done by hand. Ojja estimate: 2 to 3 days per inventory.

Each “Ojja estimate” is a starting order of magnitude, set by Ojja with its assumption when it has one: neither a measurement nor a promise. The measurements of our first customers will replace it.

Your levers, therefore your engagements

  • Your engagements, pre-filled, coming. Unlock, adjust, turn off: each of your client’s levers arrives with its facts, and usage or euros before and after prove what your engagement changed.

Your dated reason to call

  • Each Microsoft renewal at a client: a seat can only be reduced in the seven days that follow the renewal (Microsoft Learn, cancellation policy, 09/25/2025).
  • The Microsoft 365 increase at the first renewal after July 1, 2026.
  • And then: your clients’ decisions reach you as work orders, with Ojja Actions (coming).

What Ojja gives you

  1. If you administer their tenant. The authorization link comes to you: about ten minutes, with an administrator account, read-only.
  2. The origin of each line. Turned on by the vendor, by an administrator or by an employee; extracted from the tools, declared by your client, or inferred.
  3. Five alerts, as soon as the event is read. New AI application connected, usage billing turned on, vendor terms or features changed, new model behind a feature, new data access.
  4. What sits idle, before the renewal. Seats paid for with no usage over 28 days, including on deactivated accounts, with the date they can be reclaimed.
  5. The decision circuit, and the work orders. Your client decides. With Ojja Actions (coming), the action goes through you first: Ojja prepares the work order, your client approves it, you carry it out with your own delegated administration rights, and the next reading dates the result. Your client can also choose, family by family, that Ojja carries it out itself after their approval.
  6. The AI inventory in your security review. The AI applications connected to your client's data, its agents and their access, its API keys: the dated material for the review you bill them.
  7. All your clients on one screen. One line per client, with what is left to decide.
  8. The connections between their tools. What vendors document about the connections between your clients' tools.

If you resell licenses

  • If you resell licenses, they see that too.
  • What you receive from Ojja is visible to your client.
  • Reclaiming or turning off a license you sell them: the decision remains theirs.

On the Arvenne example

Arvenne's readout reads 37 applications and 14 AI features. Grouped by vendor: at Microsoft, Copilot Chat, enabled by the administrator for all 412 accounts, the Teams meeting recaps, enabled by the vendor with no decision, and a Purchasing agent built in Copilot Studio; at OpenAI, ChatGPT, connected by employees on 14 accounts. During the week, Arvenne's AI lead regularizes the meeting recaps and turns off the AI companion of the video conferencing tool. The administrator applies; the next snapshot records it.

Arvenne, a fictional company · sample data

See an example: Arvenne

What Ojja never does

  • Nothing changes in your clients' tools without their approval: their administrator applies, or Ojja Actions (coming), if they have turned it on.
  • Ojja installs nothing on workstations.
  • Ojja resells no software and builds nothing.
  • Ojja gives no figure per person.