Almost two months ago now, Joel Semeniuk blogged about responding to RFPs and how awful it is. The thing is, it's really hard to keep a business larger than one person afloat without ever responding to them. And once in a while, you get the contract, which is fantastic but keeps you from blogging .
Gregory Consulting is in the midst of not one but two contracts landed through RFPs right now, and I just can't help myself, I'm responding to another, this to get on a Vendor of Record list for, er, a major provincial government. About two years ago this ministry built a list and the RFP had a due date for responses of December 23rd. The first Q & A session was full of questions about the deadline, would it be postponed, and the answers were oh no, absolutely not, there's plenty of time for you to make a good response in that time. Every Q & A after that, the same question, the same answer. Until two weeks before the deadline when they announced a four week or so extension. So here we go again in 2004 and the due date was July 29th, and the Q & A literally complained “the government is ruining my vacation” and the answer was “we are ruining our own as well but there will be no extension.” Again and again people asked and were told the deadline was immutable.
I've been busy doing the work I landed but I settled down last night to pull the whole RFP package together so it could be printed and bound today and hand delivered tomorrow. And with a horrible sinking feeling I was realizing I had hours of work writing project profiles and filling out checklists. I got to the bit where you have to list all the addenda you have seen, popped up to merx to get the most recent addenda (I've been busy, remember?) and -- hey! This thing closes August 19th now!
At least I found out before I stayed up all night.