Are you a solopreneur? How does it work for you?
I had a small game dev studio, but I found that I wanted to work on more interesting technical issues by myself. Currently I'm working as a one person consulting company, for the development of new tech related projects. Projects I work in are very interesting, I learn a lot with my work, and I also keep a better part of the gains of the company. However, I have issues with the kind of services I can provide: I can't provide a soft development service as, once I'm developing programs for one or two clients (even if I make a part of it be developed by a third party), I have no more time to do a second or third project. So I'm starting to provide a consulting service, and only eventually offering development for very interesting projects.
It's working now but this is new for me, and I'm not sure how I'll manage this in the future... what do you think about it? do you know other cases similar to mine? how do they / you manage this kind of problem?
In my case, the project I just finished prototyping (yes, this is a plug/request for feedback, although the product is of extremely limited interest to this community) solves a narrow problem in the electricity industry: Energy meter data is passed around in an obscure binary file format (MDEF) that few people can understand, read, or troubleshoot when they receive a broken file from a 3rd party. There's a need for a tool to wrangle this format, and I believe I can do one that's better and cheaper than anything out there, with a modest effort.
As for why I'm a solopreneur: I didn't know any good co-founder candidates, and didn't have a compelling sales pitch. ("Hey - let's quit our jobs, and poke around for a product that we can try to build into a successful business" is a little too honest!) I also didn't want any more of my life to drain away writing vbScript (long, long, long story) and, as the great Peter Gibbons put it: "I don't think I'd like another job".
I'm not philosophically opposed to growing the company, but it will have to be from a "given this problem, I need more people" angle, rather than a "let's enlarge the team, and hope something good happens" view.
P.S. http://www.mlsite.net/meterdoc
This is very useful advice, it's a good rule to have in mind. I'm actually doing development, but I don't do active promotion of that as I can only do one project at a time, and projects tend to go for months. But as I keep developing on projects, I keep very focused on them and only a little consultancy work and some basic business meetings, sales, etc keep me out of full focus on dev. But I don't think I'm in the minimum yet, so I'll really think in what you said.
I also agree with you in prefering the "given this problem, I need more people" angle, for growing the company.
Thanks a lot for your useful and very interesting! advice, and good luck with your new project!
I also started a startup solo a couple years ago, and the combination of running my other company by day (splitting my time) and being the only person to do everything certainly factored strongly in its early demise. Got to about 10,000 users but couldn't take it to the next level because there was simply not enough time in one day.
My new startup that's launching any day now (waiting on a couple things like payment processing to be hooked up) is a partnership, and while I'm still splitting my time with my main company and I'm also the only programmer, it's been way better because it's two and not just one of us. After these experiences, I'm now definitely sold on PG's recommendation of having more than one founder. The key still is to find the right co-founder, but I think unless you want to work 16-hour days (which isn't sustainable!) then you need 2+ people involved.
As a one person shop I can't do much more than consulting, and as a technically minded person I find that I'm not particularly motivated to do the promotion / PR / SEO side of things. I'm on the lookout for a cofounder now but it's hard(er) to pick one up after college and all my friends want stable jobs instead of entrepreneurship.
If it's working for you now then I wouldn't worry about it. I find that getting myself motivated to do the non-technical things was the key to getting more success when going solo.
The important thing I've found is to build assets that have the potential to creative passive (or near-passive) income and then run those in parallel to your more experimental ideas. Ideally, you can then sell off some of those assets when you need more time or more cash to put into other ideas.
On my part, I started a code snippets repository a few years ago. Only took 24 hours to do the first version, then it got another few days work a year on. It made about $800 a month for a couple of years, then I sold it for $30k. Not giant money but that's just one of many projects. I sold another one for a lot more just several months later. Having savings and a passive income that pays all your bills makes it a lot easier to work on the bigger and more experimental projects!
As to the "why".. I as in full-time work for almost a year after leaving school, and it didn't click with me at all. I wanted to run everything. So I became self-employed, and despite earning a pittance for the first few years, it was totally worth it. Besides, none of my friends are technically or academically minded, and I don't know anyone like that who lives nearby, so I'll be dreaming and working on my own for the foreseeable future :)
I should point out, however, that when I reach a point where I need other people to launch larger scale projects, I will happily hire them.. online! Just because you're on your own doesn't mean you do everything alone. You always have to rely on other people and companies, whether it's for your hosting, graphic design, printing, or whatever. If you live in the general economy, you're never as "solo" as you think.
I care now a lot that new projects will always improve my tool chain. I think in the long run that's my best chance as a solopreneur. So I try to get projects where I can learn new skills and I make contracts which allow me to use the sources I developed afterwards.
And now I mostly hope I manage to learn fast enough to survive. I learned already a lot about negotiating by now, for example that I will always underestimate project time (even if I know it...) and therefore I really need to demand higher rates than I had originally expected.
Also I have some long-term targets for own products. So I'm not just doing blindly projects, but I care that projects always get me closer to that. Originally I had hoped to find time beside the official projects, but that was not the case so far.
Trying to get a new project while still working on the old is also tricky. I learned by now that I need full concentration for the current task. This means delaying everything that has no connection with my current project by all means until I can spend a full day on the other project. And then I will stay on the other until everything that was accumulated is done even if it needs more than the time I planned for it.
About parallel projects for products... I have none of them, but I use development work to learn more and more about difficult subjects that would take a long time of research or study to learn well (for example, on an older project I learned some basics of computer vision, etc). In the end that makes my development time more expensive and useful with every project. But maybe I should think in products too.
If potential customers are banging down your door, and you're worried about not having the time to develop all of their software, then you need to raise your rates. At least some (more likely, most) of your customers will stay, and you'll be able to afford working on just one or two interesting software projects at a time.
There are other downsides to a lack of diversification though, like being less able to drop one of your customers if necessary.
You should also consider sending clients you turn away to another consultant. The idea is that when you're really busy, you send "overflow" customers to him (or her). And the other consultant would ideally return the favor as necessary.
Its a huge challenge to cleanly define areas to hand off, and to trust others with them. But I'm convinced its the key to growth.
I do both and I definitely agree. Not only is it harder, there's more responsibility. You have to make something work. If it doesn't get done, or doesn't work, that's your fault. By contrast, if you tell someone what to do and it doesn't work, you can always say "well, they didn't do it right". Which of course is exactly what does get said. It's a moot point, though, because there isn't really much accountability to begin with, and because people tend to blame themselves and hide failures under the rug.
Edit: There's also a perception gap. Writing code is a lot harder than most people think it is. Ultimately, I think that's one of the deeper reasons to make one's own product and sell it rather than be a hired code-writer.
Maybe not quite as good as having residual income from an actual product, but pretty good just the same.
Thank you for your interesting comments.
http://searchyc.com/%2522single+founder%2522