The numbers, where you already work.
Close packs, chargeback journals, board summaries and scheduled digests. Into Excel, Sheets, Snowflake, your ERP, or over an API. On your calendar, not ours.
Can AI cost data be exported into our own systems?
Yes. Camaze is built to feed the systems finance already runs rather than to replace them. Any view can be scheduled as a recurring report and delivered to Excel, Google Sheets, Slack, Microsoft Teams, email, a webhook, Snowflake or a journal-ready ERP export. Everything visible in the interface is also available over an API, at the same level of detail, with the same attribution applied.
Another dashboard nobody opens.
Finance does not need a new place to look. The close pack has a format.
More detail
The board deck has a template. FP&A has a model that took two years to build and is not going to be rebuilt around a vendor's interface.
A tool that can only be consumed inside itself creates work rather than removing it. Somebody logs in, exports a CSV, reshapes it, pastes it into the real system, and does that again every month.
- Manual exports and reshaping every close
- Figures that do not reconcile to the general ledger without adjustment
- No audit trail from a reported number back to the underlying usage
- Board and department reporting rebuilt by hand each cycle
| Report | Runs | Lands in |
|---|---|---|
| Monthly close pack | 1st of the month | Excel, emailed to finance |
| Chargeback journal | 1st of the month | ERP export, journal-ready |
| Board AI summary | Quarterly | PDF and slides |
| Cost by team | Every Monday | Google Sheets, live |
| Raw cost and usage | Nightly | Snowflake |
| Budget variance digest | Every Friday | Slack, #finance |
Illustrative product view. Figures are examples.
Every view is a scheduled report.
Anything you can see can be scheduled, addressed and delivered. The report is generated from the same attributed data as the interface, so there is exactly one version of each number.
- Schedules: daily, weekly, monthly at close, or quarterly
- Destinations: Excel, Google Sheets, Slack, Teams, email, webhook, Snowflake, ERP export
- Formats: spreadsheet, PDF, journal file, raw table or API response
- Every figure traceable back to the underlying usage records
A month-end pack that ties out.
The monthly pack arrives on your close schedule with the figures already attributed: spend by department, by project and by product, variance against plan decomposed into volume, unit cost and scope, and a note on the largest movements.
More detail
Chargeback runs from the same source as a journal-ready file mapped to your chart of accounts. Where a period is restated because a mapping changed, the restatement is shown explicitly rather than applied silently.
- Journal-ready export mapped to your chart of accounts
- Accrual support for periods where provider billing has not settled
- Variance decomposed rather than reported as one figure
- Full drill-down from a journal line to the underlying usage
| Project | Model | Share | Cost | Change |
|---|---|---|---|---|
| Support automation | Claude Sonnet | $34,800 | +22% | |
| Search and ranking | GPT-4o mini | $21,400 | -6% | |
| Sales copilot | GPT-4o | $18,900 | +31% | |
| Docs assistant | Llama 3.1 70B, self-hosted | $15,200 | +9% | |
| Data enrichment | Gemini 1.5 Flash | $11,600 | -14% | |
| Internal agents | Mixed | $9,800 | +64% | |
| Engineering seats | Cursor, Copilot | $8,300 | 0% |
Illustrative product view. Figures are examples.
The AI slide, generated.
Board reporting on AI has settled into a predictable set of questions: what did it cost, what is the trend, what is it as a share of revenue and of cost of goods sold, what did we get for it, and what does next year look like.
More detail
Camaze produces that as a quarterly summary with the trend, the drivers, the unit economics and the forecast with its range, so the pack is assembled rather than authored.
- Quarterly AI summary as PDF or slides
- AI as a share of revenue and of cost to serve
- Forecast with range, plus prior forecast accuracy
- Savings identified and realized, tracked over time
Illustrative product view. Figures are examples.
For the teams that want the raw data.
FP&A teams with their own model, and data teams building internal reporting, generally want the underlying table rather than a rendered view.
More detail
Cost and usage land in Snowflake nightly at full detail, with attribution already applied.
Everything is also available over a REST API, including forecasts, budgets, alerts and savings findings, so Camaze can be a data source inside reporting you already own.
- Nightly cost and usage tables in Snowflake, attribution applied
- REST API covering spend, usage, budgets, forecasts and findings
- Live Google Sheets connection for models that need to stay current
- Webhooks for events, so alerts can drive your own workflows
| Report | Runs | Lands in |
|---|---|---|
| Monthly close pack | 1st of the month | Excel, emailed to finance |
| Chargeback journal | 1st of the month | ERP export, journal-ready |
| Board AI summary | Quarterly | PDF and slides |
| Cost by team | Every Monday | Google Sheets, live |
| Raw cost and usage | Nightly | Snowflake |
| Budget variance digest | Every Friday | Slack, #finance |
Illustrative product view. Figures are examples.
See it in your own format.
Bring last month's close pack or board slide to the walkthrough and we will show you the generated version.
What most teams schedule
A typical set after the first month.
Weekly digest to budget owners
Each team owner receives their own spend, budget position, forecast and largest movements, in Slack or Teams, every Monday. This is the report that changes behavior.
Monthly close pack and journal
Attributed spend, decomposed variance and a journal-ready chargeback file, delivered on the close calendar so it arrives before it is needed rather than after it is chased.
Quarterly board summary
Trend, drivers, unit economics, forecast with range, and savings identified against realized. Generated, then edited, rather than built from a blank page.
Keep reading
Cost allocation
The attribution underneath every report: team, project, product, department and customer.
Read moreForecasting
Where the month lands and what next year costs, with ranges and variance against plan.
Read moreFor FP&A teams
AI as a driver you can model, in the planning process you already run.
Read moreQuestions people ask
Can reports go straight into our ERP?
Yes. Chargeback output is available as a journal-ready file mapped to your chart of accounts, on your close schedule. Teams currently export for NetSuite, SAP and similar systems. If your ERP needs a specific layout, the export format is configurable.
How do you handle providers that bill late?
Every figure carries its own freshness, and anything still settling is marked as such rather than presented as final. For close, Camaze supports an accrual based on usage already observed, which is then trued up when the provider bill settles.
Is there an audit trail?
Yes. Any reported figure can be drilled from the summary down to the individual usage records behind it, with the attribution rules that were applied and when they last changed. Mapping changes are versioned, so a prior period can be reproduced as it was reported.
Can we build our own reports?
Yes. Any view you construct can be saved, scheduled and addressed. For anything beyond that, the API and the Snowflake tables give you the underlying data at full detail.
Do reports respect access permissions?
Yes. A team owner sees their own scope. Finance sees the consolidated position. Scheduled reports inherit the recipient's permissions, so a digest cannot leak spend a recipient is not entitled to see.