Choosing the Right Product Partner
Here are some of the key factors you might want to consider as you evaluate platforms during Your AMS Journey:
Your Size and Growth
We often come across associations that have purchased a 16 wheeler, when what they really needed was just a SUV. If you are a small association that has a concise set of features and processes you need to operate well, then going for an extremely flexible and innovative platform might be overkill.
However, are you looking to grow substantially in the future, and do you envision your members doing the same? If so, you need a cloud based, highly flexible product on an innovative platform.
Place of Birth
What we mean here is, was the product “born in the cloud”? It’s obvious we want a product that lives in the cloud, but was it architected for the cloud from its inception. This becomes a crucial factor as you grow.
We tend to come across legacy products that were built before the cloud, but have added a web use interface and claim that they are a cloud platform. Unfortunately, that is not true, as the core architecture was never designed with the needs of the cloud in place.
Platform Compatibility
AMS platforms are great in the sense that your tool is built on top of a stable, innovative, foundational layer. The platform will continue to evolve, and the AMS automatically benefits from the underlying technological innovation. As an example, if the platform began to support artificial intelligence and blockchain, the AMS would be able take advantage of it. Non-platform products would have to integrate or build support for these independently. At some point, your organization will find non-platform products too difficult to keep up with evolving needs.
Features & Technology
We frequently see associations making decisions purely on features, while not fully understanding the ramifications of the technologies the product is built on. Most legacy systems that have been around a long time have solid features, but are poor at integrating, not born in the cloud, and are hard to customize. Furthermore, some of them are not built on a stable platform.
In-house Technical Competence & Budget
Lastly, it is key to make your product decision based on the technical competence you have on staff and the potential budget you are willing to allocate to IT.
We come across organizations that purchase larger complicated systems, when they clearly did not need it. This in turn leads to poor implementation and adoption, and adds problems instead of solving them. A simpler, fully partner managed, easy to use system will be more beneficial in the long term.