Buying membership software
Seven questions for associations, professional bodies and charities before a new membership system becomes the one you have to live with.
A feature grid hides the decisions that cost money later: who owns the member record, who owns the journey, and whether you can explain an automated decision.
The member should have one record: grade, payment, event, message, document and agent action. eMembership is built to replace a legacy CRM and become that system. An API to Dynamics or Salesforce is a bridge while an organisation must keep the old CRM. See the Dynamics and Salesforce alternative and the comparison.
Join, renew, pay, book, learn, vote, donate and raise a case should stay with an agent until it has no further authorised action. A person then receives the case with the file. That is the model on agentic AI and enterprise.
Each organisation has a separate secure database instance. Data is encrypted with AES-256 at rest and TLS 1.3 in transit, inside UK-hosted infrastructure. Ask any vendor to show the boundary between your members and the next customer's.
Staff actions, member self-service, API calls and agent activity should land in one log. If the answer is a set of exports from three products, the audit will fail the first time a board asks a straight question. Detail is on security and compliance.
eMembership includes daily backups, 30-day retention, geo-redundant storage, point-in-time recovery and scheduled restoration tests, under ISO 27001 and ISO 9001. Ask to see the restore test, not only the backup job.
Each agent decision stores the context it used, the policy it applied, the action it took, the outcome, and whether the case was handed to a person. That trace sits in the same audit log as staff and member activity. The control model is on AI governance.
eMembership prices automations per member per month, not seats. The published range is 60 to 600. Typical organisations measure around 120, the calculator default. At 5,000 members and 120 automations the guide figure is about £2,121 a month. Endpoints are about £1,500 a month at 5,000 members and 60 automations, and about £12,000 a month at 100,000 members and 600 automations. Below 5,000 or above 100,000 members, ask for a quote. Billing is monthly in arrears. Use the pricing calculator.
The same platform, described for the buyer who is searching.
The member. Grades, payments, events, messages, documents and agent actions should hang off one record. eMembership is built to replace a legacy CRM and become that system. An API to Dynamics or Salesforce is a bridge while an organisation must keep the old CRM.
Price follows automations per member per month, not seats. The published range is 60 to 600. Typical organisations measure around 120, the calculator default. At 5,000 members and 120 automations the guide figure is about £2,121 a month. Endpoints are about £1,500 a month at 5,000 members and 60 automations, and about £12,000 a month at 100,000 members and 600 automations. Below 5,000 or above 100,000 members, ask for a quote. Billing is monthly in arrears.
Each agent decision stores the context it used, the policy it applied, the action it took, the outcome, and whether the case was handed to a person. That trace sits in the same audit log as staff and member activity.
Each organisation has a separate secure database instance. Data is encrypted with AES-256 at rest and TLS 1.3 in transit, inside UK-hosted infrastructure. Daily backups are kept for 30 days, with geo-redundant storage, point-in-time recovery and scheduled restoration tests.
We will walk the seven questions against your member numbers, your current CRM, and the automations you actually run.
Request a demo