How per-seat pricing works
Each subscription carries a seat count, and the bill for a period is the seat count times the price per seat. A team of 8 on a $15 seat price pays $120 a month; a team of 9 pays $135. The price per seat can be the same at every size, or it can fall as the team grows through volume or tiered pricing.
Seats rarely stay still. When a customer adds seats partway through a period, the new seats are prorated: they cost only the days left in the period. When seats are removed, the unused days become a credit, or the removal waits until the renewal, depending on your policy.
Larger contracts sometimes use a true-up instead of changing the bill every time. The customer commits to a seat count for the year, adds people freely, and at the end of each quarter or year the seats added above the commitment are counted and billed in one go.
bill for the period = seats × price per seat
prorated charge for added seats = seats added × price per seat × days remaining ÷ days in the period
Worked example
A support team pays $15 per seat per month for 8 seats. On June 21 it adds 4 seats. June has 30 days, and 10 of them remain, counting the 21st.
- June 1: 8 seats × $15
- $120.00
- June 21: 4 new seats × $15 × 10 ÷ 30
- $20.00
- Billed for June
- $140.00
From July 1 the invoice is 12 seats × $15 = $180.00 a month.
Why per-seat pricing matters
Per-seat pricing is easy to understand on both sides. The buyer knows what one more colleague costs, and your revenue grows as the product spreads through a team, without a new sales conversation each time.
It fits products where value follows people: collaboration tools, CRMs, help desks. It fits less well when one user can get most of the value alone, because customers then share logins to keep the seat count down.
Common mistakes
- Billing new seats for the full month A seat added on the 25th that costs a whole month feels like a penalty for growing. Prorate by the day, or wait for the renewal.
- Refunding removed seats as cash by reflex A removed seat usually becomes a credit on the next invoice, or the removal takes effect at renewal. Decide the rule before the first customer asks.
- No link between seats billed and seats used If the product lets a customer invite more people than they pay for, the bill and reality drift apart. Enforce the seat limit or bill from the actual count.
- Pricing seats that nobody needs When most of the value comes from one user, seats push customers to share a login. Consider flat or usage pricing instead.