|
|
|
|
|
|
by jroseattle
4064 days ago
|
|
|
Thanks for the reply, Mike. I was referring to the bullet-point list of "How will this help you?" on the webpage. I haven't read the book, so my feedback is entirely based on the website content. I've been both the single entrepreneur as well as a co-founder. I found that list to be entirely applicable to both scenarios. (Good list, BTW!) Anyway, just offering some feedback that I thought there would be a greater emphasis on the unique challenges for a solo founder vs. a team. Indeed, I'm not sure there's a more concrete example of "judging a book by it's cover." :-) |
|
|
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.