Responding to RFPs

RFP and I generally avoid them, but sometimes a good one comes around and I keep thinking that you say I'm not in the business of writing proposals. So I do. What do you do when they are asking you for your strategy in an rfp? I mean. Well no, well, I mean, I can 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 question phrased would be, what are your thoughts on our ps? Because I'm not sure I want to do them, but I feel tempted to do it because some of the projects are 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 lazy for companies that are reps because they write a generic document. Some of them don't even read their own documents and it's very boilerplate, meaning they pump these things out and they just want a bunch of people just jumping at it, throwing things at it. Our process to solve problems requires me to talk to the client to understand who their users are and their pain points. I cannot do that. I myself just doesn't work. So, in essence, then I'm asked to guess and to guess and give my best thoughts on something that's based on nothing. How good can that be? I don't know. So typically, when I see an RFP, I just send a capabilities stack and say, if you'd like to talk to us, we will, but we don't do work for free. And it's not helpful to you or anybody else to have people guess at a solution, you might get lucky and find somebody who thinks they have an answer. But I don't like to gamble. OK OK. That's what I'm going to do today. Try see what happens. So I do send capability decks and I just tell them, if you want to pay me, I'll solve the problem. And they can choose whoever you want to work with. But they never want to pay you. That's why they sent out an RFP. It's usually part of.