One AI estate. Every leader gets the answer they need.
The same connected estate and the same measured facts, read through the question each role is accountable for. Not six dashboards — one source, six answers, so two leaders never arrive at a meeting with different numbers.
Why one source matters. Most organisations answer AI questions from whichever tool the asker happens to own — finance from the cloud bill, security from the SIEM, the board from a slide. The numbers then disagree, and the meeting becomes a reconciliation exercise instead of a decision. Every answer below resolves to the same reading of your estate. Where a source is not connected, the answer says not measured rather than filling the gap.
Board & management committee
The question: are we moving fast enough without creating exposure nobody owns?
Board reporting on AI usually answers the first half with adoption metrics and the second half with an assurance, which is why it rarely survives a follow-up question. What a board can actually act on is one measured number, its trend, what moved it, and how much of the estate that number covers.
- What you see: the AI Exposure Score with its band, the coverage fraction behind it, high-risk findings, autonomous agents without an owner, and a short list of decisions waiting on a named person.
- The honest part: whether the result sits inside the board’s risk appetite is the board’s judgement. Govern360 does not assert an appetite threshold, because a product that did would be inventing governance rather than reporting it.
- What you decide: whether the programme is funded adequately, and whether the exposure trend justifies the adoption trend.
CIO & Chief AI Officer
The question: which AI initiatives are scaling, and what is holding the rest back?
The honest answer in most enterprises is “security review”, and that is a governance problem rather than a security one. An agent with a resolved owner, a scoped identity and a declared purpose does not need a three-week review, because the evidence already exists.
- What you see: every AI system across the estate including the ones nobody registered, which are scaling and which are stalled, and where the control load is genuinely disproportionate to the risk.
- Where the leverage is: tiering agents by what they can do irreversibly, so low-risk assistants move quickly and the heavy review lands only where it changes something. Over-restricting low-risk agents drives shadow development; under-restricting autonomous ones creates real exposure.
- What you decide: what can go to production next, and which control to build so ten more things can follow it.
CFO
The question: where is AI spend going, and what is producing measurable value?
Cloud and vendor bills arrive at the account level, which tells you the total and nothing about which team, agent or use case produced it. This is the role least well served by every other tool in the category, and the one where a defensible answer is most achievable.
- What you see: token and AI spend attributed to team, agent, model and purpose — including Microsoft 365 Copilot licensing and Power Platform consumption, which generate no traces for an observability tool to read.
- Why it holds up in an argument: allocation is computed per record, not smeared across a department average, and every charge carries a replayable trace — the inputs, the rule that fired, the resulting owner. The first person to dispute an estimate wins; nobody wins against a trace.
- What you decide: which teams get budget, which agents to cap, and whether the spend curve is adoption or a runaway loop.
CRO & risk
The question: where is AI creating material enterprise exposure?
AI usually sits on the risk register as a paragraph, because “we do not know” is not a rating and a rating has to be defended. What a risk function needs is a measurement with a published method it can inspect and challenge.
- What you see: exposure concentrated by dimension, the risks that could not be measured excluded rather than shown low, and regulatory readiness mapped to the EU AI Act, ISO/IEC 42001, NIST AI RMF, SOC 2, HIPAA and GDPR.
- The method, stated: weighted geometric aggregation so a strong dimension cannot mask a weak one, the band capped by the weakest measured dimension, and evidence required before anything counts as measured.
- The limit, stated: the score measures governance state and is not validated against incident outcomes, because no incident corpus exists to validate it against. A risk officer will trust that answer more than a confident one.
CISO & security
The question: what can our AI access, do, and send outside the enterprise?
You likely signed off the Copilot rollout. The question that follows is who approved each agent built on top of it — and that is usually the one nobody can answer without a project.
- What you see: the data-to-action graph — which agents ingest untrusted content, which hold private data, which can send data outside the tenant, and which hold all three at once. Including the harder case, where the three legs sit across two agents that each pass an individual review.
- Identity posture: which agents hold a machine identity and which run as their creator, credential expiry and rotation, and the non-human identities linked to each agent.
- Enforcement without a new choke point: policy compiles into Purview, Intune, your SASE and your AI gateway, and applied state is read back where the platform exposes a read path — reported as Compiled, Marked applied or Verified rather than as a green tick you have to trust.
- What you decide: which three exposure paths to close first, and what to tell your board you closed.
Business leaders
The question: what can we safely move into production next?
The frustrating version of this is an agent stuck in review with nobody able to say what would unblock it. The register answers that directly, because it ranks by how much exposure each decision closes rather than listing alphabetically.
- What you see: your team’s agents, their autonomy tier, whether each has a signed purpose and an owner, and exactly which field is missing.
- Why it is faster: three decisions that close real exposure beat thirty that close none, so the queue is short and the sequence is obvious.
- What you decide: which agent to sponsor, and what to fix before asking for approval rather than after being refused.
Or start from what is actually driving it
Roles describe who asks. These describe what prompted the question — and each has its own page with the measured findings behind it.
- By use case: AI sprawl · agent accountability · non-human identity sprawl · token and Copilot spend · EU AI Act readiness
- By platform: Microsoft 365 Copilot · Copilot Studio and Power Platform · GitHub Copilot · ChatGPT Enterprise · full coverage and what is scoped
- By industry: financial services — SEC and FINRA, examiner-ready · healthcare — HIPAA, BAAs and PHI · technology — source code and IP
One estate, one reading. These are six views of the same measurement, not six products and not six licences. Where a source is not connected the answer reads not measured in every view, so no role sees a cleaner picture than another by accident. Figures shown in demonstrations come from a connected demonstration tenant, not a customer estate.
Questions, answered
Do different roles see different numbers?
No. Every view resolves to the same underlying reading of the estate, at the level of detail that role needs. That is the point — two leaders arriving at a meeting with different AI numbers is the failure mode this replaces.
Who should own AI governance internally?
Observability and inventory sit naturally with the CIO, because that is where the platform competence is. Risk appetite, tiering thresholds and named ownership belong with the business and the board. A CIO who absorbs all of it takes unbounded liability for judgements they do not make, and lets the business avoid the work.
Which role usually starts the conversation?
Most often the CISO, after an agent rollout raises a question nobody can answer. The CFO conversation tends to arrive second and independently, when an AI line item grows without attribution. They resolve to the same estate reading.
Is this a separate licence per role?
No. Pricing is per governed seat across three editions; the role views are how the same measurement is presented, not separate products.
What if a role’s question needs a source we have not connected?
The answer says not measured and names the missing source. It is not scored zero, not estimated, and not quietly omitted — the coverage fraction is published alongside the number in every view.
See it on your own estate.
Thirty minutes to connect, read-only, no proxy. One reading of your AI estate, answering all six questions — within twenty-four hours.
Get my AI Exposure Score