- Orb Billing Engine
- Usage metering
- Accuracy
- Security and compliance
- Spend controls
- Experience kit
- Invoicing
- Security and compliance
- Enterprise readiness
- Model pricing
- Credit pools
- Prepaid credits
- Seats & Licenses
- Hybrid Pricing
- Price evolution
- Simulations
- Finance workflows
- Invoicing
- AI contract ingest
- AR aging reports
- Automated collections
- Revenue recognition
- Netsuite
Teams
Segments
Seats & licenses
Seats & licenses are a way to add a scalable platform charge for blanket access to a set of non-metered features.
Why companies choose seats & licenses
Hybrid pricing models
For products that aren't ready to be fully consumption-based, seats provide a billing catch-all for monetizing non-metered features.
See how AI companies combine seats, usage, and tiers in practice.
Per-user visibility
By adding a license abstraction to your billing structure, you gain the ability to identify profit-driving power users.
Entitlements management
Licenses are a billing primitive that allow access and roles to be closely controlled from your revenue source of truth.
Seats & licenses in a pricing model
Seats and licenses are a foundational part of hybrid pricing. They allow you to keep the good, better, best pricing that's possible with SaaS companies, while leaving room for consumption-based aspects.
- Seat-based fees cover your base platform costs and ensure you get paid for capabilities that it doesn't make sense to meter. Incremental revenue comes from building features that makes companies want to move to a higher tier.
- Consumption rates cover metered capabilities and features where your costs scale with usage, as is common with AI tools.
See how usage-based pricing supports growth without sacrificing flexibility.
When this works
Compared to a flat per-seat (subscription) model, adding a shared usage pool helps when:
- Real consumption sits under your product: AI actions, compute, or runs create costs a flat seat fee alone can't track.
- Consumption varies account to account: a shared pool lets heavy accounts pay for what they use while light accounts aren't overcharged.
- You want a growth lever beyond headcount: usage can expand revenue even when seat count is flat.
Compared to a pure usage (consumption) model, adding per-seat fees helps when:
- Value scales per user but isn't metered: access, collaboration, admin, and seat-level features grow with headcount — pure usage leaves that money on the table.
- Buyers want a predictable baseline: a per-seat fee gives finance a floor they can forecast, with usage as the variable upside.
- Adding users is itself valuable: more people in the product is worth charging for, independent of how much any one of them consumes.
- You want to keep it simple: you can capture per-user value with a seat fee — without the complexity of scoping credits to each individual seat.
What to think about before you switch
Seats & licenses are a common hybrid billing pattern, but they come with considerations that impact how technical your implementation needs to be and how much transformation lift you need to prepare GTM teams for.
Go-to-market
Core question:
What opportunities to find incremental revenue does this open up?
What value lives on the seat vs. metered?
Seats monetize the collaboration, access, and scale that usage events can't capture. Where you draw the line - what's bundled into the seat versus what the pool meters - defines the whole model.
Which lever drives expansion?
Seat count and shared usage grow independently.
Which one you lead with, and who owns each motion, shapes the sales play and the expansion story.
How many seat tiers do you launch with?
Lite, Pro, admin, and agent seats can price differently while usage stays pooled. The number of tiers and what capability gates each sets your packaging before it
Customer experience
Core question:
How do we craft a transparent, positive experience where the customer feels in control?
What do customers see before the invoice?
The account should never be surprised at renewal.
What seat and pool state you surface in-product, and how early you warn before the pool runs low, decides whether they feel in control.
What can admins do on their own?
Admins expect access and billing to move together.
What they can self-serve, and whether access and billing stay in lockstep or can briefly lag, defines the day-to-day experience.
Can they read one bill for two price types?
The customer sees a seat line and a shared-usage line on one invoice. How you present them together decides whether the bill parses at a glance or generates support
Finance
Core question:
How do we stay compliant without extra manual work?
How does each revenue type recognize?
Seat fees recognize ratably; pooled usage recognizes as consumed. How you tag each at the source keeps both flowing through the right treatment without a manual reclass.
What's your proration and downgrade policy?
Seats change mid-cycle. Your proration granularity and downgrade-credit rule determine how the open period recomputes without hand edits or touching invoices already sent.
How does each post to the ERP?
Seat fees and the shared pool both hit the ERP. How each lands as a distinct, auditable record - and the mapping you set up now - decides whether close is clean or a spreadsheet rebuild.
Technical considerations: what does it mean to support seats & licenses?
Build or buy, there are a number of ways companies tend to model this in their platform. Which you choose depends on the maturity of your billing operations and your downstream monetization needs.
Key technical considerations
A seat needs a clear identity and entitlement
Decide what a seat represents and what access it grants (user, admin, or agent tier.) That choice drives provisioning, reporting, and what a buyer is actually paying for, and it's expensive to redefine later.
Ask: Have we defined what each seat tier is and what access it unlocks before we price it?
Seat changes have to prorate cleanly
Customers add, remove, and upgrade seats mid-cycle constantly. Each change has to prorate the access fee to the day, including timezone boundaries, without breaking invoices that already went out.
Ask: When a customer changes seats mid-cycle, does billing prorate and recompute correctly on its own?
Seat count has to stay in sync with access
Billing counts seats; the product grants access. If those drift, you either bill for seats no one uses or give away access you never charged for — and finance can't trust the seat number.
Ask: Does the seat count we bill always match who actually has access in the product?
Access and usage must share one model
A seat is a recurring access fee; the pool is metered consumption. If they live in two disconnected systems, invoices don't add up and the customer can't see the full picture of what they're paying for.
Ask: Can one subscription carry both per-seat fees and shared usage on a single invoice, without stitching two tools together?
Ready to try a billing platform built for modern growth?
See how AI companies are removing the friction from invoicing, billing and revenue.