There's a specific moment that happens to volunteer organizations. Someone finds a tool that would genuinely solve their problem, gets to the pricing page, multiplies by the number of members, and closes the tab.
A per-user price that looks trivial next to a software budget stops looking trivial when you multiply it by a membership. For a rowing club with a hundred-odd members, whose income is subscriptions and a summer raffle, it can land somewhere near the cost of repairing the boats.
The tool wasn't too expensive. It was priced for a completely different kind of organization.
Seats assume salaries
Per-seat pricing makes sense in a company, and it's worth being clear about why. A seat costs a fraction of what the person occupying it is paid. If a tool saves an employee twenty minutes a week, it has paid for itself several times over. Finance approves it without reading the details.
Every part of that logic breaks in a community:
- Nobody is being paid, so there's no salary to compare the cost against
- The people using it most, the volunteers, are the ones you least want to charge for
- Membership is seasonal and lumpy, so the count you're billed on is never the count you have
- The budget is fixed a year in advance by a committee, not adjusted monthly
The result isn't "communities pay more". It's that communities don't buy at all, and keep running on group chats.
What rationing seats does to a community
Faced with per-user pricing, organizations do the rational thing. They buy a few seats for the people who really need them. That decision looks harmless and isn't.
You've now split your community in two. The committee is inside the tool. Everybody else is outside it, receiving forwarded screenshots. The tool that was supposed to bring the community together becomes an administrative back office, and the actual community life continues in the free chat group where it always was.
The moment access to your community's tools depends on a budget decision, the tool stops being where the community is.
Worse, the split hardens. Because the members aren't in the tool, nothing important can live there. Because nothing important lives there, buying more seats never gets approved. You end up paying for a tool that duplicates your spreadsheet.
The two-tier problem is also a fairness problem
There's a quieter issue with seat rationing in volunteer organizations. Who gets a seat becomes a status question.
The committee has one. The head coach has one. Does the parent who organizes every away trip get one? The person who has run the raffle for eleven years? These aren't budget decisions any more, they're decisions about who counts, and no volunteer organization wants to be making them at a Tuesday meeting.
Charging by member creates that conversation. Not charging by member deletes it entirely.
The hidden cost of "just use the free tier"
The usual answer is to stay on the free plan of a tool built for teams. Free tiers are designed as a funnel to a paid one, so they're pruned precisely where a growing community starts to need them: how far back you can search, how many members you can add, what guests can see, whether the member list is really a member list.
So the community grows into the free tier's edges and then stops, or splits across two tools, or quietly goes back to WhatsApp. That cost isn't on any invoice, which is exactly why it's easy to miss.
When per-seat pricing is genuinely the right model
It would be dishonest to pretend seats are always wrong. They're a good fit when:
- The users are paid staff, and the tool saves working time
- The number of users is stable and known
- Access is genuinely tied to a job, so a leaver frees a seat
- You're doing client work, where the tool cost is billable
If your organization has employees using a tool to do their jobs, per-seat pricing is fine and often the fairest option available. A professional association with twelve staff should absolutely pay per seat for its finance software.
The mismatch is specific. It appears when the people using the tool are the community itself rather than its staff.
What to look for instead
If you're choosing a tool for a community rather than a company, the questions worth asking are:
- Can every member get in without anyone approving a cost?
- Does the price move when the community grows, or when the organization's use of it grows?
- If we stop paying, do we lose our history, or just some features?
- Can a member join in the browser without installing anything?
That first one matters most. A community tool that not everybody can join is a back office with extra steps.
It's the reason members join Joyn with an invite link and it's free to get started: we watched the seat-rationing conversation happen too many times to build it any other way. Pricing is only one of the ways community tools mismatch communities, though. The wider version of that argument is why group chat isn't enough.