A pilot with twenty users costs almost nothing. The same platform, rolled out to two thousand users with agents running in the background, is a different financial product entirely — and most teams only discover that after the rollout is already committed.
The three cost curves nobody models
Usage-based pricing creates costs that grow with success, not with value:
- Adoption penalty. Every new user is a new line item, so the finance team ends up rationing the tool that was supposed to raise productivity.
- Automation penalty. Background agents are the highest-value use case and the highest-volume consumer of tokens. Usage pricing taxes exactly what you want more of.
- Retry and context tax. Long context windows, retrieval passes and retries multiply consumption invisibly. Nobody budgets for the third attempt.
How to compare properly
When you compare a SaaS assistant with a self-hosted platform, model the second year, not the first month.
| Dimension | Usage-based SaaS | Self-hosted platform |
|---|---|---|
| Cost driver | Users, tokens, features | Fixed license + infrastructure |
| Budget predictability | Recalculated every quarter | Known in advance |
| Cost of scaling agents | Grows linearly | Marginal |
| Exit cost | Data and workflows are hostage | Portable by design |
The practical takeaway
The right question is not "what does a million tokens cost?" — it is "what does it cost when this works and everyone uses it?" Fixed-license, self-hosted platforms flip the incentive: you optimize for adoption instead of rationing it.