Seats Plus Usage Pricing
One unified bill for the subscription, the usage limit it includes, and the usage add-ons customers buy on top. Control every plan, seat, and add-on by configuration — not engineering sprints.
One Unified Bill
Seats, usage limits, and add-ons — one bill
Most B2B SaaS and AI platforms do not sell pure seats or pure usage — they sell both. A plan includes a number of seats and a usage allowance; customers who need more buy usage add-ons on top of their subscriptions, either for the whole team or for individual users. All of it needs to land on one clean, correctly rated invoice.
That means controlling every feature in the plan, measuring every feature’s usage — whether it is billable today or you are just exploring its monetization potential for later — and turning features, limits, and add-ons on or off without waiting on a release.
How It Works
What seats plus usage pricing looks like
Any pricing page you can design — pooled, per-seat, or both at once — needs a backend built to run it.
Shared pool across all seats
Each seat is really a subscription with a usage allowance built in. Every seat draws from the same shared pool, and the whole team burns it down together.
25 seat subscriptions share 1M tokens/month included in the plan.
Per-seat limits within the pool
Cap what any individual seat’s subscription can draw from the shared pool, so one heavy user cannot burn through the team’s whole allowance.
Pool: 1M tokens/month. Per-seat cap: 100K tokens.
Add-ons at the pool or seat level
Sell extra usage to the whole account when the shared pool runs low, or let individual users buy their own top-ups.
Team add-on: +250K tokens. Per-user add-on: +25K tokens.
AI agents count too
As AI agents increasingly call your APIs on a user’s behalf, that usage needs tracking and metering just like usage from a human seat — so it stays part of the plan.
Agent-driven API calls are tracked as usage against the same plan.
Meter now, bill later
Track every feature’s usage from day one, whether or not it is billable yet — so you can switch on monetization for a feature the moment you are ready, without waiting on engineering.
Usage is captured for every feature; billing rules apply only to the ones you turn on.
Configured, not coded
Turn features on and off, change the usage limits included with a plan, and launch new add-ons — all through configuration. No engineering sprint required to ship a pricing change.
A new add-on or limit change takes effect immediately from the control plane.
Seats plus usage is one hybrid pattern among several — explore hybrid licensing models and their monetization potential.
Why It's Different
A traditional metering tool won’t cut it
What we’re describing has traditionally taken long engineering sprints to go from spec to reality. There is no time for that in a market where competitors move fast and AI features carry variable, changing costs to the vendor.
If you need hybrid pricing across different product tiers — sold by the seat, but with usage limits — you need a backend system designed to do exactly that. That’s what Zenmeter is: entitlements and metering built for seats plus usage, connected to the plans you control and the billing platform you already run.
Design your seats plus usage plan
Our team can help you design a seats plus usage model and put it on infrastructure that changes by configuration, not code.
FAQ
Seats plus usage FAQ
Any pricing plan you can design, we can power
Pooled allowances, per-seat limits, and add-ons that apply wherever you need them — configured, not coded.