Custom vs. Configurable AMS: What It Means for AI

For 30 years I watched good association teams get stuck with systems that were custom-built for them once and then frozen in place.

Every new dues category meant a change request, a consultant and a bill. Every upgrade risked breaking a report someone had built years earlier. And now those same associations are walking into board meetings where the first question is, "What's our AI plan?"

Here's what I tell them: your AI plan starts with a decision you may have made years ago, when you chose between a custom AMS and a configurable one. That decision shapes how much your system costs to change, whether you can take upgrades, and whether AI can make sense of your member data at all.

The short answer

A custom AMS is association management software whose code has been changed for one association. A configurable AMS lets association staff set up membership types, dues, rules and fields in the product's settings, with no code changes. Configuration is cheaper to change, stays current through upgrades and keeps member data in a consistent structure. That consistency is what AI tools need: they work from structured, predictable data, not one-off fields and workarounds.

What "custom" really means

Custom sounds like a compliment. It means the system was built around you. In practice, it means a developer changed the software's code for your association, and now that code belongs to you to maintain.

That has three consequences that show up later, usually at the worst time:

• Every change costs money. A new membership type or a different grace period becomes a project with a quote, a timeline and someone else's schedule.
• Upgrades get risky. Custom code has to be retested or rebuilt whenever the core product changes, so many customized associations stop taking upgrades. That's how you end up on a version from years ago.
• Your data drifts. Each custom build adds fields, tables and workarounds that only make sense to the people who built them. When those people leave, the logic leaves with them.

What "configurable" means

A configurable AMS gives your staff the controls. Membership types, dues rules, grace periods, eligibility, events, certifications and the member portal are all set up in the product, in settings your team can see and change. When your membership model changes, you change the settings, not the software. (If you run tiered, corporate or chapter-based memberships, here's what to look for in a flexible membership model.)

Because every association runs on the same product, everyone gets every improvement. Nobody is stuck on an old version because their custom code can't survive the upgrade.

Custom vs. configurable AMS at a glance

Why this decides what AI can do with your member data

There's a lot of talk right now about the "AI AMS." Here's the part that gets skipped: AI is only as useful as the data it reads. An AI tool can summarize a member's history, spot who might not renew or help build a segment, but only if member data lives in a consistent, predictable structure.

Custom systems make that hard. One association tracks membership status in a custom field, another in a notes box, a third in a spreadsheet someone updates on Fridays. A person can untangle that. An AI tool will either guess or give up.

So my contrarian advice is this: you don't need an AI tool first. You need member data AI can read. Configuration gets you there, because every membership, payment and registration is recorded the same way, every time.

What that looks like with HubSpot

Cannolai is built to pair with HubSpot, and this is where the data structure pays off. Contact and company properties sync both ways between Cannolai and HubSpot, so member data lives on HubSpot records like any other HubSpot data. That means HubSpot's AI, Breeze, can summarize a member's record and answer questions from accurate membership data, once CRM data is turned on in your HubSpot AI settings.

Other membership data, such as event registrations or group participation, reaches HubSpot when you add it to a static or active list in Cannolai, and those lists sync into HubSpot. Your team also sees each member's Cannolai data right on the HubSpot contact and company record, and can work in Cannolai without leaving HubSpot. (More on how to use HubSpot alongside an AMS.)

How Cannolai handles what you need next

"Configurable" doesn't mean you'll never need something new. You will. The question is what happens when you do.

At Cannolai, we don't build one-off custom versions. When an association needs something the product doesn't do yet, we build it into the platform, and it becomes available to every association that uses Cannolai. We release updates every month and publish release notes, so you can see what has changed.

How to tell the difference in a demo

Ask these four questions in any AMS demo:

1. "Show me a staff member adding a membership type and changing a dues rule, without a developer."
2. "When you build something new for a client, does every client get it, or only them?"
3. "How many of your clients are on the current version?"
4. "Show me how a member's status, payments and events are structured, and where an AI tool would read them."

If the answers involve quotes, scoping calls or "it depends on your version," you're looking at custom.

Try it before you decide

We're a newer AMS. The people behind it aren't: our team has spent decades inside associations and running AMS implementations. If you want to see configuration for yourself, ask about the Taste Test, a working sandbox with a playbook that your team can use for a couple of weeks before you sign anything.

Or book a 15-minute fit check and bring your messiest membership scenario. In 15 minutes, you'll know whether Cannolai fits the way your association actually runs. And if it doesn't, we'll tell you.

FAQs

Is AMS customization ever worth it?

Rarely, and the cost shows up later. Custom code can solve a one-time problem, but you pay to maintain it, it can break at upgrade time, and it often keeps you on an older version. Before customizing, ask whether the need can be met with configuration or added to the product for everyone.

Can a configurable AMS handle complex membership models?

Yes. A well-built configurable AMS handles individual, corporate, tiered, chapter-based and hybrid memberships through settings, including multiple contacts on a corporate membership and different grace periods by membership type. Ask the vendor to set up your most complex model live in the demo.

What does AI-ready member data mean?

AI-ready member data is stored in a consistent structure that AI tools can read the same way every time: membership status, payments, events and engagement recorded in defined fields, not scattered across custom fields, notes and spreadsheets. It's less about having an AI tool and more about having data an AI tool can trust.

Can HubSpot's AI use Cannolai member data?

Yes, for the data that syncs into HubSpot. Contact and company properties sync both ways between Cannolai and HubSpot, and other membership data syncs through static or active lists in Cannolai. Once that data is on HubSpot records and CRM data is turned on in your HubSpot AI settings, Breeze can summarize records and answer questions from it.

Do we need HubSpot to use Cannolai?

No. Cannolai runs on its own as a complete AMS. It is built to pair with HubSpot for associations that want to use their member data in HubSpot's marketing and AI tools.