Quick answer
Cursor spend has two parts: fixed seat cost and variable on-demand usage. Track them in separate columns, because a rising bill is usually on-demand rather than seats. The Cursor admin console provides per-member usage, and a local tracker adds project-level detail where sessions allow it.
The columns to keep
| Column | Source | Why |
|---|---|---|
| Seats | Admin console | Fixed cost |
| Included usage consumed | Usage tab | Efficiency |
| On-demand spend | Billing | Variable cost |
| Period dates | Billing | Comparability |
| Active members | Usage report | Wasted seats |
A monthly process
- Export seats and usage for the period.
- Split fixed and variable cost.
- Divide variable cost by active members.
- Compare with the previous period, noting plan changes.
- Flag members with seats and no usage.
- Set a spend cap if the account supports one.
Avoid the common errors
- Mixing a plan change with a behaviour change in one chart.
- Comparing a partial month with a full one.
- Ignoring on-demand because it is a small line until it is not.
- Ranking people instead of workflows.
UsageAtlas keeps on-demand spend and plan usage visible per machine, which is the detail the admin console lacks.
A monthly review that takes ten minutes
- Export seats, included usage, and on-demand spend for the period.
- Split fixed seat cost from variable spend.
- Divide variable spend by active members.
- Compare with the previous period and note plan changes.
- Flag seats with no usage.
- Set or adjust a spend cap.
Ignore per-request price when reviewing. It changes with model choice and hides the two levers that actually move the bill: seats and on-demand usage.
UsageAtlas records the reported plan usage per machine. See plans compared for the tier decision.
Questions, answered
Can I export Cursor billing data?
The admin console provides invoices and usage reports for teams. Check the current export options in the billing section.
Why did Cursor spend jump without new seats?
On-demand usage after the included allowance is the usual cause. Check the per-model split for premium model growth.
Should we allow on-demand billing?
Allow it with a cap if blocked work costs more than the overage. Without a cap, a single heavy month can be expensive.