Choosing a membership platform is something most people do once. These are the questions worth asking every supplier — including us — and what a good answer sounds like.
The fastest way to judge a membership platform is to put your most awkward rule in front of it. Bring that one.
Where does the membership data physically sit, and whose agreement covers it? The answers vary more than people expect: the supplier's cloud account, a shared database with a tenant column, or your own infrastructure. All three are legitimate; they are not the same thing.
Who holds the underlying licences? If the platform is built on Microsoft, Salesforce or similar, ask whether you hold that relationship directly or whether it is resold to you. It changes what happens if the supplier relationship changes.
A good answer names the location, the agreement and the licence holder without hedging, and does not need to check.
This is the question that separates suppliers fastest. Ask for a screen — not a slide, not a diagram, not an animation of a dashboard nobody uses.
Ask specifically for: a member record with grade history; a subscription showing a mid-year change and the resulting pro-rata; a renewal run with failed collections in it; and the member portal on a phone.
A poor answer is a demo environment with three perfect members in it. Ask to see something that went wrong.
Every organisation has one. Joint membership where one party is invoiced. A concession that requires annual re-certification. A CPD cycle that does not align to the membership year. Grade progression that requires a panel. Employer-paid cohorts where the payer is not the member.
Do not describe it in advance — bring it to the session. What you are testing is not whether the platform can do it, but whether the supplier recognises it immediately or has to think about what you mean.
Every platform has all three, and the boundary is where budgets move. Ask for the boundary in writing, per requirement, before contract — not "yes we can do that", which is true of any software given enough days.
The requirements most often quoted as standard and delivered as builds: member-facing upgrade and regrade journeys, anything involving a panel or assessor, complex pricing structures, and integrations with systems the supplier has not met before.
A good answer volunteers where the boundary falls before you ask.
Most difficult implementations are difficult because of data, and most timelines move for the same reason.
Ask: how many source systems, who does the cleansing, how many trial loads before go-live, what reconciliation is run and who signs it off, and what happens to twenty years of history where the rules changed three times.
A good answer includes a trial load reconciled before anyone commits to a go-live date.
Their membership sector expertise has ensured they challenge us where appropriate, and we have re-engineered both our membership and case management processes as a result.
Implementations fail on client-side capacity at least as often as on supplier capability, and almost no supplier says so at bid stage.
Ask: how many days of your team's time, from whom, in which weeks. Who needs to be available for decisions. When UAT falls in your calendar, and whether that collides with your renewal run — because it usually does.
This is where a five-year relationship is decided and where most evaluations spend the least time.
Ask: how improvements reach you — as product releases you receive, or as chargeable projects. Whether other clients' improvements reach you. What ongoing support actually buys. What happens when you want something changed in year three.
A good answer is specific about the mechanism. "Continuous improvement" without a mechanism is a word.
Every supplier in this market now has an AI story. Very few have an answer to the second question.
Ask: where the organisational knowledge is held, and whether it stays yours if you change AI provider. Whether the answer shows its sources. Whether it tells you what it could not find — because the failure mode that damages an organisation is not an answer that says it does not have something, it is a confident report quietly missing a third of the records.
A poor answer is "it respects permissions" and nothing further.
Ask for a reference at your scale and in your structure — a 4,000-member learned society and a 60,000-member chartered institute have almost nothing in common operationally.
Ask the reference, not the supplier: what went wrong, and how was it handled. What did you underestimate. Who from the supplier is still involved. Would you choose them again — and if the answer is yes, ask what would have to change for that to become no.
Published outcome figures are worth having, and worth reading properly. A retention improvement can come from a genuinely better renewal process, or from a rate change, or from a lapse policy change, or from counting differently.
Ask what the baseline was, over what period, and what else changed at the same time. A supplier who can answer that is showing you something real. So is one who says they do not know.
Ready to test it?
Bring your most awkward membership rule to the first demo. Ours or anyone else's — it is the fastest question in this guide to get answered.
Reflections from MemberWise Digital Excellence 2026 on why membership organisations are moving beyond basic portal self-service and focusing instead on more connected, personalised, and engaging digital member experiences.
Wattle are delighted to be attending the latest MemberWise Membership Solutions Day on Thursday 11th June 2026 in London - the data-driven decisions edition.
A demo environment with three perfect members tells you nothing. Ask to see a renewal run with failed collections in it. What happens next is where most platforms quietly struggle.
