Your AI bill, as a statement finance can sign off.
TraceROI allocates your Claude Code, Cursor, Copilot and OpenAI spend to teams and projects, ties the total to the vendor invoices, and shows what shipped work costs and what next quarter will cost.
No surveys. No individual scores. No ROI multiple you have to defend.
Read-only by design
Narrowest vendor scopes. We never write to your systems.
Metadata, never code
Costs, repo names, timestamps, PR counts. No code, prompts or outputs.
Teams, not people
Views are team-level, with a minimum group size. No individual scores.
Honest about limits
Hosted in the US. No SOC 2 yet. Unplaced spend is shown, never hidden.
The AI line jumped again. Finance wants three answers.
Which teams and projects was it for? What does a unit of shipped work cost now? And what will next quarter cost?
The vendor dashboards each show one tool, per person. Engineering analytics show activity. Finance needs dollars that tie to the invoice.
of finance leaders name unit-level allocation of AI cost as a gap; 48% name forecasting.
CloudZero, 2026 survey of 260 finance leadersof engineering leaders say they measure AI productivity gains at all.
LeadDev, The AI Impact Report 2026of finance leaders can't fully connect AI spending to business outcomes.
CloudZero, 2026 surveyOne monthly statement. Four numbers finance actually uses.
Every AI tool, allocated by repo and team, tied to each vendor invoice to the cent.
AI cost per merged PR, by team and repo, month over month. From GitHub, not a survey.
Next month and quarter by team, with each change explained: active people, spend per person, model mix.
Set a budget per team; see the variance before the invoice does.
CSV with your cost-centre and account codes, ready for the close.
Paid vs active seats on every tool, before the renewal.
Good tools exist. We're building the statement none of them file.
| What it does well | What a 50–300 engineer company may not get | |
|---|---|---|
| Vendor dashboards | Free and accurate for their own tool. | One tool each, per person. |
| Spend management e.g. Ramp | Free. Spend by user, team and model, with controls, from the real invoices. | No repo, project or shipped-work view in public materials. |
| Developer productivity e.g. DX, Jellyfish | Surveys and telemetry; AI spend by team or initiative; named customers. | Built for engineering leaders; reported contracts often run to tens of thousands a year. |
| Delivery analytics e.g. Swarmia, LinearB, Zest | Delivery metrics; AI adoption and cost modules; cost per merged PR (Zest). | No invoice reconciliation or finance statement found in public materials. |
| TraceROI (early access) | One statement across tools, reconciled to invoices, by team and project, with unit cost and forecast. Public price. | New and small. No SOC 2 yet. No causal ROI figure, by design. Cursor and Copilot are allocated by activity share. |
Based on public product materials as of November 2026. Tell us if something here is out of date.
A week to first allocation. A statement at your next close.
Connect, read-only
Claude Code telemetry rolled out by your admin, Anthropic and Cursor admin keys, a read-only GitHub app. OpenAI and Copilot follow.
day 1Map repos to teams
Import GitHub teams or a CSV of repos, teams and cost centres. Add budgets if you have them.
week 1Close the month
Enter invoice totals. Get the reconciled statement, unit cost, forecast and export.
next month-endTargets for early access, not measured results. Unit-cost trends and forecasts need a few weeks of history.
What engineering and finance leaders ask first.
Is it available now?
Not yet. TraceROI is in private build. Early access opens in the new year, starting with a small group of companies.
Where's the ROI number?
On purpose, there isn't one. Nobody can honestly measure a causal return on AI coding tools today. We give finance the numbers that do exist and hold up: where the money went, what shipped work costs, and where the bill is heading.
Will engineers see this as surveillance?
Views are team-level with a minimum group size, and there are no individual scores. We store metadata only: costs, repo names, timestamps and PR counts. See Security.
How is this different from Ramp?
Ramp is excellent at spend by user and team. TraceROI goes one step further: spend by repo, project and shipped work, reconciled to each invoice, with a forecast that explains its own changes.
What will it cost?
Planned: $399/month up to 100 engineers, $899/month up to 300 and $1,799/month up to 600. See Pricing.
Close next quarter with an AI line finance can sign off.
TraceROI is in private build. Join the early-access list and we'll invite a small group of companies first, in the new year. No spam, and no sales calls before then.
Got 2 minutes? Tell us how you account for AI cost today →
Thank you. You're on the list. We'll email you when early access opens.