See which teams use which AI tools, and what it costs.
“We bought seats for everyone. Which teams are using them?”
Usage and spend are read from each AI provider and shown by team. Seat counts, adoption goals and idle seat findings are in preview.
Where the AI spend goes
$38,640 in 30 daysWhere people's time goes
≈$610k in 30 days · with AI ≈$650kRead from pull request activity, 80% at set daily rates
53% of this month’s AI spend reached no goal.
- Claude Code and Cursor usageLive
Daily usage and spend for Claude Code and Cursor, by team, read from the provider.
- Copilot, Claude Enterprise and OpenAI usageLive
Usage of Copilot, Claude Enterprise and OpenAI appears in the same place, counted by the vendor.
- Seats held and active by teamPreview
See seats held against seats in active use by team, and set an adoption goal on it.
- Idle seatsPreview
Team owners are told which of their AI seats are idle, so they can reassign or cancel them.
- Reported by teamLive
AI usage is shown by team, for teams of five or more.
- Company AI spendLive
Each AI tool's bill in one place, read from the vendor, with the change since the last period.
Live In the product today. Preview Working, refined with customers.
Kestrel holds four hundred AI coding seats across three tools.
- 01With seat measures in preview, payments engineering shows nine in ten seats active and branch systems three in ten.
- 02The head of AI sets an adoption goal for branch systems, measured on active seats read from the vendor.
- 03Sixty seats idle for a month are raised with their team owners, who reassign most of them.
Kestrel Bank is a fictional example. The figures are calculated by the product.
- Cursor
- GitHub Copilot
- Claude Enterprise
- Claude Code
- Anthropic
- OpenAI
- TeamForm
- BambooHR
If a system you rely on is not listed, ask for it. Outcome’s integration builder drafts the connection, and it is offered to you to try before it is switched on. How the agents work
Adoption is measured from provider usage and seat data, including Claude Enterprise outside coding tools. Sentiment about the tools stays in your survey tool.
Leaders can direct enablement to the teams that need it and stop paying for idle seats.
More in engineering excellence- Delivery metricsDeployment frequency, lead time and pull request flow, by goal.
- AI impactAgent and human work compared on share, speed and cost.
- Agents at workHand a goal's work to coding agents, with human approval.
- ReliabilitySentry errors and user feedback, grouped and given an owner.
- Where effort goesHow much work reaches a goal, and where it overlaps.