Over the years, we have received many solicitations from organizations seeking to gain further understanding of the providers within our market space, find areas of differentiation, and score the various solutions.
Among the cornucopia of questions, there have been some insightful gems. The lions’ share, however, are rather standard that I would expect most providers would not struggle in their response. These are basic feature-function related, such as: does your system provide an ability for suppliers to enter their own information; or, can users create their own reports?
The gems? They have dug straight to the core - whether on the viability of a provider, or a foundational issue within the platform. I would like to share some of these here, with brief commentary.
The first category of questions are focused on the stability of the provider…
Financial stability:
Commentary:
The market has gone through some recent consolidation and providers that have traditionally focused on one area of expertise are, in many cases, suddenly dealing with a different environment. Some have even found themselves, mid-cycle, dropping a whole product line. As such, it is logical that if a change in company direction occurred, or is planned, that there needs to be an understanding of your exposure.
What I find even more intriguing is the venture capital question. It can be very revealing, not just in whether outside investors have control of the company and can force sale at any time, but based on the healthiness of the investment. For example, investors are often concerned when a company has raised too much money in too many rounds, as it may be a sign of delayed progress, or change in direction. Subsequent rounds often follow these rounds, as the cash infusion is needed to keep the doors open – and these "down" rounds lower the ownership percentages of existing investors, as the pre-money valuation drops. As such, it is valuable to differentiate between a, point in time, healthy balance sheet of cash, and the reasoning behind the funding.
Employee stability:
Commentary: I am confident that this is self-explanatory. What does it suggest when there are three staff reductions in a short period of time? What does it suggest when there is turnover at the executive level? What skillsets, and knowledge, was lost - and what was gained?
Customer turnover:
Commentary: In my experience, it is very rare that a customer cancels a contract, unless the company overpromised and seriously under delivered. Sure, I have seen it under other circumstances, such as financial distress by the customer, or due to an acquisition. This breach of commitment is often the fault of the provider, however – and it is the reason many no longer trust providers (and especially sales). If there is attrition, it is worth digging deeper into the cause.
Competition:
Commentary: What I find interesting about these questions is not so much learning whom they compete with, but learning how well the provider understands their own market. If they specify areas where they feel they have a competitive advantage, but it is proven to you otherwise by their competition, how viable will they be moving forward? Further, if there are proven competitive differentiators, and they weren’t thought of in advance within the RFP, maybe this question can provide further insight into which provider would be the best fit.
Dependencies
Commentary: Oddly enough, this is rarely asked in RFPs. The business model of the provider can have consequences. What if they are dependent upon a software provider that goes out of business, changes their price, or mandates some change (e.g., storage space)? What if they are dependent upon a 3rd party for implementation? Ironically, in the purchase of a SIM platform, many overlook the same resiliency principals that they seek to manage through the SIM platform they are purchasing.
The second category of questions are focused on the foundational aspects (not features and functions) of the software…
Deployment:
Commentary: There is no question that multi-Tenant SaaS environments are useful for software providers, so that they can leverage a single source of code; however, these environments are not always welcome within global organizations. In fact, this is often prohibited (e.g. - corporate governance, state laws, etc.). Electing SaaS (deployment ease and reduced operating costs) or on-premise (security, operating flexibility, and peace of mind) should not be a decision removed from your control. Further, these questions reveal an additional insight: is there a blended model, and is it possible to have further control of where systems reside?
Data model:
Commentary: Net-net, the data model controls everything. If the model is broken, how can one build upon it? If the model has limitations, will it grow with your needs? This is, too often, an area overlooked, but it should not be taken lightly and may be the cause of a failed project. We have seen these questions from those that have experienced failure in the past, but learned from them.
Processes:
Commentary: Tied very closely to the data model is the ability to capitalize on workflow / process control, as it should apply specifically to your organizational structure and needs. Can they fit your model? How are they scoped? And, since few organizations never change… How do the processes handle change?
Master Data Management
Commentary: It should go without saying, but… if a provider struggles with this area, there will be many functional limitations that will prevent effective, and efficient, management of suppliers – and the supplier master may eventually resemble your current ERP environment (multiple entries of the same supplier, multiple supplier masters, etc.).
Integration:
Commentary: There is value in a stand-alone supplier management system, but there is power in a system that is synergistic with your environment. How well does the provider understand integration? How do they handle and validate data between systems? And, how integrated is integration (irony?) within their core platform, versus being “bolted-on”?
Version Updates:
Commentary: Do upgrades always go smooth? Are they always applied without needing some reconfiguration? Can you be assured of this? The reality is that applied updates will sometimes alter how an existing, stable system works. If not, maybe the updates are merely maintenance releases, versus leaps forward. If you do not have control of timing and testing of these updates, your organization may be in for a wild, and unwelcome, ride.
Last, but certainly not least, implementation services…
Staffing
Commentary: Sometimes overlooked during the excitement of acquiring new functionality, the implementation team is core to the success of the project, as well as a significant contributor to the TCO.
The reality is that if you seek improved Supplier Information Management, the process of selecting the appropriate solution provider is not easy. The providers have gone through many, many buy cycles, where, often, the buyer is going through it for the first time. The questions to ask are not always obvious, but I hope that some of these will be of benefit – and I would encourage anyone in the process of selecting a provider to take their time, dig deep, and ensure that the choice you make will result in a long-lasting, successful partnership.