Spend
See the proof behind every dollar
RepoOps does not estimate your AI spend, it attributes it. Here is what the Telemetry and Claude Code usage surfaces show, and how the cost of every run ties back to the code it shipped.
Telemetry and Claude Code usage
Telemetry is a combined view of tokens and spend across every tracked repo, per developer, per day, per model, captured locally and retained as long as you want. Claude Code usage drills into per-session token spend with heuristic and LLM-driven recommendations on where you are overspending. Together they mean you stop guessing what AI cost this week.
Cost per PR
Every merged pull request gets priced, so spend is fused to the unit of work it produced, not just a monthly total. You can see the dollars behind a session, a prompt, and a developer, reconciled against real Anthropic billing.
Financial Model
The full model: revenue, cost of goods, margin floors, and the levers that move them. A team sees the economics of its AI usage, not just the invoice, so a spend decision can be made on the numbers.
Efficiency tab
A composite Spend-Efficiency grade over six levers: defaults, routing, caching, context, visibility, and ROI. Routing savings open as a pull request, then get measured after they land, so a saving is proven rather than promised.
Billing Outcomes
A per-client, one-page invoice export with proof-of-work line items, so you can defend every billable AI minute to a client or to finance. Each line ties a dollar to the work it shipped.
How it helps you
- Know what AI cost this week, per developer and per repo, with a defensible split for chargeback.
- Tie every dollar to the pull request and outcome it shipped, not a lump-sum bill.
- Turn a cheaper-model insight into a reviewable pull request, then confirm the saving landed.
- Hand a client or your CFO an invoice that proves the spend produced working code.