|
Over the years, I've been on the recipient end of many a request for proposal (RFP). Like many sales professionals, early in my career this created excitement and a flurry of activity on my part, caused late nights, missed dinners and visions of endless revenue. I learned, as many have, that when an RFP is distributed, it's sent to many possible suppliers. By definition, the odds of any one firm winning are not great, unless that firm has stacked the odds in their favor. That was an important lesson. Today when I receive an RFP I still respond, only not with a proposal. I follow a process destined to obtain access to the executives involved with the decision so that I can understand the problem they are trying to solve. This allows me to probe deeper into the root causes, with the hope that I can help the executives more fully understand the problem, its impact and its urgency. Naturally I'd like to bias this understanding toward the solution I hope to ultimately propose, but only if I can do so honestly and with integrity. Of course this is an approach that we teach in the CustomerCentric Selling workshop. Even though I'm happy that I learned this lesson early in my career, I'm surprised at how many people haven't, and find themselves in constant response mode, but still with a low batting average. In business, it's important to try and stack the odds in your favor as much as possible, and if you can't use the RFP process to re-engineer the buying process, your odds are improved if you decline to respond and focus your energies on more promising opportunities. 6 Responses to "Responding to RFP's"
Posted by: Gary Walker
Tuesday, December 21, 2010 @ 7:48:49 AM Matthew, I think it is very important how you respond. The response needs to be a rational, logical, and unemotional business response. When the 'unsolicited RFP/RFI' arrives the first thing that I do is to study it to see if I can one, identify who may have helped them craft the request, and two, determine if I'm capable of providing them with the capabilites that they are requesting in the RFP/RFI. If I can't, it's a no brainer. However, if I can, I call the issuer, thank them for considering, advise them it will probably take me about 40 to 80 hours of my time to research and prepare the response they have requested, and request an opportunity to speak individually, on the telephone, with the three (3) people I think are going to be impacted by the selection of the product and/or service covered by the RFP/RFI. My reason for wanting the meetings is obtain a complete and thorough understanding of what needs to be accomplished and why. It allows me to do a better job and the 'prospect' obtains a much more satisfactory response; the prospect is the major beneficiary of my request. Usually, but not all the time, you are denied the requested meetings. At that point, I advise them that if they are unwilling to provide me with what would amount to three one hour interviews, then I'm unwilling to invest the 40-80 hours of my personal time to fulfill their request. I then follow-up the conversation with an email that 'documents and confirms' the telephone conversation and leaves the door open for them to re-enage with me if the reconsider their position. At that point I'm done. No need investing all that time and work into an RFP/RFI that is wired for someone else and, that I don't have the opportunity to change the requirements. If you would like a 'generic' sample of the email we suggest you use, just send me an email and I'll send it to you. Posted by: Matthew Fuellhart Tuesday, December 21, 2010 @ 4:49:30 AM How important is how one declines the invitation to respond and what is advice on the best way? Post a CommentOther Recent ArticlesCategoriesBlogroll & Resources |









