Think You Need a New AMS? Start With the Work.

You may know your association needs a different way to work long before the rest of the organization does.

You see the reports that require three exports and a spreadsheet. You know which routine changes need a support ticket. You hear from members who cannot complete a task that should have been simple. You know which process depends on the one person who remembers every exception.

Other people may see a system that still processes renewals, accepts registrations, and stores member records. From their perspective, it may not be obvious why the association should invest time, attention, and money in changing anything.

That difference in perspective is what makes the internal conversation difficult. The person closest to the work feels the friction every day. Leaders and colleagues often see only the final result after capable staff have kept everything moving.

The strongest case for change does not begin with a complaint about the current AMS or a list of features in a new one. It begins by making the work visible, connecting it to shared outcomes, and keeping the possible answer open.

The people closest to the work usually notice first

Systems rarely stop working all at once. More often, the association changes around them. Membership options expand. Reporting expectations grow. New programs, pricing models and integrations are added. Staff find ways to make the platform support work it was not originally configured to handle.

Those adjustments can be reasonable. The problem is that they gradually become the normal way of working. A spreadsheet fills one gap. A manual check catches another. A staff expert remembers which button not to use or which report cannot be trusted without cleanup.

Because the work still gets done, the organization may not see the effort surrounding it. That is not a failure by leadership, staff, or the vendor. Different people simply see different parts of the operation.

The goal is not to prove that the current system failed. It is to create a shared view of what the association needs next.

Start with evidence, not frustration

Saying, "Our AMS is terrible," may feel accurate in the moment, but it is difficult for someone else to evaluate. It can also turn a useful discussion into a debate about whether the system is good or bad.

Specific examples create a better starting point. For two to four weeks, document the moments when a routine task requires extra work. Capture what should have happened, what actually happened, how often it occurs, and who or what is affected.

Listen for the phrases that signal an established workaround:

• We always have to export it first.
• Only one person knows how to do that.
• Do not use that report without checking it.
• We keep a separate spreadsheet for that.
• The system cannot do it unless we customize it.

One example may be an inconvenience. A recurring pattern that crosses teams, affects members, delays decisions, or consumes staff time deserves closer attention.

Look for a pattern, not a perfect score

An internal review should not become a scorecard for the technology or the people using it. The purpose is to understand where the same kinds of issues keep appearing.

A useful readiness check looks across three areas:

• Staff effort. Are staff entering the same information more than once, relying on one expert, or avoiding the system because another method feels easier?
• Data and decisions. Do reports require cleanup, do systems provide different answers, or does leadership wait for information it should be able to access?
• Members and growth. Do members need help with basic online tasks, or do new programs, products, and pricing models require workarounds?

A few focused issues may call for training, configuration or a process change. Repeated issues across departments may justify broader discovery. The pattern matters more than the number of boxes someone can check.

Estimate the impact without pretending to know everything

You do not need a perfect return-on-investment calculation before beginning the conversation. You do need a conservative estimate that makes the scale of the work understandable.

For recurring staff work, a simple starting point is hours each month multiplied by the estimated hourly staff cost, multiplied by 12. If four people each spend three hours a month reconciling data at a blended cost of $45 an hour, that is about $6,480 a year. The estimate will not capture every consequence, but it makes an otherwise invisible task easier to discuss.

Time is only one part of the impact. Also consider:

• Errors, duplicate records, refunds, and manual corrections
• Delayed renewals, registrations, invoices, or other revenue activity
• Member frustration and the staff follow-up it creates
• Continuity risk when essential knowledge lives with one person
• Outside consulting, custom development and support costs
• Programs, pricing ideas or services the association cannot easily launch

The point is not to inflate a number until it supports a predetermined answer. It is to size the opportunity honestly enough that the organization can decide whether further discovery is worthwhile.

Ready to make the case more clearly?

Download The New AMS Internal Buy-In Kit for practical worksheets that help you document recurring friction, estimate its impact, and prepare for a productive internal conversation.

Download the free guide →

Connect day-to-day friction to shared outcomes

Leadership may not need to understand every workaround. It does need to understand what the recurring work prevents the association from doing well.

Translate the examples into outcomes that matter beyond one department. Instead of asking for a particular report builder, describe the need for reliable information that staff, executives, and the board can use. Instead of asking for a specific portal feature, describe the need for members to complete common tasks clearly and confidently.

A useful outcome:

• Describes a result rather than a product feature
• Matters to more than one person or department
• Can be observed or measured later

For example: Our current renewal process requires membership and finance staff to reconcile three exports every month. That delays reporting and creates avoidable errors. We want a reliable view of member and payment status so staff can spend less time checking data and leadership can make decisions with confidence.

That statement gives colleagues something concrete to respond to. It explains the current work, the organizational consequence, and the outcome the association needs without assuming which product or project must provide it.

Your first ask should be a conversation, not approval

The first meeting does not need to end with permission to replace the AMS. A better goal is to create a shared view of the current situation and agree on what the organization should explore.

Invite a small group that sees the work from different angles: front-line staff, workflow owners, finance, technology or operations, and an executive sponsor who can connect the discussion to strategy and investment.

A focused 30-minute conversation can:

• Review two or three examples that show a recurring pattern
• Discuss the people, time, cost, and member impact involved
• Ask each team what it sees from its part of the organization
• Agree on the outcomes that matter most
• Choose the next step and name an owner

A constructive opening can be simple: Our current system has supported the association, but our needs and processes have evolved. I have documented several recurring points where staff are doing extra work or members are experiencing friction. I would like us to review the examples, agree on what improvement would look like and determine what we should explore next.

Keep the possible answer open

A fair internal process does not begin by deciding that a new AMS is the only acceptable answer. The right next step may be process improvement, staff training, configuration, a targeted integration, or a different platform.

That openness makes the conversation more credible. It also helps the association separate fixable issues from structural limits. If the current platform can reasonably deliver the agreed outcomes, the organization can pursue those improvements with clearer priorities. If it cannot, the same evidence becomes the beginning of a stronger evaluation and requirements process.

Either way, the association is making a decision based on the work, the impact, and the outcomes it needs, not on whoever is most frustrated or whichever demo has the most appealing feature list.

Create a short path to clarity

This process does not need to take months. Over 30 days, an association can check for recurring patterns, document friction, estimate impact, connect the work to shared outcomes, begin the internal conversation, and decide what deserves further exploration.

That is why we created The New AMS Internal Buy-In Kit. It provides readiness questions, worksheets, conversation prompts, and a practical 30-day path to help your team decide what comes next.

Download The New AMS Internal Buy-In Kit →

That is where association management, made lighter, can begin.

Frequently asked questions

How do you know when it is time to discuss a new AMS?

It may be time to begin the conversation when staff repeatedly work outside the system, reports require manual reconciliation, members need help with routine tasks or new programs require one-off solutions. These signs do not automatically mean the AMS must be replaced, but they do justify a structured review.

How do you build internal support for replacing an AMS?

Start with recurring work rather than a feature list. Document specific examples, estimate their effect on staff and members, and connect them to outcomes the organization already values. Invite the departments affected by the work to review the evidence and agree on what improvement should look like.

Who should be involved in the first AMS conversation?

Include a small cross-functional group: front-line staff, the owners of important workflows, finance, technology or operations, and an executive sponsor. The goal is to understand the pattern from several perspectives while keeping the group small enough to choose a clear next step.

Do you need a complete business case before talking to leadership?

No. A few recurring examples, a conservative estimate and agreement on the outcomes that matter are enough to begin. The first request can be a short discovery period, not approval for a purchase or implementation. A formal business case can follow if the evidence supports a larger change.

What if the current AMS can be improved?

That may be the right answer. A useful review should consider process, training, configuration, and integration improvements alongside replacement. If the current system can reasonably support the agreed outcomes, the association can use the same evidence to prioritize improvements and measure whether they worked.