For teams

Your team is adding AI spend faster than it can see it.

The question isn't whether your team uses AI agents. It's whether you can see and account for what they cost. Ottto gives leaders one reconciled number - per developer, per tool, per machine - before finance asks.

Ottto for Teams is in early access · grab a 30-min slot or request an invite
See it first

One number for the whole team, not a pile of vendor dashboards.

Teams add AI spend faster than they can see it. Ottto reconciles every engineer's subscriptions, API usage, credits and cloud into one labeled total - so you can answer "what did AI cost us this month, and why" without stitching screenshots.

  • Per developer, per tool. Who spent what, on which agent, across every account and machine.
  • Human work vs agent work. Separate what people drive from agents spawning other agents.
  • One source-labeled total. Exact where we know it, estimated where we don't - never an unlabeled guess.
ottto.net/team
Backend squad · 6 devs$2,840exact
Platform · 4 devs$1,610exact
Mobile · 3 devs$980est.
62% of this month is agent-driven, up from 41%. The shift, not just the total, is where the budget went.
Budgets

Budgets that warn before the invoice.

Set a budget per tool, per team, or per developer. Ottto pings you on Slack or desktop while you can still act - before the spend lands, not after. No blunt per-seat cap needed; you see the trend and decide.

  • Before, not after. An alert when you're trending over - with time to move, not a surprise on the bill.
  • Slack + desktop. Where your team already works, plus a daily digest of what changed.
  • Anomaly catches. A runaway loop or a misrouted model flagged the moment it spikes.
slack · #eng-ai-spend
Platform team is at 82% of the monthly budget on day 19. On pace to land ~$430 over. Review the drivers?
A Codex session has looped 240+ tool calls in 35 min. Likely a runaway agent - want to cap it?
ROI

Know what the spend returns.

"$200 a developer and no one can say what it bought" is the default today. Ottto gives you the real cost denominator - true per-developer token and usage spend across every tool - then lines it up against shipped work. Connect your repos with our plugins and skills and watch AI spend next to PR merge rate: is the budget turning into merged code?

  • The real denominator. Per-dev spend across tools and accounts - the number ROI math usually gets wrong.
  • Spend vs shipped PRs. Cost per merged PR by team, so "expensive" and "productive" stop being guesses.
  • Your data, your agents. The unified data layer is exposed over CLI, MCP, plugins and skills - so your own agent can pull the team's real usage and run its own analysis.
ottto.net/team/roi
Backend · 47 PRs merged$60per PR
Platform · 31 PRs merged$52per PR
Mobile · 9 PRs merged$109per PR
Mobile costs $109 per merged PR vs $60 team-wide. Worth a look before the next budget - is it harder work, or wasted spend?
Out of your team's way

Observe, don't intercept.

Never in the middle · no proxy, no latency No tool limits · we don't touch provider terms Open source · local-first, read-only

Ottto collects in parallel. It doesn't proxy requests, limit which tools your team uses, or sit between an engineer and their provider - so it can't trip rate limits or terms.

For teams

See your team's real number.

One reconciled total, budgets that warn early, and AI spend lined up against shipped code. Start free for yourself, then bring the team.

We'll be in touch within one business day. · individuals can start free anytime at app.ottto.net