|
Totally misleading title (good choice for AL, bad for HN). I am myself a 1-man startup and it is hard to get any good advice other than "don't be a 1-man startup". Well, I am. And I am pretty sure is the right choice for me for now. I don't want to get in an accelerator, I don't want VC money, I don't need to correspond to anyone expectations about what makes me more likely to succeed. I just want advice on how to improve my chances being a 1-man startup. Well, so I share my experience for those who came to this post thinking the same thing as I did. An obvious statement is that 1-man startup is not a 1-man's work. I outsourced design and engineering (code to developers, infrastructure to Microsoft Azure). Mostly I am responsible for customer development, product management and growth marketing. But this year I quit my job in order to learn how to code (simultaneously HTML/CSS, javascript and C#/.NET) and be able to better take charge of my startup. Still, I am talking to two developers (a junior and a senior) to work by the hour, with the expectation to become a full-time member of the team - as a freelancer-mode experience period that, if successfull, become co-founder or Director/VP of Engineering. My to-do list is long, dynamic and diversified. It is not that hard to keep changing hats, but it is extreme hard to know when to and to which hat change. What is my priority? I have no idea. Talk to early adopters, fix some spceficic bugs, A/B tests on design, handle twitter account, learn how to code, better develop my vision, the product roadmap, etc. One thing I learned is that complete development outsourcing is a mistake. It is expensive and hard to manage. I wish I had the freelance-as-a-test-to-co-founder approach much sooner.
Other lesson (opinion) is that the "learn to code" advice is prioritary to "don't be a 1-man team". I would love to read more advice out there on how to be a better 1-man startup. Don't bother telling me the best option is not to be. |