The Royal We: Single Founder Startups
ginzametrics.com
ginzametrics.com
In addition to OSS, the huge existing distribution channels like organic SEO, AdWords, and all those things you cool people use are also a major draw. Infrastructure has improved by orders of magnitude. APIs and snap-in services are getting better all the time -- ten years ago, payment processing was a multi-week endeavor, now you can do voice calls in about ten minutes of work. Scaling is... is solved too strong a word? There has been huge diffusion of the black magic of how to setup and architect things, both in the n-tier server architecture sense of the word and in the "here's how you get capital without slicing open chicken entrails" and "here's how you get users" senses of the word.
It is a great time to be alive.
On the other hand, if you're overly emphatic about the peril of going it alone, then if one of two cofounders leaves, the remaining one won't want to continue.
Motivation, more workers, and new ideas are all valuable contributions, but I feel like you might have missed the biggest benefit of all.
Co-founders can be good at the things you, personally, can't do. This is most visible in the business/technical co-founder division, but it can generalize to all kinds of tasks. If you're terrific at engineering large-scale filesystems (or whatever), but you can't build a web interface (or whatever), you might really need a technical co-founder with a different skill set. Every day or so, my co-founder cranks out something that would have taken me a week or more in a few hours.
Don't underestimate the value of teaming up with someone who's as good as you are at different things!
Speaking as a one-man startup, I think the problem is worse than skills-sets, and worse than the costs of switching between tasks; it's also values - not in terms of ethics, but in terms of where your attention goes. eg. attention to detail vs. big picture; the product vs. the market; the solution vs. the problem. One person definitely can do it all (and it's getting easier) but it's more than twice as hard as having two people.
However, whether it's easier or harder for two people is less important than whether it is easy enough for one particular person to do it.
I'm curious about the line between co-founder on paper and the role a spouse or significant other plays? A spouse in this position is clearly contributing to the success and viability of the "single-founder" venture. If the spouse is not there to help this would increase the workload and the founder would have to seek out someone else for emotional support. The shared risk is there as well as the shared hardship. If the founder can say that their spouse has been as much a part of the start-up as they have, then how they not a co-founder?
They may not be a founder on paper, but especially in light of how assets are split during a divorce it seems the reality shows that they do have a stake in the business's earnings.
As a single founder, I don’t agree with that. Once I passed a few hundred signups, I found that people were willing to write in and tell me what they liked and didn’t like about my service. Now, I find myself with a list of things to get done because that’s what my customers want (not to mention what I personally want). Like the author, I “never feel at a loss for ideas (and have more than I know what to do with)”.
Emotional support, however, is hard because it’s not something you can take care of on your own; until you have people validating your work as worthwhile, it can be difficult to believe in yourself.
I think that “two (or more) heads are better than one” for solving issues, whether they be technical or with regard to how an idea should be executed.
Otherwise, nice essay (although I was hoping for a discussion on why single founders use “we” in their text instead of “I”).
Regarding "we" vs. "I", I actually had that in my draft but it didn't flow well with the rest of the post.
As was I. My own thoughts are that "I" sounds unnatural when you're talking about a non-human entity like a corporation. Somehow, "we" does not. When I say "I launched a product", I feel like it means that I, the person did it. When I say "We launched a product", it means the company did it, even if it's just me. "We" might be more than me (or not me at all!) in the future but I will always be just me.
And when it's launched it's looked what 'I' did.
Cynical? Moi? Never ;)
That said, there are still people who are going to do startups on their own anyway and some will be successful. I wanted to share what's worked for me so far.
The background I began with was to provide clarity around why people advise against going it alone and some creative ways of making it work when you don't have the natural advantage of co-founders.
It's rare for good engineers to have an entrepreneurial/business mind - thinking about, and being aware of, the business world outside of code (business strategy); understanding people (sales/marketing/team leadership, when there is a team). These kinds of engineers are amazing!! :)
For example, in a retail or fast food establishment, one person will usually handle the operations side and the other will handle the business side.
I really don't think a startup is really a startup if you don't have anybody working with or for you. That's also legally reflected in the difference between a sole-proprietorship and C/S corps.