Budgets requires seat tracking admin rights and unlocks once your allocation has at least one group.
Get started
- Sign in to nOps.
- In the sidebar, open AI → Budgets.
- Review the targets setup generated from your recent spend, and adjust them.
- Switch to Budgets vs. Actual to see how the current period is tracking.
Planning
Summary cards
The second card is the one to watch. Handing out more limit than you budgeted is not an error, but it is a decision, and this is where you find out you made it.
The group grid
A Targets row totals the grid. On a bottom-up budget you edit each group’s periods and the total rolls up; on a top-down budget you edit the Targets row total and the group rows move proportionally.
Search with Search groups… when the list gets long.
The two halves of this grid come from different places. Period targets and actuals come from the linked Explorer report. Seat spend, Limit, and Remaining come from live provider APIs. They can legitimately disagree for the current period.
Roll up by group or vendor
The Roll up by toggle changes the lens:- Group — roll spend up by allocation group, with editable targets. This is the working view.
- Vendor — roll the same seats up by AI vendor (Claude, Cursor, and so on).
?budgetBy=vendor. Its period columns cover the current period and earlier, drawn from the monthly spend rollup; future periods hold targets, which stay on the Group view. Vendor mode is not available when your allocation is organized by user.
Context banners
The grid tells you when something upstream is incomplete rather than quietly showing zeroes:- Enable AI providers to sync seat usage — no provider is syncing seats yet.
- Your allocation rules are per user — you are in user mode and the group lens does not apply.
- Waiting for seat usage — providers are connected but no usage has landed.
- Group membership is still loading — figures will settle in a moment.
Budgets vs. Actual
Reachable from the second tab, or directly with?view=actual. The header reads Track & Forecast: AI seat spend with a rolling daily forecast.
Period summary
Controls
- Forecast horizon — 14 days, 30 days, 2 months, or 3 months. It defaults to 3 months. Training history scales with the horizon, so a longer projection is fit on more history rather than extrapolated from a couple of weeks.
- Group filter — narrow the forecast to one allocation group, or leave it on All groups.
- Scope — All Project Usage, My Department, or My Usage. You only see the scopes you have access to; a seat holder with no admin role sees their own usage.
FAQs
Where did my initial targets come from?
Where did my initial targets come from?
Setup generates them as a monthly, bottom-up budget over 12 periods, starting from the average of your recent monthly spend with no growth applied. If your AI spend history is shorter than the lookback window, the average uses whatever months exist.
Why don't Seat spend and the period actual match?
Why don't Seat spend and the period actual match?
They are different sources on purpose. Actuals come from the Explorer report behind the budget; Seat spend is live period-to-date spend straight from the provider API. Within a period, the live figure moves first.
Can I edit targets on the Vendor view?
Can I edit targets on the Vendor view?
No. Vendor is a read-only roll-up. Targets are edited on the Group view.
Can I set alerts on this budget?
Can I set alerts on this budget?
Yes — it is a normal nOps budget. Configure threshold alerts from the budget itself. See Budgets.
My targets say they're stale.
My targets say they're stale.
That happens after the underlying allocation changes. Regenerate targets so they match your current groups.