2 ms·
One of my early consulting prospects was someone who basically wanted me to do that for their app, at a similar price point. As I recall, the project went nowh
by patio11 15y ago
One of my early consulting prospects was someone who basically wanted me to do that for their app, at a similar price point. As I recall, the project went nowhere after they didn't follow up about signing a contract and I didn't follow up about following up.
In hindsight, after learning more about consulting, I am so glad I dodged that bullet.
You are setting yourself up for catastrophic failure in every way with this offering. You will not receive a complete spec from your clients. There are people capable of writing complete specs. They have done successful software development before. They will run screaming from your offering, because they're looking at $1k and 3 days and concluding "He's either insane, inexperienced, or out to swindle us." I plead a combination of insanity and inexperience for saying "Yes, that sounds reasonable for $2,000" to my prospect.
If you get takers, they will be the napkin crowd. The napkin crowd believe they have specs. They do not have specs; they have napkins. You can turn a napkin into a prototype; you cannot turn a napkin into a prototype in 3 days if it is not your napkin, because you will chew far more than 3 days of calendar time and $1,000 (or $2,500) in billable time just doing requirements analysis.
There are also jobs which, if one is not acquainted with reality as experienced by engineers, one might think are doable in three days.
Would you really love to receive this email? "Here's a screenshot. Make it work. I'll pay you a thousand bucks."
http://images1.bingocardcreator.com/blog-images/hn/this-is-not-a-spec.png http://images1.bingocardcreator.com/blog-images/hn/this-is-n...
Edit to elaborate:
If you're a good Rails/Django programmer, you are at least 20% of the way to a successful consulting business. The market is signaling in a very strong way that it needs them right now. (Ditto mobile anything.) That last 80% is very important, though. It includes things like getting good at estimation and prospecting. I ended up charging off about two months of calendar time to goodwill because I was ludicrously optimistic about estimation and how hard project management would turn out to be.
With regards to prospecting: There are plenty of people on HN who make good consulting clients. waves to consulting clients There are also many people on HN who, and I mean this in the nicest possible way, are not good clients at this point in their lives. Good clients have a clear idea of how the process operates. Good clients cut checks for five or six figures, in a timely manner, without complaining. Good clients have reasonable expectations for what $1,000 will buy them at market rates from someone who is actually capable of delivering projects in Rails/Django. (Hint: not much programming.)
- dspillett 15y ago> The napkin crowd believe they have specs. They do not have specs; they have napkins. Ah, like my boss you mean. Only he uses flip-charts or white-boards instead of napkins.
- discordance 15y agoWe recently did just this with a client. They weren't sure if the idea they had would float. They had a potential investor and the investment weighed in on if their idea would actually work in practice. We recognised that we could build their MVP pretty quickly, so we agreed to do it for a thousand bux, so long as they agreed that if their investor liked it and they got funded, we would get an extra (substantially bigger) amount to finish and polish the job. We developed the MVP for them for 1k and they ended up getting funded by their investor. So that part turned out well. We have now proceeded to polish the product for them at the higher fixed rate. For the most part it has been a success in that it has helped another startup realise their idea, and we have and will be getting paid accordingly. We placed quite a bit of faith in our client in following through with the subsequent job that justified our initial time investment, and that is something we were only able to do once we met with the client and formed a trust with them. Knowing your client and forming a trust is something more valuable than any web form/screenshot submission or even a contract. What we have learnt from this exercise: * The initial agreement period took a far longer than expected, almost a couple of months for a really simple $1k prototype. * People need a lot of hand holding, especially when forming their idea into a product... Far more than what $1k would justify. * The customer pivoted several times in terms of functionality, feature creeping all over us. We tried to account for this to begin with, but the amount their idea changed was quite unexpected. * Our client was very organised in terms of getting real users for beta tests. Every week we produced a new build, and tested it with a significant amount of real users. This helped the product turn into something valuable very quickly. We are going to try and make this mandatory for every client we work with from now. * We would not have taken on the $1k prototype job if we weren't confident that they hire us to finish the job for the extra substantial fee. So in summary, I think the $1k prototype is a great idea as long as you find a client you can trust who understands the outcome of the MVP, and also that you believe in their idea.