You know the five decisions and the frame. Before you make any of them, you’ll name who owns each decision, then run an intake that flags the ones needing extra attention at your company. A decision with no owner is one of the quickest ways a rollout stalls.
Who owns a decision
Depending on your company’s size and rollout strategy, one person may own several of these decisions, or each may have a different owner. Titles vary too much across companies to be the guide, and some of these roles have never had to exist before: your company may not have had a “Claude spend owner” role before. Instead, look for the characteristics of what the role requires — what the owner is accountable for and can commit.
| Decision | Who decides: look for | What they need from you |
|---|---|---|
| Structure & Identity (organizations and groups) | • Owner (you) • Those who run your identity provider (IdP), such as Okta, Microsoft Entra ID, or Google Workspace • Those who know what your directory can express, such as IT operations | Your proposed group structure and the directory groups it relies on. |
| Access (surfaces and connectors) | • Owner (you) • Those who lead or champion the teams using Claude and can speak to their daily work and tooling • Those who answer for data risk and can sign off on connector access | Which groups get which surfaces and connectors, the phase order, and the workflow behind each write grant. |
| Governance (customization) | • Owner (you) • Those who own change management and enablement, such as an AI Center of Excellence, plus your security lead if the posture isn’t yours alone to set | The governance posture options and what each asks of members. |
| Spend (caps and escalation) | • Owner (you) • Those who can commit budget for this rollout, such as a finance partner or the executive whose line item this is | Your proposed caps and the usage story behind them. |
| Visibility (measurement and retention) | • Owner (you) • Those who answer for data risk, such as security, legal, or compliance, wherever that lives in your company | The options, your recommendation, and what each costs to change. |
The table above is a guide for who should be involved in these decisions, not a rule. If a decision has no obvious owner, take the characteristics column to whoever runs the function nearest to it and ask who should grow into the responsibility. Two of the five usually land with someone other than you: Spend, with whoever commits the budget, and Visibility, with whoever answers for data risk.
Pluto’s owners
| Decision | Owner at Pluto | Why they were selected |
|---|---|---|
| Structure & Identity | IT lead (holds Pluto’s Owner role) | Runs Pluto’s identity provider and knows what the directory can express |
| Access | IT lead, with the risk lead for Payments & Trust signing off on any connector grant that writes | Same owner as the directory and sign-in; a write-capable connector adds data risk, so the risk lead co-signs those grants |
| Governance | AI Center of Excellence (CoE) lead, with the IT lead holding the settings behind it | The CoE owns change management and enablement — how customizations spread is their function |
| Spend | CFO’s delegate | Holds the budget line the rollout draws on |
| Visibility | Risk lead for Payments & Trust | Answers for data risk under Pluto’s financial regulation |
Lesson activity
The interactive widget below is the intake questionnaire: it asks about your company’s shape, your directory, your regulated work, and your mandate, and flags the decisions that need extra attention at your company, with the reason for each flag. The decisions are already in the order they have to be made, and you can copy the result into your companion.
→ Record this in the work-along companion, section Lesson 2.
Downloads
What’s next
In the next lesson, you lay down the last of the groundwork: where you’ll work, the roles that gate your organization settings, the six prerequisites to confirm before the first decision, and domain claiming.