In this guide 6 sections
Per seat billing is easiest to run and forecast, usage billing tracks cost but brings disputes, and flat fees are simplest for customers but hide heavy users. Choose by what you can meter reliably, how much invoices may vary and how your customers buy.
Per seat is the easiest to bill and the easiest to forecast
You count named users on the first of the month. The number changes slowly, so next quarter’s revenue is close to this quarter’s. Invoices rarely surprise anyone. Finance likes that.
The trouble starts with the definition of a seat. Is it a named person, a concurrent session, or a login that was active in the last thirty days? Inactive accounts cause most arguments. Define them early.
Per seat also pushes customers to share logins. If your product has an audit trail, that habit becomes a security issue for them and a revenue leak for you.
- Billing effort: low, one count per period
- Forecast accuracy: high
- Dispute source: inactive and shared seats
- Risk: heavy users cost more than they pay
Usage billing follows your costs but needs a meter you trust
Usage can mean API calls, gigabytes stored, minutes of compute, messages sent or records processed. Pick the unit your cloud bill also grows with. Then your margin holds when a customer scales. Otherwise it thins.
The meter has to be correct, retained and explainable. Events must be deduplicated. Late events need a rule. Time zones and cut off times need a rule. A customer will ask why Tuesday’s count differs from their own log. Be ready.
Forecasting is harder. One large customer’s batch job can swing a month. Offer usage alerts and a monthly cap so nobody opens an invoice in shock. Surprises kill renewals.
Flat fee is the simplest to sell and the hardest to defend
One price, one line, no counting. Easy. Buyers with a fixed budget like it, and procurement approves it quickly.
The risk sits with you. Plan for it. A customer with ten users and a customer with ten thousand pay the same unless you set tiers. Most flat plans end up with fair use limits, which brings counting back in through the side door.
Flat works when your cost per customer is steady and the product has limits that matter little, such as a small reporting tool or a fixed support bundle.
- Billing effort: lowest
- Forecast accuracy: high
- Dispute source: fair use limits
- Risk: a few heavy customers erode margin
Compare the three on the problems you actually have
Do not choose from a pricing blog. Use your own data. Open your last twelve invoices and list every credit note you issued. Group them by cause. If most are about seat counts, you have a definition problem. If most are about volumes, you have a metering problem. Different fix.
Hybrid models are common. A base platform fee, an included seat bundle and usage above a threshold. They suit mixed customers but triple the number of fields on the invoice and the rules in your billing system.
Ask your billing tool whether it can rate usage in tiers, apply minimum commitments, prorate seat changes and show the meter data on the invoice. If not, price the model your tool can run. Anything else becomes spreadsheet work.
Test the model before you roll it out
Take five real customers and recompute last quarter under the new model. Compare revenue, invoice size and the questions each would ask. Two who would pay far more need a plan, not a surprise. Call them first.
Write the dispute rules before launch: who reviews a meter query, how long it takes, how credits are issued.
Your next step is a single spreadsheet with those five customers and three columns, one per model, so the trade offs sit in front of you in numbers.
Pricing model comparison worksheet
Printable grid with five customer rows and three column groups for seat, usage and flat pricing. Each group shows the recomputed invoice, the change from last quarter and the likely customer question. A side box lists the seat definition, meter unit, cap and dispute owner.
Open a blank worksheet to printQuestions owners ask
Which pricing model is best for a new SaaS product?
Per seat or a simple tier is usually easiest to start with. Move to usage only once you can meter reliably and explain every line on the invoice.
Can I mix per seat and usage pricing?
Yes. A platform fee with included seats and a usage charge above a threshold is common. Your billing system must support tiers, minimums and proration.
How do I reduce billing disputes under usage pricing?
Show the raw meter data next to each invoice line, send usage alerts before the cut off and publish the rules for late events and time zones.
When does flat pricing fail?
When a few customers use far more than the rest. Without limits or tiers, your costs rise while their price stays fixed.