Included - AI Studio

A digital workforce for technology finance.

Workers trained in technology economics take on the jobs your team repeats every week: the morning cost check, the commitment watch, the Monday variance pack. They read your governed cost model, work under your permissions and report to the people you name. No language model ever produces a number. The engine calculates, and the workforce explains.

Included with every capability. Not an add-on, and not priced per seat.

Included with every capability

AI Studio uses AI to explain your technology cost. The AI Economics capability measures what AI itself costs and returns.

Why it matters

Every vendor now announces agents. The question is what you can check afterwards.

Most AI in finance software works from an export and gives you a plausible answer about money, so someone in finance still has to check it. That is the work the AI was meant to save.

AI Studio works the other way around. The engine calculates every figure from the governed model, and the workforce reads those figures, prepares the work and explains it. Workers stand on the context Data Studio has already built: what each application is, who consumes it and what it costs. A data platform on its own can give an AI your rows. The model is what tells it what those rows mean.

So the work can be checked. The numbers came from the engine. The brief it followed is a saved method, not a prompt someone typed once.

No language model ever produces a number on this platform.

Meet the workforce

Standing jobs, done before anyone asks

Every team builds its own workers. These are examples from a FinOps practice, written the way they were briefed.

Put a worker on shiftFour choices, then the work arrives on its ownRelease 6.2

  1. Who does itAn Assistant or a Specialist
  2. The briefA skill, written in your own words
  3. When it runsDaily, weekly, before the meeting
  4. Who hears backThe people you name
See

Spike Detective

Compares the newest settled day with a like-for-like day and names the services that moved.

Daily, 06:00 · reports to the cloud owner

ExampleVirtual machines down 30% on the day, licenses to zero alongside them

Optimize

Commitment Custodian

Watches every reservation and savings plan for low use and coming expiry, so renewals are deliberate.

Mondays · reports to the FinOps lead

ExampleOne reservation 12.5% used, ending in five weeks: let it lapse

Optimize

Weekend Wind-down Spotter

Finds non-production environments still running at weekends and sizes the wind-down.

Mondays · reports to engineering managers

ExampleDevelopment and QA running at full weekday cost on Saturdays

Control

Tag Police

Patrols ownership tags for duplicates, blanks and case splits, and names the resources to fix.

Mondays · reports to the platform team

ExampleTwelve clients split by capital letters, so their cost lands in two places

Prove

Friday Executive Brief

Turns the week’s movements, savings and risks into one page for the leadership team.

Fridays · reports to the CIO and CFO

ExampleSpend on track, two commitments to decide, one new workload without an owner

The workforce does the preparation. Your people make the calls. Workers prepare, check, measure, explain and report. They never post a charge, approve anything or change the model.

No worker produces a number. Every figure in their work comes from the model’s own calculation, the same one behind your reports and chargebacks.

What AI Studio does

Built like a technology economics team, with a worker for each part of the job

The work

Put a worker on shift

Choose who does it, give it a brief, set when it runs and who hears back. A daily spend check at six, a commitment watch every Monday, a variance pack before the month-end meeting. The work is ready before anyone asks for it.

Release 6.2

Briefs your people write once

A skill is a saved brief in your own words. Publish it across the organization and an analysis someone worked out once becomes a method every worker runs the same way.

One job, more than one Specialist

A single brief can draw on more than one Specialist. Ask for the variance on a cost center and it reads actuals from one and the budget from another, then returns the difference with drill-down.

Every run on record

Each scheduled run is saved as a conversation, so every piece of delivered work has a permanent home you can open, read and trace back.

Release 6.2

Who is on the team

An Assistant for each module

The Model Assistant finds where cost stops flowing, names the root cause and drafts the driver rule for you to apply. The FinOps Assistant covers cloud, commitments and unit cost. The Planning Assistant covers budgets, forecasts and scenarios.

A Specialist for each object in the model

Specialists go deeper than the Assistants, one for each standard object, answering at field level. Each is narrow on purpose, so every answer is small enough to check and says where it came from. Specialists you build for your own use cases arrive in Release 6.2.

Work in the pipeline, with nobody asking

AI Enrichment runs inside Data Studio as data arrives: it classifies ledger lines, normalizes vendor names and flags AI spend, before anyone opens a report.

Trained before it meets your data

The Assistants carry TBM and FinOps knowledge. Ask what a rolling forecast is and it explains the method. Ask what your rolling forecast is and it reads your model.

Built to be trusted with money

The engine calculates, the workforce explains

Every figure comes from the governed model. A data platform on its own can give an AI your rows. The model is what tells it what those rows mean.

Prepares, never posts

Workers prepare, check, measure, explain and report. They don’t change the model, post a charge or approve anything. Your people make the calls.

Your own AI, the same workers

Through the Model Context Protocol, the AI tools your teams are building can call the same Assistants, Specialists and briefs, on the same governed numbers. We enable the connection for you.

On request

Where the workforce stops

The workforce is only as complete as the model it reads. When something a job needs isn’t in the model, such as a contract end date that was never loaded, the worker says so and tells you what its answer is leaning on instead. Workers read the model; they don’t write to it.

Or ask in a sentence

The same workforce answers on demand, with no query language or report builder to learn

  • What did we spend on cloud yesterday, and what changed?
  • Why is this business unit’s recharge higher than last month?
  • If salaries rise five percent, what happens to the cost of serving each product?
  • Which of our AI licenses are assigned but sitting idle?

A workforce you can audit

What you can check afterwards: all of it

The numbers came from the engine, not from a language model. The brief a worker followed is a saved, published method, not a prompt someone typed once. And the work sits on the same governed model as everything else in MagicOrange.

AI Studio isn’t a separate pipeline that copies your data somewhere else to be analyzed, so the questions your security team asks about the platform are the questions to ask about the workforce too.

ISO 27001:2022
SOC 2 Type II
CyberVadis Gold
CSA STAR Level 1

Analyst view

What analysts say about the context behind AI answers

What it covers

One workforce across every category of technology spend in the model, whether it’s consumed, owned or human

Consumed

  • Public cloud
  • AI and agent workloads
  • Software and SaaS
  • Data cloud platforms

Owned

  • Infrastructure and network
  • End user technology

Human

  • Labor and services

Put your first worker on shift.

In a demo, put a worker on shift and follow every figure it reports back to the record.