…but it is also one big pain in the neck! I have been thrown into the process of answering an RFP (request for proposal) for a city government down here in Texas, and I cannot begin to tell you how tedious and ridiculously complicated the whole process can be. RFPs can be complicated enough with corporations. But when you get one from a governmental entity, you have so many other things to worry about (there are a ridiculous number of special considerations and conditions when you do work for governments).
Another thing I am finding out first hand is that many government workers (not all, but I wouldn’t think it too far from the truth in saying most) are functionally inept in their positions, at least when it comes to technical matters. Though I have had some inkling of this from talking to peers over the years, it amazes me when I see it so closely.Â
First of all, the RFP is very poorly written.
Second, it is incomplete.
Third, when you try to ask questions to work out the inconsistencies, the answers are often, “Because I say so”, or “Don’t question why our network is setup as it is.”
I don’t know if we will win this contract or not. If we don’t, then we have wasted a LOT of man hours.  I guess it is worth the payout if it happens, but I have to wonder if anyone has figured out the cost of NOT getting one of these and compared it to the potential profit. I am sure someone has.Â
And if you are thinking that I make a salary, so it doesn’t matter, then think again. I have about 4 projects for which I am either scoping or actively talking to clients to complete. Two of these are sure things, and two are 50% or above on probability. And these aren’t some small deals you can just sneeze at. There is good money to be made here. So the more time I do this dang RFP, the less time I am working on some potentially good profit for Accuvant. All to work on a deal that no one has a good idea whether it will come through.
Oh well, business is business!
Vet
