On RFP's...
As poacher turned gamekeeper I’m only too aware what a pain preparing responses to requests for proposals (RFP’s) can be. However I get to read a lot of responses these days, and it can be tough on the other side of the table as well, so I want to set out some thoughts on what distinguishes a good from a bad response.
The first point I’d make is that companies issue RFP’s for a reason – they need to make a purchase decision. The quality of the RFP response forms part of the purchase decision. I make that point because some vendors seem to pursue a strategy of preparing a response, which, while not of great quality, is what they believe to be enough to make the short list. The problem with this approach is that it’s predicated upon the notion that once the short-list is finalized everyone starts afresh on a level playing field. In reality this isn’t the case. The vendors with the strong response, are already ahead on points once the next round starts. We tend to rank the responses we receive, and this initial ranking is visible through the entire decision making process. A high ranking can sometimes also confer additional benefits, such as first choice in selecting a presentation date. So the stronger the initial response, the better the chances of winning.
So what’s the difference between a good response and a bad one? A few thoughts:
A good response answers the questions. Customers pose questions in RFP’s for a reason – they want answers. Not answering the question, or the more common practice of answering a question, just not the one that was posed, gets a big red cross in the margin.
A good response answers the question without direct recourse to an appendix, as in ‘please see appendix Z’. While this practice is marginally less irritating than not answering the question at all, when you have a pile of responses to plough through, the need to hunt around to find the required information is an undesirable diversion, particularly when the referenced appendix is invariably an opaque piece of techno-babble. That said a succinct answer, referenced to an appendix should the reader require more detailed information, is more than acceptable.
A good response makes little use of the cut and paste function. Inserting seven pages of marketing waffle in the midst of the response because it seems to be generally on-topic, again only scores highly in the irritation stakes.
A good response is candid. If the product doesn’t exactly meet the requirement, then the respondent is going to earn points for being open and honest about the situation, thereby positioning themselves as people we can work with, rather than trying to hide the fact. The latter strategy is likely to be rumbled at some stage anyway, either straightaway because we already know the issue or at some stage in the selection process.
A good response pays at least some level of attention to spelling and grammar. While we wouldn’t expect a masterpiece of English literature, we would figure on some level of attention to detail. It doesn’t matter how well the product and vendor are respected in the market, or how great their track record, prospective customers will judge responses as the prima-facie evidence as to how they will be treated should they become a customer. If the response is riddled with errors then the prospective purchaser is likely to conclude the vendor will be as error prone when implementing their system.
A good response follows the requested format. Comparing apples with apples can be complex at the best of times, particularly in respect to pricing. This can be made an order of magnitude more difficult when respondents take it upon themselves to demonstrate their creative side and ignore carefully prepared templates.
Finally, good responses don’t forget that their ultimate purpose is to sell. Some vendors overlook this. In a world where the differences between products and vendors are often slight, and we’ve tough choices to make, we like respondents to clearly explain ‘why us’.
I guess the recurring theme here is about making it easy for the prospective customer. When you get to work your way through a thousand or so pages of responses, clear concise honest communication really does stand out.
The first point I’d make is that companies issue RFP’s for a reason – they need to make a purchase decision. The quality of the RFP response forms part of the purchase decision. I make that point because some vendors seem to pursue a strategy of preparing a response, which, while not of great quality, is what they believe to be enough to make the short list. The problem with this approach is that it’s predicated upon the notion that once the short-list is finalized everyone starts afresh on a level playing field. In reality this isn’t the case. The vendors with the strong response, are already ahead on points once the next round starts. We tend to rank the responses we receive, and this initial ranking is visible through the entire decision making process. A high ranking can sometimes also confer additional benefits, such as first choice in selecting a presentation date. So the stronger the initial response, the better the chances of winning.
So what’s the difference between a good response and a bad one? A few thoughts:
A good response answers the questions. Customers pose questions in RFP’s for a reason – they want answers. Not answering the question, or the more common practice of answering a question, just not the one that was posed, gets a big red cross in the margin.
A good response answers the question without direct recourse to an appendix, as in ‘please see appendix Z’. While this practice is marginally less irritating than not answering the question at all, when you have a pile of responses to plough through, the need to hunt around to find the required information is an undesirable diversion, particularly when the referenced appendix is invariably an opaque piece of techno-babble. That said a succinct answer, referenced to an appendix should the reader require more detailed information, is more than acceptable.
A good response makes little use of the cut and paste function. Inserting seven pages of marketing waffle in the midst of the response because it seems to be generally on-topic, again only scores highly in the irritation stakes.
A good response is candid. If the product doesn’t exactly meet the requirement, then the respondent is going to earn points for being open and honest about the situation, thereby positioning themselves as people we can work with, rather than trying to hide the fact. The latter strategy is likely to be rumbled at some stage anyway, either straightaway because we already know the issue or at some stage in the selection process.
A good response pays at least some level of attention to spelling and grammar. While we wouldn’t expect a masterpiece of English literature, we would figure on some level of attention to detail. It doesn’t matter how well the product and vendor are respected in the market, or how great their track record, prospective customers will judge responses as the prima-facie evidence as to how they will be treated should they become a customer. If the response is riddled with errors then the prospective purchaser is likely to conclude the vendor will be as error prone when implementing their system.
A good response follows the requested format. Comparing apples with apples can be complex at the best of times, particularly in respect to pricing. This can be made an order of magnitude more difficult when respondents take it upon themselves to demonstrate their creative side and ignore carefully prepared templates.
Finally, good responses don’t forget that their ultimate purpose is to sell. Some vendors overlook this. In a world where the differences between products and vendors are often slight, and we’ve tough choices to make, we like respondents to clearly explain ‘why us’.
I guess the recurring theme here is about making it easy for the prospective customer. When you get to work your way through a thousand or so pages of responses, clear concise honest communication really does stand out.
posted by Richard Boardman at 6:45 pm
<< Home