Choose a platform
The true cost of community software: a buyer’s checklist
Find the fees, add-ons, operating work, and switching costs that rarely fit in a pricing card.
The short version
- Monthly price is only one line in the cost of running a community.
- Transaction fees matter differently at different revenue levels.
- Administrative time and switching difficulty belong in the comparison.
List the fixed costs
- The base subscription and the billing period required to get the advertised price.
- Higher tiers needed for courses, custom domains, automations, analytics, or more members.
- Separate tools for email, events, video hosting, files, forms, or certificates.
- Setup, migration, implementation, or required service fees.
Model the variable costs
A percentage fee can look harmless before revenue grows. Calculate it at three believable monthly revenue levels and keep platform fees separate from payment-processing fees.
Also check whether member, admin, storage, email, automation, or video limits create a step change in price.
Count operating work
Estimate hours per month, then assign even a modest value to that time. Complexity is a recurring invoice even when no vendor sends it.
- How many places must an admin update an event, member, lesson, or announcement?
- Which reports or exports require manual cleanup?
- How much member support will onboarding and login create?
- Who owns integrations when another tool changes?
Ask what leaving would cost
Before you join, learn what you can export: profiles, posts, comments, course progress, files, payments, subscriptions, and custom-domain settings. Ask which parts come out in a reusable format.
Build the smallest useful version of your community.
Start with a feed, classroom, calendar, messages, and member list. No card required.
Start a community