A few weeks later he e-mailed back asking how much he would have paid if that friendly chat with an official consulting job. The answer was around $10,000. Yes it was only 2-3 hours of time, but built upon thousands of hours of experience. And the changes they could immediately implement would generate more than $10k in increased revenue so it would easily be worth it.
My point here is that it doesn't matter jack shit how many hours are spent on a project or how cheaply it could be done. What's infinitely more important is how much money can be made. If you can get more money out than you put in and putting more money in means you get more out then you put as much in as you can afford. Now for someone to plop down a million bucks on three months worth of work means they'd have to be unusually confident in a project's chances of success. So that number I gave is pretty high. However paying big money to a seasoned vet to get the ball rolling makes an unbelievable amount of sense.
Needless to say, times change. At present, Patrick's consulting rate is somewhere north of $30K a week [6], and dare I say it, I'm sure he's worth every penny of it for the right companies.
[1] http://www.kalzumeus.com/2011/07/08/business-psychology/ [2] http://productpeople.tv/2012/12/26/patio11-part2/ [3] https://news.ycombinator.com/user?id=patio11 [4] https://news.ycombinator.com/user?id=tptacek [5] https://news.ycombinator.com/leaders [6] https://news.ycombinator.com/item?id=8574541
Even if it was their idea (aka no communication and decision overhead, working 16hours/day), two month is pushing it.
If you have tight, modular code following good practices (e.g. a relational backend, not an ORM), you have experience doing it before, there's no micro-manager, and with a clearly defined, functional spec, you can build robust things that scale well relatively quickly. We're not talking about a new Facebook here, merely copying 80% of the functionality of an existing product for a launch in markets with no competition, as greenfield. Also, it's not like a site like that would reach a million users in a couple of months, nor would it win design awards, but why should it? It just needs to process transactions accurately and list a bunch of shops across a few countries.
I do think that the global market for programming talent is like that for real estate here in Singapore: I pay around 2 grand a month, and my neighbours across the street something like 8-10 for the same space. It is what it is. You'd be amazed how "cheap" it can be to hire a greybeard these days, sometimes less than twice a fresh Stanford grad...
>It just needs to process transactions accurately and list a bunch of shops across a few countries.
Yes, I hear this kind of off-the-cuff assessment frequently from potential clients, and I turn them down if I'm not able to help them see the complexity often involved.
After all, opentable is a restaurant reservation system for the entire world.
>You'd be amazed how "cheap" it can be to hire a greybeard these days, sometimes less than twice a fresh Stanford grad...
This is true, and the open ageism among SV companies makes me incredibly sad.
Knowing how/where you can effectively add caching, or even pre-aggregated data into an existing system can be the difference between a system going under, and being able to keep the single-instance database server from collapsing your business while a new system can be established.
Two months, with two experienced engineers should totally be enough. Sure it's not going to have all the bells and whistles but it should at least be a very very good better than MVP.
To share an anecdote: I was having a chat with a HNWI who wanted to "get into startups" about the cost of launching a product that he was thinking about (something similar in complexity to OpenTable). He had very high estimates in mind, something along the lines of what you're talking about and half a year.
I told him it was probably possible to do it much faster by employing experienced developers at a high hourly rate but whose experience would drastically cut both mistake time and planning time. He asked me to get him a quote, so I contacted two guys I knew from the functional programming meetups, both with PhDs and recently published papers, both with half a decade experience in a big famous company based in Silicon Valley, both having worked with each other on consulting projects for years, and they spent a week drafting a rough, serious quote.
The estimate came to around 25-40x cheaper than what you're talking about, and two months (part-time, on the side of their research work) to launch + USD 2k/month post launch to maintain it with no new features.
Of course, the HNWI changed his mind (in part due to a co-investor on another project who objected to the "high" estimate and told him to use free or cheap fresh grads instead... welcome to the world outside the US) and I profusely apologised to my contacts for having wasted their time, but it did put an order of magnitude on the "high quality contracting" idea.