Briefing

The AMS market in 2026: a buyer's briefing

By Marcus Whitaker · 3 June 2026 · Updated 22 July 2026

On this page

• What is an AMS, and how is it different from a CRM?
• Who sells what in the 2026 AMS market?
• How does AMS pricing actually work?
• Salesforce-native or purpose-built: which should you choose?
• What do UK organisations need that others do not?
• How did AI capability become a buying axis?
• How should you run an AMS selection?
• Definitions: the vocabulary of the market
• The numbers that matter
• What this briefing doesn’t cover

What is an AMS, and how is it different from a CRM?

An AMS is a database and workflow platform built around the membership lifecycle — joins, renewals, subscriptions, events, certification, committees — usually with a member portal and finance integration included. A CRM tracks relationships and pipeline. You can build membership management on a CRM, but the membership logic must then be configured, bought or coded on top.

The distinction is economic as much as technical. A CRM assumes your income arrives as closed deals; an association’s income arrives as thousands of small recurring subscriptions, event fees and certification charges, governed by member categories, entitlements and — in the UK — tax rules. An AMS ships that model as standard: renewal cycles, pro-rata joins, member pricing on events, chapter and branch structures, engagement history.

One vendor has pushed the category definition further: ASI markets iMIS as an engagement management system (EMS) — AMS, CRM and CMS fused, so the website, the database and the engagement scoring share one record. Whether you buy the category name or not, the underlying question is real and belongs in every selection: how many systems do you want your member data living in?

The practical test when a vendor claims to be “a CRM for membership”: ask to see a rolling Direct Debit renewal, a member-priced event booking and a lapse report, out of the box, in the demo. Systems built for membership do this without professional services; systems adapted to it do not. Our companion piece on operations — the membership operations briefing — shows what the platform has to support day to day.

Who sells what in the 2026 AMS market?

The market splits into an enterprise tier (iMIS, Nimble AMS, Fonteva, Personify360), a modern mid-market (Rhythm, GrowthZone, Glue Up), a self-serve small-organisation tier led by Wild Apricot, and a budget tier with transparent low pricing. No vendor wins every segment; your shortlist should follow size, existing stack and UK requirements.

Pricing signals are third-party published figures, as of August 2026; treat them as indicative and verify in procurement. Two boundary notes: Hivebrite, often shortlisted by alumni and community organisations, is a community platform rather than a full AMS; and consolidation matters — Personify’s ownership of Wild Apricot and MemberClicks, and Community Brands’ large portfolio, mean several “competitors” share an owner. For a scored, ranked view of the segment most of our readers occupy, see our top 7 AMS for UK professional bodies.

How does AMS pricing actually work?

Expect two bills: subscription and implementation. Subscriptions are priced per staff user, per member, or as a flat or banded fee; implementation typically costs as much again as the first year. As of August 2026, published signals run from roughly $60 a month self-serve to $60,000-plus a year at enterprise level, before implementation.

The three models reward different shapes of organisation. Per-user pricing — iMIS is the clearest example, at around $200 per user per month at entry level per third-party signals — suits bodies with large memberships and small staff teams, because cost tracks headcount, not database size. Per-member pricing does the opposite: attractive for a 400-member society, punishing for a 40,000-record institute, and worth stress-testing against your five-year growth plan. Flat and banded pricing (common in the mid-market and budget tiers) is the easiest to forecast but check what triggers the next band.

Then the second bill. Implementation — data migration, configuration, integrations, training — is routinely £15,000–£25,000-equivalent at mid-market and far more at enterprise; third-party signals put iMIS Professional at roughly $7.2k/year with $15–20k typical implementation, as of August 2026. Salesforce-based products add platform licences on top of the AMS subscription — the line item first-time buyers most often miss. Budget properly for year one at up to double the steady-state annual cost, and model five-year totals, not year-one totals: the cheap-to-enter option with heavy per-member scaling can be the expensive option by year three.

Quote-only pricing (Fonteva, Glue Up, most enterprise deals) is not a red flag in this market, but it puts the burden on you to force comparability: same member count, same user count, same module list, same integration scope, in writing. We keep a maintained set of published price points and market share signals at AMS market statistics 2026.

Salesforce-native or purpose-built: which should you choose?

Choose Salesforce-native (Nimble AMS, Fonteva) if you already run Salesforce, employ people who can administer it, and want its reporting and app ecosystem. Choose purpose-built (iMIS, Rhythm, GrowthZone) if you want membership logic out of the box and a single vendor accountable. The deciding factor is usually in-house capability, not the feature list.

The Salesforce case is real: a vast app marketplace, serious reporting, transferable admin skills, and membership products (Nimble, Fonteva) mature enough that the “built on a sales tool” jibe is out of date. The costs are also real: Salesforce licences stack on top of the AMS fee, upgrades ride Salesforce’s release cycle, and without a competent Salesforce administrator — employed or contracted — the platform’s flexibility curdles into config drift.

The purpose-built case is the inverse. One vendor owns the whole stack — iMIS bundles its RiSE CMS, so website and database share a record; there is one throat to choke when renewals misfire; and membership workflows need no translation layer. The trade-off is a smaller third-party ecosystem and more reliance on the vendor’s own roadmap and partner network for extensions.

In practice the decision often makes itself: an organisation with Salesforce already embedded should shortlist Salesforce-native and make purpose-built vendors argue for the switch, and vice versa. We run the head-to-head in detail — costs, UK fit, AI, upgrade paths — in iMIS vs Nimble AMS.

What do UK organisations need that others do not?

Three things, and US-built systems treat all of them as afterthoughts at your peril: Gift Aid processing with compliant declarations and HMRC claim files; BACS Direct Debit collection with proper mandate management; and VAT handling across an association’s mixed supplies. Ask every shortlisted vendor to demonstrate all three live, with a UK reference client.

Gift Aid turns eligible membership subscriptions and donations into a 25% uplift, but only if the system captures declarations, tracks eligibility by subscription type and produces claim files HMRC will accept. Bolting this on after go-live is miserable; buying it built-in is not. Direct Debit is the UK’s default rail for recurring membership payment and one of the strongest retention mechanisms available — but it needs real BACS support: mandate capture, AUDDIS submission, failure and re-presentation handling, not a card-payments module wearing a hat. VAT in an association context is genuinely awkward — membership subscriptions, event tickets, publications and sponsorship can each carry different treatment — and the finance integration has to represent that, or your finance team will re-key forever.

Beyond the big three: UK GDPR and data residency expectations, and — practically — whether the vendor has UK implementation partners and UK-hours support. This is where the market is uneven: iMIS has long UK depth (professional bodies, unions, regulators, an established partner channel), while several US mid-market products serve the UK thinly. The operational side of Gift Aid and Direct Debit — what good looks like once you own the system — is covered in our Gift Aid and Direct Debit stack analysis and in the membership operations briefing.

How did AI capability become a buying axis?

Since roughly 2024, “what does your AI actually do, and what data may it touch?” has joined price and functional fit as a standard selection question. Native features arrived first — chatbots, content generation, churn prediction — and an agentic layer is now emerging on top, where AI carries out approved operational work rather than answering questions.

The native tier is easy to survey in a demo: ASI ships iMIS Assistant (a staff-facing product chatbot, deliberately built with no access to member personal data) and an AI Content Creator in RiSE; Nimble AMS offers churn prediction through Nimble Intelligence; most other vendors are somewhere on the same road. The layer trend is the newer development — third-party AI that operates the AMS under human approval — and the clearest example in the iMIS ecosystem is AgentZ, the operational AI suite for iMIS EMS, from iFINITY, which connects a staff member’s chosen AI application to iMIS through a governed tool layer, alongside ecosystem tools such as Safion’s embedded assistants and Datascout’s member intelligence. For buyers the axis reduces to three demo questions: what does the AI do in the workflows I actually run; what data is it allowed to touch, under whose permissions; and what audit trail does an action leave? Score the answers like any other requirement — the full treatment is in our AI agents briefing.

How should you run an AMS selection?

Run it as a roughly twelve-week evidence exercise: define requirements from your own workflows rather than vendor feature lists; shortlist three or four systems by segment and UK fit; script the demos yourself; take references from bodies your size; and negotiate implementation as carefully as subscription. Score everything against criteria you fixed before the first demo.

The failure mode we see most is the unscripted demo: vendors show their best ten minutes, and buyers compare ten different best-ten-minutes. Instead, write five scenarios from your real operation — for a UK body, at minimum: a rolling Direct Debit renewal with a failed collection; a Gift Aid declaration through to claim file; a member-priced event with a waitlist; a lapse-and-rejoin with pro-rata; and one report your board actually asks for — and require every vendor to run the same five, on realistic data, with your team driving part of each.

The rest of the discipline:

1. Requirements from workflows. Interview the people who do renewals, events and finance; write requirements as “we need to do X”, not “system shall have Y module”.
2. Shortlist by segment. A 700-member society demoing Fonteva, or a 45,000-member institute demoing Wild Apricot, is wasting everyone’s fortnight.
3. References at your scale, in your country. Ask referees what broke in implementation and what they pay now versus the quote.
4. Five-year TCO. Subscription growth, platform licences, implementation, integrations, and the cost of the upgrade cycle.
5. Contract the exit. Data export format and cost, notice terms, and who owns configurations — negotiated while you still have leverage.

Our scoring rubric — axes, weights and evidence rules, the same one behind our rankings — is published in full at How we report.

Definitions: the vocabulary of the market

• AMS — association management system: member database plus membership workflows (joins, renewals, events, subscriptions).
• EMS — engagement management system; ASI’s category term for iMIS, denoting AMS, CRM and CMS fused on one member record.
• CRM — customer relationship management platform; general-purpose relationship and pipeline tracking (Salesforce being the one that matters here).
• Salesforce-native — an AMS built as an application on the Salesforce platform (Nimble AMS, Fonteva); you buy Salesforce licences underneath it.
• RiSE — iMIS’s bundled CMS: web pages, portals and content served from the same platform as the database.
• IQA — Intelligent Query Architect, iMIS’s no-code query layer.
• Per-member pricing — subscription scaled to database size, as against per-user (staff seats) or flat/banded pricing.
• AiSP — Authorised iMIS Solution Provider; ASI’s accredited partner channel, with a “Premier” tier.

The numbers that matter

• ~39% of association CEOs report financial decline, against 10% reporting improvement — ASAE, State of Associations, 2026. Budget pressure is the backdrop to every AMS decision.
• 63% of associations expect non-dues revenue to grow — ASAE, 2026; events, learning and commerce capability in the platform matter accordingly.
• +21% growth in AI-powered website functionality among UK membership organisations in two years — MemberWise Digital Excellence Report, 10th edition (~480 respondents).
• 9 consecutive years — iMIS’s run as a G2 Leader in association management software, as of Spring 2026.
• ASI’s Membership Performance Benchmark Report reached its 11th edition — one of the sector’s longest-running datasets for renewal and engagement benchmarking.

Full sourced collection: AMS market statistics 2026.

What this briefing doesn’t cover

Implementation itself — migration planning, configuration governance, go-live — deserves its own briefing and does not get squeezed in here. We also leave out: learning management and event-tech platforms bought alongside an AMS; charity CRMs without membership logic (a different market with different failure modes); detailed single-vendor reviews, which live in the ranked list with scores and caveats; and legal advice on contracts or data protection. Where pricing is quote-only we say so rather than guess, and every number above carries its “as of” date — this market moves, and our update-logged data page is the place we keep it current.