Part 7 of 12 · 1 min read
How to build it so it holds up
- Measure cost per task and per resolved task from traces, split by model, tools, infrastructure and credits.
- Define "resolved" precisely before you price on it, and have a dispute path.
- Set the floor from cost and the ceiling from customer value, then price between them.
- Model your customer distribution, especially the heavy tail, before choosing seat pricing.
- Use caps and quotas (Level 11 module 7) so one customer cannot turn a flat price into a loss.
- Offer included usage plus overage when customers want predictable bills.
- Re-run the numbers whenever model prices, caching or resolution rates change.
- Watch the failure and escalation mix, not only token spend.
- Show customers their usage so billing is explainable.
- Recompute any cost figure you copy; the arithmetic is easy to get wrong.