In Part V we outlined the most critical question that needed to be addressed after you decided that you needed a BoB or FuSS solution and what the critical features of that solution was, namely, what was required for globalization.
Now that we have outlined the high-level functional requirements from a multi-faceted view, we’re ready to go to market with a supplier RFI, and, in particular, an RFI that answers the following (set of) question(s):
(06) How will you support my solution requirements as a vendor?
And, more specifically:
(06.1)Who are your references who are comparable in size, scope, and needs to us?
(06.2)Does your solution support the functionality we absolutely require? Explain.
(06.3)Do you currently have customers in the (majority of) countries we need to deploy in and do you support the (majority of) languages that we require? (If you don’t currently support all the languages we need, how long does it take to add another language into your solution?)
(06.4)What is your organizational culture?
(06.5)How many non-critical functions on our wish-list can you address?
(06.6)How financially stable are you? Will you open your books to us or let us speak to a reputable third party that has seen your books?
(06.7)What is the total end-to-end cost of your solution up-front and on an annual basis? Will you guarantee this in writing?
(06.8)What third parties can we talk to who will verify your claims
(06.1)Who are your references who are comparable in size, scope, and needs to us? And can we speak to them?
As they say, the best proof is in the pudding, and the best pudding that a vendor can give you is references who are comparable in size, scope, and needs that they are currently serving successfully. They don’t necessarily have to be in your industry, but the industry should be similar enough that you can feel confident that the vendor could handle you. For example, electronics and component manufacturing are similar, but finance and pharmaceuticals aren’t that close.
(06.2)Does your solution support the functionality we absolutely require? Explain.
After you’ve divided your requirements into must-haves, should-haves, and nice-to-haves, ask the vendor to describe in detail how all of your must-have requirements will be met and briefly how they will meet each should-have that is on your list.
(06.3)Do you currently have customers in the (majority of) countries we need to deploy in and do you support the (majority of) languages that we require? (If you don’t currently support all the languages we need, how long does it take to add another language into your solution?)
If you need to deploy your solution across 20 countries and the vendor has only deployed across two countries and both were English speaking, how likely is it that the vendor will be able to meet your needs? On the other hand, if you only need to deploy across 6 countries and the vendor has deployed across 30 countries in twice as many languages, you know that you’re covered now and likely will be covered for years to come.
(06.4)What is your organizational culture?
When all is said and done, if you have three vendors who appear equal from every other perspective, the tie breaker will be the vendor’s organizational culture and how cleanly it meshes with yours. Even if you are IT and services savvy, you’re always going to need some help from the vendor. Maybe not that much compared to its other customers, but the vendor is typically the only expert in tweaking every last bit of value out of its solution.
(06.5)How many non-critical functions on our wish-list can you address?
Even though the functions are non-critical and wish-list, they’re on the list because someone wants them, and every wish-list item put there by a stakeholder that can be met is one less reason for resistance that you won’t have to overcome.
(06.6)How financially stable are you? Will you open your books to us or let us speak to a reputable third party that has seen your books?
Considering the effort that goes into solution selection, the last thing you want is to select a solution from a vendor that goes bankrupt in a year. Even if the code is under escrow, and you get complete rights to it, the value of the solution will decrease rapidly once the vendor stops improving it. That’s not a situation you want to find yourself in.
(06.7)What is the total end-to-end cost of your solution up-front and on an annual basis? Will you guarantee this in writing?
Considering that there will likely be implementation costs, integration costs, and training costs in addition to up-front license costs and annual maintenance costs, and may be costs for third-party middleware, data feeds, and other solution components, it’s important that you know all of these costs up-front and account for them accordingly. Otherwise, that 500K solution with an expected ROI of 9X return might actually be a 1.5M solution with an expected ROI of 3X – which won’t impress the CFO at all come performance evaluation time.
(06.8)What third parties can we talk to who will verify your claims
The vendor should be willing to give you names of investors, analysts, and bloggers who can verify their claims. If these do not exist, be wary. A good vendor is open about it’s capabilities and claims. It doesn’t hide behind NDAs and embargoes.