You know it’s time to select and implement new association management software (AMS). And you may have even begun to do research and ask AMS vendors about their products. But not everyone at your organization understands the challenges with your existing technology or sees the value a new solution could provide. It’s time to build the case for a new AMS!
Here are some tips for persuading your organization to consider new software:
Examine the history of your AMS.
Take some time to understand the history behind your existing system:
- Has your association taken advantage of all available upgrades? If not, why?
- Have any customizations (or fixes) been done since implementation? If so, why and by whom?
- Has your organization outgrown your current solution?
- Does your staff have to do a lot of manual processes?
Also, assess your relationship with your current vendor:
- Are you receiving the level of support you desire?
- How responsive are they to requests for bug fixes or new functionality?
- Are they providing sufficient training for users? For example, do they have a user conference, user group and online resources?
And finally, evaluate whether the system has evolved with your association’s changing needs. Where is it falling short?
Study your software’s impact on association staff.
Now that you have a sense of the system’s past, dig into the present by talking to your staff using the system.
- How does your existing technology hinder your association from achieving strategic goals?
- What regularly causes frustration when using the system?
- What do you and your colleagues wish the system could do, but doesn’t?
- What actions can’t you take because of the system’s limitations?
- What questions do you have about members, prospects and donors that can’t be answered due to the system’s limitations?
- What processes would you like to automate or streamline?
- What reports would you find useful?
- How could technology free up time so you can spend more time on more useful work?
When presenting your business case, numbers will make an impact on listeners. Ask staff to translate their experiences into data you can share. For example:
How much extra time does it take to run a process because of system limitations? How many times does this happen per week/month?
How many errors are made per week/month due to system issues? How much time does it take to fix those errors?
When presenting your business case, numbers will make an impact on listeners. Ask staff to translate their experiences into data you can share.
Assess inefficiencies and problems caused by your software.
You’re more likely to change minds if you document system issues and accompany the documentation with scenarios illustrating issues in these areas:
- Data integrity issues
- Reporting limitations
- Integration issues
- Impact on staff morale
- System adoption rate
- Data security issues
- Compliance issues
- Lost staff time translated into dollars and budget percentages
- Overtime or temporary staff costs for data entry or other tasks
- Money spent on fixes, workarounds and issues related to the system’s age and/or limitations
- Unknowns due to missing data or reporting limitations
- Projects put off because of system limitations
- Decisions not made or made with insufficient information
- Opportunities missed
- Existing technology’s impact on ability to attract staff talent
- Ability to respond to new market needs
- Competitive posture
You’re more likely to change minds if you document system issues and accompany the documentation with scenarios
Provide examples about the system’s shortcomings.
Document the product’s shortcomings in the following areas, and back up your argument with supporting data in the appendix of your business case:
Life expectancy: Point out the following aspects concerning the life expectancy of your current software:
- Technology: If your system is heavily reliant on technology that is being discontinued, bring this up.
- Members: Point out if members have threatened to leave if you don’t fix certain issues or offer particular services, and mention that there may be others who have the same issue but remained silent as they shop around for another organization to join.
- Cost: Quantify how much it’s costing to keep your current systems and software in working order. Point out that an all-in-one AMS solution will help decrease software costs and reduce using multiple vendors.
Functional requirements: Add context to your list of functional requirements, explaining why those features are needed. For example, for each feature, assign which task it will help complete. Add details about how the task is currently being completed. Estimate the time to complete the task now versus how long it would take with a new system.
The cost barrier: Even though you’ve demonstrated how a new system will make your organization more efficient and can point out ways in which you’ll be better serving your members, be prepared to hear phrases like “this isn’t in the budget” or “this isn’t the right time”. Combat this type of thinking with your research and efficiency calculations to create the most compelling case for new software.
Build a convincing business case for new software.
After you’ve gathered all the information you need, it’s time to build your business case for new software. Describe the risks and challenges for staying with the status quo, including the impact on staff productivity (and, therefore, the budget), technical inefficiencies and risks, missed opportunities, and limitations the existing software imposes on your association’s ability to deliver value to members and achieve its goals.
- When you explain the benefits of a new solution, speak to the concerns of the decision-makers, and speak in their language. The Board of Directors may want to know how this change will impact the bottom line. Others on the executive team may be more interested in how new software will help increase member engagement or improve decision-making. Focus on the impact of a new solution, not so much the functionality, unless you can tie it to a strategic goal.
- Let the decision-makers know whom you consulted to prepare your presentation. Identify the members of the selection team and describe the vendor selection process and the criteria the team will use to decide.
- Discuss the budget in the context of the expected ROI. Reference the data you’ve collected in the appendix of your business case to back up your argument. Refer to case studies of associations like yours that overcame similar challenges by investing in a new database.
- Discuss the timeline and basic implementation plan, including your change management strategy and the project’s impact on operations.
Finally, have someone with an eye for detail and the strategic big picture review your presentation. If you can’t convince this audience, support your argument with more impactful statements and data. For more tips on choosing the right association management software for your association, download the Buyers Guide for Large Associations.
A Buyer’s Guide for Large Associations