AI

Claude Enterprise

Roiva books Claude Enterprise usage cost by user group or estimated chat Project, values the time Claude Code saves, and counts who chats against your seats.

What usage cost by user group or chat Project, how much developer time Claude Code gives back across your Claude Enterprise organization, and how many of your seats are used for Claude chat each month

Each member's daily analytics for the last 3 months, and the organization's assigned seats. Rows name members by email; Roiva adds Claude Code up by day, swaps each member who chatted for its own digest, and drops the names before anything is saved. Also what usage cost by member, user group and product, and each member's messages in each chat Project, as far back as Anthropic's reports go, with members dropped the same way. The chat and cost figures come from Anthropic's beta Analytics API. Built from Anthropic's docs.

An Analytics API key, created by your Claude Enterprise organization's primary owner

What you can measure with Claude Enterprise
Developer time from accepted edits

Edits developers accepted in Claude Code × minutes saved per edit × your developer rate, as freed capacity. Roiva starts from one minute an edit until you set your own.

claude_enterprise.claude_code.acceptances

Starts from the AI Coding Assistant Rollout template

Beside Copilot, each in its own unit

A Copilot acceptance can bundle several completions and a Claude Code one is a single edit, so with both, each is priced at its own minutes rather than added together.

Starts from the AI Coding Assistant Rollout template

Adoption

Developers using Claude Code on an average day, and the share of its edits they accept, month by month.

claude_enterprise.claude_code.active_users_avg claude_enterprise.claude_code.acceptance_rate
Time given back on the tasks you timed

Members who chatted with Claude in the month × the timed tasks each does with it × the minutes your own time study found it saves × your blended rate, as freed capacity. Roiva supplies no tasks or minutes, so nothing is booked until your study sets them.

claude_enterprise.chat.monthly_active_users

Starts from the AI Assistant Rollout template

Seats against use

Seats assigned beside the members Anthropic counts as active, by their token use over the 30 days to the same day, so seats nobody uses show up before the renewal. Reclaiming them lowers the cost; it isn't booked as value as well.

claude_enterprise.seats.assigned claude_enterprise.users.active_30d
Against what the seats cost

Claude Enterprise seats are the initiative's cost, from Anthropic's invoice or the bill in your books, so cash ROI sets them against the freed time once it becomes cash.

What usage cost, by user group or Project

On a usage-based plan, what usage cost comes from Anthropic's beta cost report, and each initiative books the user groups it claims, or the Projects and products, or a percentage of one. Anthropic doesn't report cost by Project, so a Project's is an estimate, flagged as one: each person's chat cost, split by their share of chat and Cowork messages, which can read high or low. Built from Anthropic's docs. Seat fees aren't in that report, and on a seat-based plan it holds only usage credits, so seats still come from your books.

A worked month

Claude Code and Copilot across one engineering team

Developer Capacity Freed by GitHub Copilot and Claude Code on Claude Enterprise, from the AI Coding Assistant Rollout template, for September

Copilot suggestions accepted 12,000 GitHub
Minutes saved per Copilot acceptance 0.8 Your time study
Edits accepted in Claude Code 21,000 Claude Enterprise
Minutes saved per Claude Code edit 1.5 Your time study
Developer hourly rate, total compensation $94.50 Roiva's default, until you set yours

(12,000 × 0.8 + 21,000 × 1.5) × $94.50 ÷ 60

$64,732.50 freed capacity for September, reported beside cash ROI, never in it

A new initiative books the two assistants as separate formulas, which come to the same total. With only Claude Code, the initiative gets the single-assistant formula instead: accepted edits × minutes per edit × your developer rate.

Illustrative figures. Roiva keeps every input with the entry it calculates, and none of it counts until it's approved.

The daily Claude Code totals behind a month's accepted edits, with no developer named.

What gets synced

Roiva writes these metric observations on each sync. Reference the key in a value formula to use this data in your ROI calculations.

Usage Cost

claude_enterprise.usage.spend Usage Spend currency

Claude Code and Chat Activity

claude_enterprise.claude_code.acceptances Accepted Suggestions count
claude_enterprise.claude_code.proposals Suggestions Offered count
claude_enterprise.claude_code.acceptance_rate Acceptance Rate percentage
claude_enterprise.claude_code.lines_accepted Lines of Code Added count
claude_enterprise.claude_code.active_users_avg Active Developers (daily average) count
claude_enterprise.chat.monthly_active_users Monthly Chat Users count
claude_enterprise.seats.assigned Assigned Seats count
claude_enterprise.users.active_30d Active Members (30 Days) count
What Roiva keeps

Reads: Daily analytics for each member for the last 3 months, of which Roiva uses the Claude Code figures and the number of chat messages, the organization's daily summary of assigned seats, and, as far back as Anthropic's reports go, what usage cost by member, user group and product, and each member's message counts in each chat Project. Each member row names the member by email; Roiva adds Claude Code up by day, keeps a digest of each member who chatted, and drops the names before anything is saved.

Keeps: Records of daily Claude Code totals, daily Claude chat totals, Claude chat users by month, monthly Claude Enterprise seat counts, monthly cost by Project and product and daily cost by user group, plus the totals worked out from them.

What Roiva keeps from each platform, field by field →

How to connect

You connect Claude Enterprise from inside Roiva, so you need a Roiva workspace first. Sign in to connect it now. New to Roiva? Start free with your work email, take the free assessment and create your workspace at the end, or request an invite.

  1. In Claude: Sign in to claude.ai as your Claude Enterprise organization's primary owner — only the primary owner can turn on API access and create Analytics API keys
  2. In Claude: Go to Organization settings → API (claude.ai/admin-settings/api-access), turn on API access and create an Analytics API key
  3. Back in Roiva: Paste the key here — it is shown only once — and save the connection
  4. Back in Roiva: The connection page checks each step and says what's missing. Once it's all ticked, click Test Connection, then link this connection to an initiative on the Initiatives tab
Need help?

Email hello@roiva.ai with what you're seeing, and you'll hear back within one business day.

Claude Enterprise

Start free, then connect Claude Enterprise once your workspace is set up. Or begin with the free AI ROI exposure assessment.

Start free → Sign in to connect