There's a pricing question that keeps surfacing in the conversations we follow, from very different kinds of teams.
A volunteer at a small nonprofit has been the internal champion for a project tool, and now a change to the free plan limits how many people can even view the work. Moving everyone off it means exports, rebuilt projects and retraining volunteers who barely used it in the first place. Elsewhere, a team notices it's still paying for seats that belonged to people who have already left. An agency wants clients to request, comment on and approve work, but each client login costs the same as a full team member. A tutoring business shopping for a learning platform can't work out whether its freelance tutors count as staff, users or something in between, and whether it'll be billed per learner on top. A designer weighs a site builder where every editor seat adds to the monthly bill. And on the other side of the counter, a small plugin maker explains why it chose to sell unlimited sites for one price while competitors charge per site, and gets a mix of applause and "how will you survive?" in reply.
Same underlying question each time: who should count as a seat?
We don't think there's one right answer, so instead of arguing for one, here are the questions we think are worth talking through. We'd really like to hear where you land.
The occasional user
Most teams have a core of daily users and a long tail of people who show up rarely: a board member checking progress, a client approving a design, an accountant pulling a report, a subject expert reviewing one course module.
- Should someone who logs in twice a month cost the same as someone who lives in the tool?
- Is "view-only is free, editing is paid" a fair line, or does it push teams into sharing logins, which is worse for everyone?
- When a vendor tightens what free viewers can do, is that a reasonable correction or a bait-and-switch for teams who built habits around it?
Clients and guests
For agencies, studios and service businesses, the people outside the team are often the ones who matter most: they request work and they sign it off.
- Should clients be free by default, since they bring the revenue that pays for the team seats?
- Or is it fair to charge for them, because guest features (portals, permissions, notifications) cost real money to build and support?
- If guests are free but heavily restricted, does that just move the cost into your team's time, copying comments out of email?
Freelancers, tutors and part-timers
Seat models assume a clear line between "staff" and "customer". Plenty of businesses don't have one.
- A tutoring company with a few freelance tutors, a coaching business with guest experts, a nonprofit with rotating volunteers: who is a "user" here?
- Is per-learner pricing on a learning platform the same thing as per-seat pricing on a project tool, or a different kind of deal?
- If a contractor needs access for six weeks, how do you handle the seat afterwards, and do you remember to?
Ghost seats
The quietest cost in per-seat pricing is the seat nobody uses.
- Who on your team is responsible for removing people who left? Is it anyone's job at all?
- Should vendors flag inactive seats or offer automatic downgrades, even though that costs them revenue?
- Have you ever found out how many ghost seats you were paying for, and what made you look?
The alternatives, and their catches
Teams describe a few ways around per-seat pricing, each with trade-offs:
- Flat or per-workspace plans. Predictable, but often priced for a team bigger than yours.
- Per-site or self-hosted licences. No per-person cost, but someone has to run the server, handle updates and own backups.
- Unlimited-use pricing from smaller vendors. Generous, but you're betting the vendor's model holds up long enough for you to rely on it.
- Free tools stitched together. Cheap in money, expensive in time, and fragile when one piece changes its terms.
None of these is free. The real question is which cost your team is best placed to carry: money every month, time spent running something yourself, or the risk of depending on a small vendor.
If you sell software
This conversation has a second side. Many of us also price our own products, and the same questions apply in reverse.
- Do you charge per seat because it matches the value people get, or because it's what everyone else does?
- Would you rather have fewer customers paying more, or more customers paying a flat price that grows with sites instead of people?
- How do you make a pricing change without breaking the trust of the people who picked you because of the old model?
Where this leaves us
We don't have a tidy answer. Seat pricing makes sense for tools where every user creates real cost and value. It feels unfair when most "users" are occasional viewers, clients or volunteers. The teams that seem least frustrated are the ones that sat down once, listed who actually needs access and how often, and picked a model that matched that list, rather than the one their last tool happened to use.
Your turn
We'd love to hear your experience:
- In your team, who are the "occasional" users, and do you pay full price for them?
- Have you ever left a tool mainly because of how it counts seats, viewers or guests? What did the move actually cost you?
- If you invite clients into your tools, do you pay for them, share a login, or use something else entirely?
- If you sell software, why did you choose your pricing unit (seats, sites, usage or flat), and would you choose it again?