43 karma · joined October 12, 2009
If you look around at that "traditional" startups covered by news or accepted by YC, they don't talk about single founder startups. In my circles (MicroConf, Micropreneur Academy, etc) it's virtually nothing except single founder companies. So there's a misconception that single founder startups aren't possible or don't work.
For VC's and huge scale startups, that may be true. But I know of hundreds of small scale software companies that are doing just fine that would beg to differ. It's a matter of what your goals are and what you want out of life.
The title is meant more to draw attention to the fact that if you're a single founder, this book is for you. That doesn't change the fact that it's useful to small teams or to any software startup. But when you have two people working on something, the discussions tend to be different than the ones you have in your head.
I wrote the book in such a way so as to be that other voice saying the things you would have needed to hear from a cofounder. It's not necessarily about the message itself in many cases, so much as the subtle nuances of how that message is communicated that will make them more understandable and resonate better with a single founder.
In some ways, the title is a marketing strategy too.
I do include a discussion of taking on a cofounder in the book. Personally, I don't think that having a cofounder is bad per se, but having a bad cofounder is significantly worse than having no cofounder at all. The downside to taking on a cofounder is that your ambitions for what to build need to increase proportionately because now it has to support 2 people, not just one. It's no longer just a matter of getting 2x the work done. Basically everything doubles.
Any thoughts or suggestions are more than welcome.
I'd like to find a solution to this long term, but in the short term I don't have one yet.
I would also recommend Rob's book as a starting point. Many of the problems people run into are mindset related and knowing what else is out there, what things people have tried, and how they worked out is really important. Once you realize that something is possible, you can make it a reality. But without having concrete examples, it's difficult to make that mental leap.
I'm in the process of writing my own book on this topic called The Single Founder Handbook. http://www.singlefounderhandbook.com that you might find useful as well. Should be available within a month, but four areas it focuses on are Idea Generation, Filtering, Validation, and Execution. People have a tendency to jump right to code sometimes without thinking about whether or not the idea ticks off a bunch of specific criteria or validating it.
I think you'd find these areas helpful.
The reason BOS is so expensive is because it's in Boston and they don't have sponsors. Vegas is significantly less expensive to host a conference. We did look into Boston and it was kind of ridiculous.