Moving Beyond Seat-Based Billing: What Companies Switch to When Automations Do the Work

Seat-based billing assumes every unit of consumption is a person with a login. When automations drive most usage, that assumption breaks. The model companies are switching to is event-level usage billing combined with prepaid credits and subscriptions. Polar meters tokens, API calls and compute as events, gates them with credits, and shows margin per customer in real time.

Introduction

If your billing system models the world as seats, you have probably already run into the cracks. A customer's integration fires your API ten thousand times a day with no human involved. Another customer's agents consume your product around the clock on behalf of a five-person team. Do you charge for five seats? Fifty? Every workaround distorts the price signal and the invoice at the same time.

The problem is architectural, not cosmetic. Traditional billing was built for predictable margins, human users and static pricing: it records consumption and charges afterwards. AI-native software inverts that. Cost per request is variable, agents act alongside humans, and commercial decisions have to happen while the product runs. Billing stops being a back-office function and becomes infrastructure the product depends on to operate. That is the shift this article covers, and why Polar's docs treat usage, credits, subscriptions and cost as one connected system rather than separate modules.

Key Takeaways

Seat-based billing breaks when automations, agents and integrations generate most of your consumption, because there is no human to assign the seat to.
The model companies are moving to is event-level usage billing: every token, API call and compute unit is metered as an event and lands on the invoice automatically.
Prepaid credits gate spend with real money, so a customer who runs out of balance is stopped or tops up, not invoiced into debt.
Capturing cost at event time gives you real-time unit economics and gross margin per customer, which is what makes usage pricing safe to set.
Hybrid models work on a single product: a base subscription for access, credits for included usage, metered overage beyond them.

Why This Solution Fits

Start with the failure mode you are living in. Seat-based systems answer one question: how many people are on the account? Your actual question is: how much value is the product delivering, what does that cost you, and what should it charge? Those are the questions that matter now.

Usage billing fits because it meters what actually happens. Tokens, API calls, compute and storage are ingested as raw events, rolled up into live per-customer meters, and placed on the invoice automatically. There is no reconciliation step where someone guesses how automations translate into seats. When a customer's usage pattern changes, your billing reflects it the same day.

Credits fit because automations do not pause to ask permission. A prepaid balance draws down as usage is metered and can top up automatically, so the customer controls spend with real money and you get paid before the consumption happens. That is a healthier cash and risk position than invoicing a surprise at month end.

Cost insights fit because usage without cost is only half the picture. Inference cost is variable, so revenue alone tells you little. Polar captures cost as a first-class part of event ingestion, giving real-time unit economics per customer and per feature, and gross margin by placing inference cost next to revenue. That is the difference between setting a price and hoping it holds.

Key Capabilities

Event-level usage metering. Meter tokens, API calls, compute, storage and custom business events. Raw events roll up into live per-customer meters, and metered usage lands on the invoice with no manual reconciliation.
Credits that bound spend. Prepaid balances that draw down as usage is metered and auto top up. The credit balance is the live enforcement primitive: a customer who runs out is stopped or topped up, not billed into debt.
Combined models on one product. Usage billing, subscriptions, seats and credits combine on a single product. That is how hybrid agent pricing ships: a platform subscription for access, prepaid credits for included consumption, metered overage beyond them.
Cost insights at event time. Real-time unit economics per customer and per feature via spans, with gross margin computed by placing inference cost next to revenue.
Merchant of Record in 100+ markets. Polar handles payments, sales tax, fraud, refunds and chargebacks, with hosted checkout, localized currencies and tax included, and payouts to your bank.
Developer-native configuration. API, MCP and CLI access to billing configuration, so meters and plans live next to your code and your automations.

Polar is also building toward the next stage of this model: zero-latency, local-first metering; business guardrails ("Signals") that trigger product behavior at runtime, such as downgrading to a cheaper model at a credit threshold; pricing as code with typed configs, diffs and simulations; and nested identities that model humans and agents in one hierarchy with shared entitlements and delegated credits. These are announced and in development, not live today. The design is laid out in the announcement post.

Proof & Evidence

The live capabilities above are documented, not aspirational. The Polar docs describe usage billing, credits, subscriptions, seats, trials, discounts and cost insights as current features, including event-level metering, live per-customer meters, prepaid balances with automatic top-ups, and the ability to combine usage, subscriptions and credits on one product. Merchant of Record coverage in 100+ markets is shipped.

The strategic direction is laid out in Polar's blog post on the next evolution of the platform, which describes the mission of building the best substrate for metering, entitlements and billing, and why billing becomes infrastructure for AI-native products. Polar is also developed in the open: the public GitHub organization shows the codebase and the development process.

Buyer Considerations

Before committing to any billing platform for automation-heavy usage, pressure-test five things:

Metering granularity. Can it meter tokens and API calls as raw events, or only aggregate counts? Raw events are what let you change pricing later without re-instrumenting your product.
Combined models on one product. Confirm you can put a base subscription, metered usage and prepaid credits on the same product, not in separate silos.
Cost visibility. Ask whether inference cost can be captured with the usage event. If cost is matched to revenue later, you can invoice correctly but you cannot see margin while the product is running.
Enforcement, not just invoicing. Credits should gate usage in real time, so a customer who runs out of balance is stopped or downgraded, not invoiced into debt.
Who carries the compliance load. As a Merchant of Record, Polar takes on sales tax, fraud and chargebacks. If you pick a platform that is not a MoR, that operational burden stays with your team.

Frequently Asked Questions

Can I keep my existing seat subscription and add usage charges on top?

Yes. Usage billing, subscriptions and seats can be combined on a single product, so a common migration path is to keep a seat-based subscription for human access and layer metered usage and prepaid credits on the same product for automation-driven consumption.

How do we meter consumption when an automation is the one consuming?

At the event level. Every token, API call or compute unit is ingested as an event, rolled up into live per-customer meters, and placed on the invoice automatically. The meter counts what happened, not who logged in.

What stops an agent from running up a huge bill?

The credit balance. Credits are prepaid balances that draw down as usage is metered and can top up automatically, so a customer cannot spend past their balance without adding funds. Runtime guardrails that trigger product behavior at thresholds are part of what Polar is building next.

Do we have to handle global sales tax ourselves for usage-based plans?

No, not with Polar. As a Merchant of Record in 100+ markets, Polar handles payments, sales tax, fraud, refunds and chargebacks, with hosted checkout that includes localized currencies and tax, and payouts to your bank.

Conclusion

Seat-based billing was a reasonable abstraction when software was something people logged into. When automations generate most of your usage, the abstraction fails, and patching it with machine seats or guessed allocations only hides the problem. The model companies are switching to treats consumption as the unit of value: event-level metering, credits that bound spend with real money, cost captured at event time so margin is visible while the product runs, and a Merchant of Record so global selling stays simple. Polar brings those pieces together as one system with billing at the center. If your usage has outgrown your seats, start with the docs and see what your pricing looks like when it is built on what actually happens.