Every learned society reaches the moment where the membership spreadsheet stops scaling. The committee compares platforms, and the comparison usually starts in the wrong place: features. Features converge; operating models don’t. The questions that actually separate the options are structural.
Five questions before any demo
- Who owns the data? If exporting your member records, payment history, and consent trail is hard, everything else is rental.
- Who does the admin? Volunteer-run societies need workflows a treasurer can run in an evening, not an enterprise console.
- What happens at renewal? Look at the entire renewal journey — reminders, lapsed grace periods, receipts — because that journey is most of the platform’s real workload.
- Does it speak to the rest of your stack? Conference registration, mailing lists, and the website should share one record of truth.
- What does leaving look like? The best platforms can answer this without flinching.
Rigid SaaS or a tangle of plugins?
Most societies are offered a false choice: a closed SaaS that boxes them in, or a DIY plugin stack nobody wants to maintain. The middle path — a managed platform built on open foundations, run by people who answer email — exists, and it is usually the one volunteer-led organisations actually need.
The total cost nobody quotes
Platform pricing pages show the subscription. The real cost is the subscription plus the hours volunteers spend fighting the system, plus the integrations bolted on later, plus the eventual migration when the platform is outgrown. A cheaper licence that consumes an extra evening a week of a membership secretary’s time is not cheaper.
Run the comparison over three years, and include the exit. If a platform’s export produces a usable dataset — members, payments, consents, history — migration is a weekend. If it produces a PDF, it’s a hostage negotiation.
A short scoring exercise for the committee
- Score each candidate 1–5 on: data ownership, admin workload, renewal automation, integration with your website and mailing list, and support quality (email a real question and time the answer).
- Weight admin workload double. It is the score volunteers live with daily.
- Have the actual administrators score, not just the committee. The person who runs renewals knows things the chair doesn’t.
- Insist on a sandbox with your own data before signing anything.
And one structural suggestion: whatever you choose, keep the website and the membership system on speaking terms — single sign-on, shared records, one renewal journey. Members experience the society as one organisation; the systems should agree.
