Hi,
In my practice till now I have been involved in preparing or receiving and reading RFPs (Request for Proposal). I have seen that depending on what you have included, this might turn sometimes into "unmet expectations" and misleading communication in terms of deliverables.
My questions here are:
- What is a good RFP according to your experience?
- How can you mitigate the risk of reading a RFP and expecting some work, that has been "out of scope" for the Requested, but "in scope" for the Requestor?
- In terms of competition, how detailed would you explain your plan of work and outcomes to be in an engaging format, but still keep the "secret sauce" of the company for once you win the work?
Any thoughts and experience are highly appreciated.
Thanks,
Kate
A discussion on the topic might bring some interesting insights. My experience is not as extensive, but I will share my observations:
- what is a good RFP? It is hard to have a "panacea". Pretty much depends on the tender - whether it will be for software, services, etc... Of course a good practice is introducing a standardized template in your company, which will make it faster to prepare and easier to read (especially when regularly addressing one particular market the vendors will get used to it).
- if you need software product, the more detailed the RFP, the better. Usually it is being attached to the contract with the vendor. If you are a client, the more functionalities you mention, the more you will get for the money.
- I don`t know about the "secret sauce" thing. So far, being from the customer side we have never liked it. Usually large organization don`t like surprises of any kind. On the other hand if you present all your competitive advantages, this will take you one step closer to getting the deal.