Why an increasing number of Associations are viewing Microsoft Dynamics CRM 2011 as an industry game changer.
Since the dawn of databases, companies have created AMS (Association Management Software) to serve the unique needs of the association world. Over the years, many AMS solutions have mutated into very large complex and heavy systems attempting to accommodate every association need there is. Basically, if an association has a task or business process, there is probably an AMS module for it.
Because of this trend, many AMS systems have become overly complex, challenging to use, difficult to maintain, expensive to buy, and expensive to keep. Increasingly, association executives are searching for alternatives to this traditional AMS technology path. There is a strong desire to break out of the never-ending cycle of having to get a new updated AMS system every few years and the inevitable AMS vendor demo parade that follows. Associations are looking for cleaner, easier, lighter, and more cost effective options.
It turns out that Microsoft Dynamics CRM is filling this new role. It is an excellent non-AMS choice for a growing number of associations. It is understood that Microsoft Dynamics CRM right out of the box is not for every association, but if the association focuses on their core and high priority needs, the out of the box offering is quite compelling.
You might ask, “Why would an association look at a CRM solution in the first place?” After all, CRM stands for Customer Relationship Management and CRM systems have traditionally been used for tracking prospects and sales. The answer lies in the ability to easily extend the base CRM to meet the specific needs of the association. Extending CRM is a strategy called xRM. Before I get too deep in the weeds with CRM and xRM (that definition forthcoming), let me provide some Microsoft Dynamics CRM highlights:
- Easy to use – robust where it counts.
- If you like Outlook, then it looks and feels like Outlook.
- Lots of business productivity built in.
- Microsoft to Microsoft integration for Outlook, Word, and Excel.
- Industry’s Best Outlook Integration. The Microsoft Outlook team created the Outlook integration – not an AMS vendor.
- Provides mobile connectivity.
- Easy to deploy and maintain with a hosted or on-premise options.
- Supported by a vast number of Microsoft Dynamics partners and not a sole AMS vendor.
Microsoft Outlook – If an association already uses Microsoft Outlook, then Microsoft Dynamics CRM provides the ability for all staff to access one ‘database of truth’ across the entire organization through Microsoft Outlook. You don’t have to “get into the AMS to try and find an email”. CRM is one of the best ways to collect and manage data and communications throughout the organization.
Game Changer – I believe Microsoft Dynamics CRM is a game changer in the association industry. To help illustrate, here are a handful of other examples of industry game changers.
- Accounting Systems separated from the AMS – At one point, most AMS systems included an accounting system with a general ledger, accounts payable, etc. Associations started demanding integration to their existing best of breed accounting packages like Great Plains (now called Microsoft Dynamics GP). As a result, most AMS vendors removed their own accounting systems from the AMS. That was a game changer for accounting systems as well as accounting departments that didn’t want all the staff having access to vital accounting data.
- Microsoft .NET. Back in the 2002-2003 timeframe, associations were introduced to the concept of .NET with its promise of better system interoperability. Databases and applications could now easily talk to other systems with this new technology. Who remembers the AMS vendor panel discussion on .NET at ASAE hosted by DelCor and designData? Talk about a game changer. Seemingly overnight, associations started to include the requirement that their AMS solution be 100% .NET. The AMS vendors that had solutions that were not 100% .NET certainly struggled.
- Google. The increasing size and complexity of the AMS reminds me of how the basic home page of a website has evolved. At first, the home page was basically a fancy business card. Over time though, each department wanted to stake claim to their piece of the home page real estate and before you knew it, the website home page looked very cluttered. It was difficult to find anything. Then along came Google. All it had was a search box and submit button with a whole lot of white space going on. It clearly and succinctly cut to the purpose of that website and made it easy to use. Google was a game changer. It inspired cleaner and more efficient design. It required people to think differently about the true purpose of their design. I think that is what we have here with CRM. CRM can finally inspire cleaner and more efficient use of the membership data.
- xRM. The “x” in xRM stands for “Anything” – Anything Relationship Management or eXtended Relationship Management. xRM is not a product, it is a strategy that takes CRM one step further, focusing on managing all connections – not just those with ‘customers’. Specifically with Dynamics CRM, Microsoft has provided a rich foundation of powerful functionality. An association can then easily add to their system. If you need to track meeting attendance or committee management (as an example), Microsoft provides the ability to create that functionality. As you can see, this is not your father’s CRM. You don’t have to be a developer to add functionality to CRM. You use CRM to extend CRM. The tools Microsoft provides have been made so straight forward and easy to use, creating new “modules” (called ‘Solutions’ in CRM) is analogous to creating a custom report.
Microsoft Dynamics CRM with the xRM strategy is the game changer. Now an association can have a clean and easy to use membership system that is robust where it counts.
Association executives can now take a look at a standard Microsoft product to see if there is a fit at their association. Who knows – your next AMS might not be an AMS after all.
Author’s note on this particular post – I first wrote this post in September of 2010. I posted it on the Microsoft Dynamics for NFP’s community blog. Since that time, this post has been published with different titles and author names by the various companies I have worked for (some with and some without permission).