Deciding on the Best CRM Software For Your Business
February 26, 2008
After you’ve had a couple presentations from CRM software vendors, it’s time for your selection team to convene and compare notes. Save discussions on individual software choices until this meeting; this prevents premature decisions being made without the benefit of full discussion with all view points represented.
Evaluate the CRM Software technology, not the Partner
Remember: this meeting is to evaluate the technology, not the Partner. Yes, it’s human nature to role the two together and to some extent it’s unavoidable. However, do admonish your Selection Team to focus on the technology.
On your quest to find the best balance of features and budget, there are a few critical questions to answer at this meeting:
- Is there a clear technology winner?
- Is the project still feasible? It might be that the proposals all came in way over what you had in mind for a budget.
- If there’s not a clear winner, do we feel at least one or two of the CRM software choices may be sufficient? (watch out for inadequate presentations done by Partners).
The Structured Proposal
It can be very tricky to get a proposal that reveals the true costs of a solution. To help you get a reasonable apple-to-apples comparison, I’ve developed a very simple technique I call “The Structured Proposal”.
(check out the CRM Survival Guide if you are interested in the Structured Proposal)
Problems With Just Getting a Quote
You’d think that a sales quote is a sales quote. But with CRM it can be anything but. If you let each presenting Partner give you a quote as they see fit instead of in the Structured Proposal format, you’ll get a wide range of quotes and have no valid basis for comparison.
If you were to take the typical quote from a Partner and then have them re-do it using the Structured Proposal format, the new quote would likely be significantly higher. This is because it is designed to force the Partner to put a fair bit of thought and specificity into it, digging up costs that usually are glossed over.
The Structured Proposal is designed to make it easy for you to reasonably compare the costs associated with each technology. (while you won’t get to a true “apples to apples” comparison, you may get to an “Ida Red apple to Empire apple” comparison.) The format of the Structured Proposal is simple and
yet designed to make it difficult for Partners to “play games” with their quotes.
The 4 Elements Of The Structured Proposal
1. Software Costs
This is really the key to what makes the Structured Proposal work. Usually, Partners will bury any custom development work into services and often just quote the programming costs, leaving out such things as rework (and you can bank on there being rework on any custom development). With the Structured Proposal, you’re instructing them to be much more precise:
- Create a detail line for each custom development piece.
- For each piece of custom development, they’ll have to sign-off that they’ve considered: Functional
Spec, Detailed Design, Programming, Unit Testing, at least 2 rounds of revisions and delivery.
2. Service Costs
Each category of service should be clearly delineated. You want this to be broken down into enough detail that you get the sense that they have thought through all the various areas that will be needed.
This is a very effective device. By explicitly asking the Partner (in writing) if there are any areas of concern, the likelihood of you getting an accurate picture goes way up. Often, there will be areas mentioned in here that will warrant more discussion and perhaps more investigation on the Partner’s part. This can lead to some very useful and effective communications with your potential Partner. Partner’s that use this area well are taking a big step towards earning your trust and confidence.
4. Sign-off declaration:
There’s nothing like putting a corporate officer’s signature to a declaration to make sure that what they’re signing-off on is accurate! “I have read and understand the Business Requirements document and the attached quote represents within +/- 20%”
You need to look at the cost for the whole solution to account for differences in each software’s native strengths and weaknesses.