Pay-per-Use vs per-seat licensing: a mid-market CFO's guide to metered enterprise software

Per-seat licensing is the default because it is the easiest line to put on an order form, not because it is the most accurate way to price software. For mid-market CFOs negotiating renewals in 2026, the gap between "what we pay for" and "what creates value" has become hard to ignore.

What per-seat actually charges for

Per-seat charges for the right to log in. The price is the same whether the user runs three transactions a quarter or three thousand. The model has three practical consequences:

• Onboarding gets rationed. Adding a casual user requires budget justification, so people who would have benefited from light access never get it.
• Phantom users persist. Departing employees stay on the licence count until the next renewal sweep, because deprovisioning saves nothing this month.
• Renewals disconnect from usage. The annual true-up is a negotiation about future seats, not a reflection of past value.

For software with predictable, fixed-team usage - a single-purpose tool that ten people use every day - per-seat is fine. For a multi-module platform where Procurement spikes during sourcing season and Payroll runs once a month, per-seat overcharges every team that does not happen to be the peak user.

Four meters that match value creation

DivetIQ's Pay per Use meters four units, each tied to a real cost driver.

1. Per-transaction - invoices matched, journal entries posted, work orders closed, sales orders processed. The unit is whatever the module produces.
2. Per-API-call - external integrations and headless clients are billed by the call. Internal calls between modules are not.
3. Per-agent-action - each specialist-agent execution is metered, with the autonomy threshold priced in. A fully autonomous action costs differently from one queued for human approval.
4. Per-GB - storage tiered hot, warm and cold, priced separately. Documents that nobody opens after archival cost a fraction of documents in active use.

Modules turn on and off independently. Pause CRM in the off-season; scale Procurement during sourcing windows. The bill follows the business.

What a real Pay-per-Use invoice looks like

A representative monthly invoice for a 250-employee mid-market customer in March 2026 - eight modules, agent actions, hot/warm/cold storage, 18,400 conversational analytics queries against the AI-BI/DW - lands at €5,644.80. No mystery line items. Every charge maps to either a transaction, a call, an agent action or a gigabyte.

What to insist on when evaluating any metered-pricing vendor:

• Real-time cost observability per module, per team, per workflow, per query.
• Anomalous-cost alerts before the month closes, not after.
• Dry-run estimates for any reverse-ETL pipeline or batch job before it touches production.
• Per-action agent pricing disclosed, not bundled into a flat AI tax.

Per-seat asks a CFO to forecast headcount. Pay per Use asks a CFO to forecast what the business will do. The second forecast is harder, but it is the one the CFO is already making. Stop translating it through a licence count.