Per-Seat Pricing: Calculate Minimums, Guests and Renewal Costs
Calculate software seat costs with documented Slack, Notion and monday.com billing rules, a headcount worksheet, and examples of annual renewal commitments.
Per-seat software cost starts with the number of billable seats, which can differ from both employee headcount and active users. A useful estimate also needs the seat minimum or bundle, guest rules, billing interval, and what happens when someone leaves. Multiplying the advertised rate by today’s staff count misses those differences.
Correction, September 25, 2026: an earlier version described an unsupported studio experience and an alleged 8–14% cost overrun. Those claims and the blanket 10% surcharge have been removed. This guide uses documented billing policies and explicitly hypothetical calculations; it is not an account of tested invoices.
Illustration only; the pictured amounts are not a vendor quote or a measured bill.
Three billing policies that change the calculation
The following official documentation was checked on September 25, 2026. The comparison concerns billing mechanics, not current subscription prices. Confirm your exact product, plan, purchase channel and contract before applying a row to your account.
| Service and scope | Documented rule | What to put in the estimate | Official source |
|---|---|---|---|
| monday.com, plans covered by its pricing guide | Paid seat packages start at three, then increase in multiples of five. | Use the available package that covers the required billable users; a six-user requirement can mean a ten-seat purchase. | Plans and pricing |
| Notion, paid workspaces | Added seats are prorated; removals reduce billing at the next billing interval. Unfilled paid seats can be reassigned during the current interval. Each paid workspace is billed separately. | Track purchased capacity and renewal dates per workspace, including unused seats available for replacement staff. | Billing |
| Slack, website purchases paid by credit card or self-serve invoicing | Its Fair Billing Policy gives prorated account credits for inactive paid members. Multi-Channel Guests are paid; Single-Channel Guests are free. | Separate paid roles from free roles and credits from cash refunds. Credits are non-refundable and expire when the paid plan terminates. | Fair Billing Policy |
The policies do not support a universal churn surcharge. One account can retain paid capacity until renewal; another can receive credits. A percentage added to every quote hides the distinction and can double-count a cost already included in committed seats.
Notion also documents page-level guests, subject to plan limits, as an alternative to adding a paid member. That does not make a guest interchangeable with an employee account: first establish which pages and permissions the person needs. In Slack, the distinction between single-channel and multi-channel access similarly affects billing. A role label without its access scope is an incomplete budget assumption.
Build the seat count before choosing the rate
Create one row per workspace or separately billed account. List the people who need access, their required role and their expected access dates. Include external collaborators, but do not automatically count all of them as paid users. Conversely, do not assume everyone outside the company qualifies for free guest access.
For a simple plan with a minimum but no seat bundles, the starting calculation is:
Billable seats = maximum of the minimum purchase and required paid users.
Required paid users already includes any collaborators who need paid roles. Add those collaborators before applying the minimum. For example, two employees plus one paid contractor under a three-seat minimum occupy three seats, not four. Adding the contractor after the minimum would count an unused place twice.
For a bundled plan, round that required count up to the next available package. Keep the package schedule in the worksheet instead of assuming that every extra employee adds exactly one seat to the invoice. For mixed seat types, calculate each type separately using its own price and purchase rules.
Then identify the least expensive tier that actually covers the required workflow. A cheaper tier missing a required permission or export capability is not a comparable quote. Record the feature that forces an upgrade, with a documentation link, rather than assuming every tool has the same expensive feature boundary. The broader pricing audit checklist can help organise the questions, but the vendor’s current checkout determines the payable amount.
A worked example with explicit assumptions
Everything in this example is hypothetical. It is not a monday.com, Slack or Notion price. Assume a fictional tool sells individual seats with a three-seat minimum, charges $15 per seat per month on an annual commitment, and offers no removal credits during that year. There are no taxes, extras or discounts in the example.
Two employees start on January 1. Two more employees and one collaborator requiring a paid role join on July 1. Treat July through December as exactly six months for this simplified calculation; an actual invoice may prorate by days.
| Event | Seat calculation | Cash charged in this example |
|---|---|---|
| January 1 purchase | Three seats × $15 × 12 months | $540 |
| July 1 expansion to five people | Two additional seats × $15 × 6 months | $180 |
| Total for the first year | $540 + $180 | $720 |
| Next renewal, if all five remain | Five seats × $15 × 12 months | $900 |
The initial two-employee shortcut gives $360, which understates the $540 opening commitment. The first-year total averages $60 per month, while the next renewal averages $75. These are three different quantities: initial commitment, first-year spending and renewal cost. Calling all of them the monthly bill makes the comparison hard to audit.
Suppose one of the five people leaves on October 1 and nobody replaces them. Under the fictional no-credit assumption, the first-year spending stays $720. The unused seat represents $45 of already purchased capacity for October through December. Do not add that $45 again to the $720: it is a portion of that total. If four people remain at renewal, the next annual purchase is $720 rather than $900.
A policy that issues account credits would need a separate credit line and the date on which it can offset a charge. A credit balance is not necessarily money returned to a bank account. Keep that distinction visible when comparing an annual commitment with monthly billing; the annual-plan calculation addresses the wider commitment decision.
Copy this worksheet for an actual quote
Use one sheet per candidate tool and the same staffing scenario for every candidate. Store the dated source beside the assumption so another person can reconstruct the result without trusting your memory.
| Input | What to record | Evidence to keep |
|---|---|---|
| Product and plan | Exact tier, currency, region and purchase channel | Checkout or written quote |
| Paid roles | Employees and collaborators needing each seat type | Access requirements and role documentation |
| Free roles | Eligible guests or viewers and their limits | Guest policy for that plan |
| Purchase floor | Minimum or next available seat package | Pricing guide and selected package |
| Billing unit | Per user, workspace, account or other unit | Billing documentation |
| Commitment | Start, renewal and reduction-effective dates | Subscription settings or order form |
| Changes | Join/leave dates and reusable vacant seats | Staffing scenario and proration rule |
| Other charges | Add-ons, usage allowances, overages and taxes shown | Quote line items |
| Credits | Amount, restrictions and application date | Credit policy and billing statement |
Calculate three scenarios: today’s staffing, the expected staffing path, and a plausible contraction. Label these as scenarios, not forecasts. A small contractor-heavy team may need a different contraction case from a stable full-time team; an arbitrary standard percentage does not capture either one.
For a first pass, total the initial payment, subsequent seat additions and other charges, then subtract credits actually applied within the period. Keep unused credits in a separate balance. For a monthly plan, sum the individual monthly amounts rather than multiplying the largest month’s bill by twelve. That makes a temporary project visible instead of turning it into an assumed permanent expense.
Check the estimate against one billing cycle
Before committing, ask the account owner to confirm the selected seat package and renewal date. Check whether an invitation creates a paid member immediately or only after acceptance, and whether adding someone can reuse an already purchased seat. Save a preview of the charge where the product provides one. Do not invite a test user solely to investigate billing if the action itself can incur a charge.
After the next invoice, compare each difference with the worksheet: seat count, rate, days prorated, add-ons, tax and credits. Correct the specific assumption that was wrong. An unexplained adjustment should remain unexplained until the billing record or vendor support resolves it; turning it into a generic overhead allowance makes the next estimate less useful.
Removing access and reducing a subscription are separate checks. A departed person should not retain access merely because their seat is prepaid, and cancelling a seat does not itself establish that their files have been transferred. Include ownership and export steps in the migration checklist.
A good final comparison states the amount due now, expected payments during the chosen period, and the renewal commitment under the stated headcount. Those three numbers give a team something concrete to approve and later verify.



