Who Pays to Keep an Online Community Running?
#group#how-to
Server and tool costs don't fall as membership grows. Dividing them equally collapses the moment some members don't pay, so work the rate back from the share who will. Plus the structure that hides what the organiser is absorbing, and how to fix it.
A Discord server, the online venue for a study group, a fan community run by a few volunteers. Joining is free, and money still leaves someone’s account every month.
Usually exactly one person knows how much. The problem with running costs isn’t the size of the number, it’s that the concentration of it on one person is invisible.
📡 Running costs don’t fall as the group grows
Start from the fact that a community’s costs are almost entirely fixed.
The monthly server bill, the domain renewal, the paid tier of a tool, storage for recordings. Those barely move whether there are 50 members or 200. Only the denominator changes.
That looks like a good structure — more people, lighter share. In practice the opposite happens, because more people means more people who reason that someone else will cover it.
🧮 Work the rate back from the share who pay
Take a community with annual costs of $1,200 and 100 members. Divide and you get $12 each.
That $12 only holds if everyone pays. In a group where membership is free and roughly 40% chip in, the arithmetic changes.
$12 ÷ 0.4 = $30.
Forty people at $30 is $1,200, which is exactly the bill.
| Amount | |
|---|---|
| Annual running costs | $1,200 |
| Members | 100 |
| If everyone paid | $12 |
| Share who actually pay | 40% |
| Rate you actually need | $30 |
Announce $12 and you will raise $480. Build the payment rate into the number before you publish it. There’s nothing scientific about 40%; use last year’s figure if you have one. In a first year, estimate low and accept that the organiser tops up any gap.
🙌 Drop the equal share and let those who can pay more
Covering a fixed cost doesn’t require the same amount from everyone.
Open-ended contributions reduce how many people pay and raise the average, and the total often still lands. Insisting that everyone pays something, however small, loads you with collection and chasing instead. That workload behaves exactly as in club dues: collections multiplied by members is the amount of admin you’ve signed up for.
Two tiers is the practical shape. Keep a genuinely free way to take part, and offer supporters exactly one amount. Every extra option you add increases the number of people who never decide.
👤 What the organiser absorbs stays invisible without a record
The most common failure is the organiser quietly paying with their own card.
At first they don’t mind. It’s a few dollars a month and it’s their project. A year in it’s a few hundred, and in the second year they start wondering whether to say something. Then, without ever saying it, they let the renewal lapse.
The reason isn’t the money. It’s that explaining a year of silent payments feels worse than just stopping. So the record exists to prevent that, not to chase anyone.
Share a project in Evere and enter the server bill once a month. When who paid and how much sit in a list, no explanation is needed. Shared tool costs among a handful of people are covered in splitting tool subscriptions between freelancers; with a community, the numbers are bigger and publishing the record is the explanation.
📉 It stops because every renewal demands a decision
An annual subscription forces a decision once a year: continue, cancel, or downgrade.
Debate it from scratch each time and eventually nobody decides. Nobody deciding means it auto-renews, and the people already paying keep paying.
Fix that by agreeing, in advance, what gets checked a month before renewal: the balance, how many people paid this year, and what next year looks like. Those three numbers tell you whether to raise the rate or cut a feature. Presented the same way every year, the discussion takes minutes.
❓ Common questions
Q. We don’t want free members feeling indebted. Don’t publish amounts per person and nobody can tell who pays. Keep payment status visible to organisers only and support stays genuinely optional.
Q. What if we end the year with a surplus? Carry it forward. If surpluses repeat, spending them on storage or backups is easier to justify later than cutting the rate and having to raise it again.
Q. What about handing the community over? Before transferring the card, hand over the list of annual costs and the renewal dates. Inheriting the payment method without knowing what it pays for is the worst position to be in.
Q. Membership spiked and our costs went up. Where a cost genuinely scales with headcount, break it out as its own line. Mixed in with the fixed costs, an increase becomes impossible to explain.