Insights and the budget forecast

What you’ll learn

• What each number on Insights means and how it's counted.
• How to read the weekly chart and find where time goes.
• How the budget forecast works, and what to do when it says you're close.

Who sees it

Insights is in the sidebar for owners and admins. It covers your whole organisation; nobody outside it sees your numbers. Choose 30 days, 90 days or 180 days at the top.

The four numbers

1. Lead time — the median time from a feature's creation to done in its first environment. Half of your features are faster, half slower.
2. To the last environment — the same, up to the last environment (production, for most teams).
3. Runs that succeeded — the share of Claude's runs that finished without failing or being cancelled.
4. Claude's cost — what Claude cost over the period, and per finished feature.

Example: Acme Logistics sees a lead time of 4 days but 11 days to production. Most of the wait is between environments, not in building — so the team turns on automatic promotion when everything is merged.

Features finished per week

The bars show how many features were done each week. Show as a table gives the same numbers as text, to copy or read with a screen reader. Gaps usually mean holidays, a release freeze — or features waiting on approvals.

Tip: compare weeks before and after a change (new rules, a new model for Build). Insights shows whether it helped.

The budget forecast

Budget forecast for this month takes what was spent so far and the pace of the last 14 days, and projects the month's end against your budget for the month — the daily budget from Settings › Claude and cost, over every day of the month.

• On track — keep going.
• Close to the budget — check which features cost the most, or use a lighter model for Check and Document.
• Over the budget — runs stop when the daily budget is reached; raise it or slow down.

Check yourself