Now, does he really have that kind of dough laying around (ie: angel funding), or will I never here from the client again because he was hoping to get it done for $200? (Or worse: profit sharing / equity arrangements. Equity doesn't pay my rent.)
Now, does he really have that kind of dough laying around (ie: angel funding), or will I never here from the client again because he was hoping to get it done for $200? (Or worse: profit sharing / equity arrangements. Equity doesn't pay my rent.)
I may be jaded about this because so many of our bids are competitive, and even a simple bid takes a couple hours to put together. We win most of them, but you get used to sinking time into deals that don't pan out and build it into the process.
I think this has two advantages: I don't put that much time into "no real business here" leads, or (if there is business there), there's no way I know the whole scope of a large project in one conversation.
I've actually revised my standard "potential lead" email based on some of the conversations in this thread. I now make it explicit that (a) I can help put together an Agile product backlog, for those larger project, and (b) make my hourly rate for this project manager/product owner work very explicit (to filter out those that don't actually have money)
I think there's a little bit of culture shock going on here between our particular contracting fields.
If you're doing enterprise-ish security contracting, you're not going to get an unemployed person in your lead pile by accident. I get three e-mails from unemployed people a week. I get 20+ leads a month from questionably-funded "startups". The number of revenue sharing posts per day on Craigslist is competitive with the number of police stations in the metropolitan area. etc.
Just to have a 30-minute conversation to determine if somebody is funded or not simply does not scale to the number of interested parties. Even reading all the e-mails and throwing them away is a massive time sink. Let alone estimating anything, thinking about the feasibility of anything, etc.
(Seriously asking because I'm curious).
1) The sort of people who pass through the existing filters I have in place (I show some prices on the contact form) who have unfunded projects will claim that they are funded. The question has a shannon entropy of zero.
2) Everyone, funded or not, is cagey about the actual budget. In the iOS world, "funded" can mean anything from $500 to $500,000. If I say "So, what are you looking to spend?" they will reply "I'm not really sure what the project will cost, can you estimate it for me?" You get this line the same from a CEO or from an intern, from a bank manager or from an unemployed person calling on a payphone. If I say "Our average project cost is X", I am turning away some projects we could legitimately do for less than X with a very comfortable margin while accidentally dangling a carrot in front of a client who has a project that's really 3 * X. The former is an invisible cost, the latter may mean lots of time spent on useless estimates instead of actual billable work.
3) I used to have an e-mail autoresponder that would inquire about budgets, but on a typical day I started spending more time reading replies to my autoresponder than writing actual code. asking the question isn't scalable.
It certainly helps sometimes in picking out project infrastructure ("I have to do this cheaply, so let's get inventive")
"You want a database on the web, that you can customize yourself, for $600? Great, let's grab a copy of FileMaker Pro, or sign up for Quickbase.com and get going" Yes, those solutions may limit potential of the app down the line, but they might actually be the right fit.
I'm another hourly-rate-all-the-way guy, but if I can extract the budget out of the client, then I can decide (essentially), "Given the client's other requirements, will a RAD/off-the-shelf/OSS-package-with-a-custom-theme work for this project... or do I just politely tell the potential client to get bent?"
In situation A it is usually because they see my hourly rate a pricy and so they give up their max budget, as a negotiating tool. In which case I tailor the solution to that budget.
In situation B they generally have a budget in which they don't see my cost as even making a dent in.
Finally in C generally we would have never had a meeting of the minds in the first place. I don't compete on price, there was a point where I had the price shoppers filtered out of my sales pipeline, but as we are bringing on new clients again, we do end up in situation C from time to time.