Responding to RFPs

RFP and I generally avoidthem, but sometimes a good onecomes around and Ikeep thinking that yousay I'm not in the businessof writing proposals.So I do.What do you do whenthey are asking youfor your strategy in an rfp?I mean.Well no, well, I mean, Ican go back to them and say.I can pay me to do the strategy.So I can answer this RFP.OK my thoughts on RFP.So the questionphrased would be,what are yourthoughts on our ps?Because I'm not sureI want to do them,but I feel tempted to do itbecause some of the projectsare very tantalizing.That's your question, right?Yes, once in a while.OK, that is my question.Here's the problem with our.It's just really lazy.It's a really lazyfor companies thatare reps because theywrite a generic document.Some of them don't evenread their own documentsand it's veryboilerplate, meaning theypump these thingsout and they justwant a bunch of peoplejust jumping at it,throwing things at it.Our process to solveproblems requiresme to talk to the client tounderstand who their users areand their pain points.I cannot do that.I myself just doesn't work.So, in essence, then I'm askedto guess and to guess and givemy best thoughts on somethingthat's based on nothing.How good can that be?I don't know.So typically, whenI see an RFP, I justsend a capabilitiesstack and say,if you'd like totalk to us, we will,but we don't do work for free.And it's not helpfulto you or anybody elseto have peopleguess at a solution,you might get luckyand find somebodywho thinks they have an answer.But I don't like to gamble.OK OK.That's what I'mgoing to do today.Try see what happens.So I do send capabilitydecks and I just tell them,if you want to pay me,I'll solve the problem.And they can choose whoeveryou want to work with.But they never want to pay you.That's why they sent out an RFP.It's usually part of.