About the Seat-Based Pricing Revenue
This calculator projects recurring revenue for a per-seat pricing model, the structure many SaaS companies use where customers pay based on how many users (seats) they activate on an account. Given the number of accounts, the average number of seats per account, and the price charged per seat, it produces the resulting monthly and annual recurring revenue along with the total seat count.
How It Works
Enter the number of paying accounts, the average number of seats each account uses, and the monthly price per seat. The calculator multiplies accounts by average seats per account to get total paid seats, then multiplies that by the price per seat to get Monthly Recurring Revenue. It also multiplies MRR by 12 to show the annualized figure.
Formula & Methodology
Because the model multiplies three inputs straight through with no discounting or rounding logic, the math scales linearly: doubling either the account count or the average seats per account doubles revenue, all else equal. To model a blended or discounted rate, common when larger accounts negotiate volume pricing, run the calculation separately for different account segments at their respective seat counts and price points, then add the resulting MRR figures together rather than averaging the price per seat across the whole base.
Examples
Mid-Market SaaS Base
With 200 accounts averaging 8 seats each at $12 per seat per month, total paid seats reach 1,600, producing $19,200 in MRR and $230,400 in ARR.
Smaller Accounts, Higher Price
With 50 accounts averaging 15 seats at $8 per seat, total seats reach 750, producing $6,000 in MRR and $72,000 in ARR.
Advantages
- Turns three simple inputs into both MRR and ARR without needing a spreadsheet.
- Makes it easy to model how revenue shifts if average seat adoption per account grows or shrinks.
- Useful for quickly comparing the revenue impact of a price-per-seat change across the existing account base.
Common Mistakes
- Using a single blended price per seat when the actual customer base has multiple pricing tiers, which overstates or understates total revenue.
- Forgetting that seat count and seat usage aren't the same thing; a customer can pay for seats that go unused.
- Applying an average seats-per-account figure calculated from a different period than the account count, mismatching the two inputs.
Edge Cases to Watch For
- There's no minimum-value guard on any input, so an account count, seat average, or price of zero simply produces zero revenue rather than an error.
- The model assumes every seat is billed at the same flat rate; it doesn't account for tiered or volume-discounted pricing that many per-seat vendors offer to larger accounts.
- Average seats per account can mask a wide spread between small and large accounts; two customer bases with the same average can have very different revenue concentration.
Common Use Cases
- SaaS finance and revenue operations teams building quick recurring revenue projections.
- Sales leaders estimating the MRR impact of landing a new segment of accounts.
- Pricing teams modeling the revenue effect of a proposed per-seat price increase.