Ask YC: Are you working on your startup/side-project strictly in your spare time?
If so, what keeps you from working on the startup full-time? Obviously there are many reasons people don't make the leap.
1. Personal reasons / family obligations
2. Can't afford to lose the salary (could tie into 1)
3. You enjoy your day job.
4. You don't think you're capable or have enough experience.
5. You're waiting for that "killer idea".
6. You have the idea you want to go with but you're waiting for some semblance of success ("We have x # of users now, I think we're on to something...")
7. You haven't found the right people to work with.
(EDIT) 8. You're not doing it for the money. You want to build something cool for yourself, your friends, etc.
I'm sure there are many more reasons. What is yours?
54 comments
[ 3.5 ms ] story [ 89.8 ms ] threadSo nights, weekends, lunchbreaks, etc, I'm writing and hacking away...
There's certainly nothing wrong with taking the safer route when you have a family to provide for.
So what you do is file your new business paperwork with the state, and then buy an HR contract with one of these companies. I think the largest one is Administaff, but my company recently switched from them to another one called TriNet, which is supposed to be cheaper.
I make a decent salary working on a project for the DoD. It's a project that's fairly interesting and to top it off we get to use Rails, which I enjoy using and learning. If I didn't feel like I was getting anything out of the job then I'd probably look to something else.
I don't really feel a sense of urgency to strike it rich yet. I just want to build something cool. For now I'm happy just working at my own pace and trying to maintain a decent work-life balance. I'm in grad school part time and once that's over I'll have more time for my personal projects.
For instance, my current side project is based on my personal interests and probably could not make for a successful business. It's an operating system project and obviously, that space is already taken. However, none of the current operating systems appeal to my technical aesthetics, so I decided to start my own.
I'd still develop software as a hobby even if there was no money in it.
The main reason for the delay is that I need to regain my technical edge. I've been a manager for 7+ years and am not at the level I once was.
I'm also playing around with some ideas. If I end up with something interesting, then I will launch the start up earlier.
I'm starting to learn Ruby/Ruby on Rails on my train commute. I'm doing this to broaden my skill set (specialize in Java for my job). It's slow going at times and sometimes I only do 15 minutes a day.
A major project at work has (almost) come to an end (1.0). And I'm worried about the inevitable screeching-to-a-halt (from overtime busy to idle bored). As a result, a few of us at work are thinking of pitching a Ruby on Rails project to key decision makers (it would be perfect for the application in mind). I'm almost convinced I'll need to build the prototype on weekends (but once we have it - it will sell itself - and they'll give us the go ahead). And the best thing is when we successfully sell the prototype, I'll be able to officially use Ruby on Rails on company time..
Of course, I have a small laundry list of projects involving web mashups/integrations that I want to implement (with RoR). Like procrastitron stated, all of them are projects I would use and if other people liked them (side benefit). I had trouble with pointers ten years ago so Objective-C is probably a stretch - I'll throw this iPhone application idea out there - I got a seeming mass text from a friend 'Hey how are you. What are you up to' - iPhone app idea: Group broadcast SMS "mail merge" - Hey <contact name>. I haven't talked to you in <rough time since last talked> What's new?'
If I had a long-term plan... it's trying to diversify my technological skill set. And, I'm constantly trying to diversify my overall portfolio with long-term side projects like Salsa dancing and public speaking (with the aim of getting out of technology [maybe]). I find I learn (about startups, business, and the business of technology) by osmosis just by reading news.YC. I love the news.YC community (8aweek keeps it from being an obsession but I cheat on the weekends).
So I'd say 2+5+6 (+8) is the combination I had. Step (a) took about 2 years, (b) - under a year, (c) - 6 months. Your mileage may obviously vary :)
The harder the idea is to copy, the more time you have for the app to mature. Any new idea needs real-world tweaking, e.g. the actual use of the app may end up being different from what you envisioned, some non-obvious features may be in a high-demand, unforeseen scalability or usability issues may surface, etc. The longer you have to address these issues without worrying about users leaving to the competitor the better.
Writing an actual copycat app is a different game altogether. I don't have an experience with it, but the common sense suggests that it's not worth doing unless there is a large, under-served market segment or all existing solutions really suck. Hoping to bite a piece out of established market with a couple of (flashy) features is not a very smart thing to do.
Who cares if it's easy to copy? Paul Buccheit says he built the first version of Gmail in an afternoon. Digg was famously built in fairly short order. Twitter, Flickr, Facebook-- all would be fairly trivial to clone. Less trivial to scale, obviously but... Feature-wise their V1 releases weren't that complex.
If you want something that you can do in your off hours AND something that isn't easy to copy, I'd say you might have an unreasonably low opinion of hackers around the world. Surely there's nothing you could build in your off hours that a few persistent hackers couldn't clone in a few months of full-time work, is there?
More on the "why should you care" front-- can you name any successful product/company that succeeded cloning someone else's idea? Maybe you can, but it's the exception, not the the rule. Now there ARE examples of companies jumping into the existing marketing and cleaning up by doing BETTER (iPhone, Flickr, etc) - but that's not cloning... That's innovating.
Additionally, you appear to be mostly considering high-profile web apps, which is not exactly the whole software universe. Head to the tucows.com, pick virtually any category and you will see it full of apps that are very similar. On the other end of spectrum, have a look at companies like NetScreen, which effectively grew their business by building cheaper Cisco devices. And this is not a singular example, it's more of a general MO rather.
All in all, I wrote about what worked for me and what worked exceptionally well. This does not imply that it's the only way.
Maybe I'll try again if I convince myself something's good enough to try for. Are you generating $500/day in value piddling around on your MacBook in Ruby? Are you generating orders of magnitude more than that?
I guess also, it's good way to stay in a positive frame of mind. In our first go at running a business, we had no idea what we were doing and after 2-3 years killing ourselves on the startup we ended up broke & depressed. If success breeds success equally failure can breed failure, and after enough time spent with that smell of 'loser' about you, you start to lose the respect of your peers and question your own worth.
It's taken me 2 years to get back on my feet to a point where life is going really well, and I'm enjoying success both in my day job and my startup. Whilst I'd love to quit full time work and focus on the startup (which I may be able to do soon with funding from some of the people I've worked for), having a day job has been great in getting the startup happening. By not relying on it for your living you have more freedom to do it right for the long term, and even if things are tough with the startup, your judgment isn't clouded by panic.
Those that rebound will have undoubtedly learned valuable lessons for their next try. For people in certain situations and certain stages in life, this is too big of a risk. Failure cannot be an option.
After a recent launch buy a certain fruit theme company I have found an excellent if not a killer idea to really start to think about the next steps. I am current gather people but I do have the issue with number 7 and I am not a hacker by YC's definition. I have started to gather resources (potential people) and working on the side project apart form going to school full time (computer engineering).
(in case you don't already know where that link goes, see if can guess before clicking it)
Although I've been live for two weeks and the money has been pretty good! We'll see if it's sustainable.
With the salaries as they are in california, people in high-demand salaried positions don't need a startup to get rich. all you need to do is forgo rampant consumerism and keeping up with the joneses and you'll be a millionaire in about 20 years with a decent investment strategy.
In the meantime there is no shortage of time for side projects, and you get the added bonus of not having to stress about something you truly enjoy doing because you aren't doing it as your main source of income.
I'm not anti-startup, but working for yourself isn't a universal good.
On the other hand, I have a couple of ideas that will be coming out in the next five years, and if I could get the right team and funding together, I would drop everything in a heart beat.
I don't want to turn this into a political discussion (it's one of the reasons I don't go to reddit anymore), but it does make you wonder how many more businesses could get off the ground if we had government-provided healthcare, and people didn't feel stuck at their day-jobs for the health insurance. :/
Let's go Obam.... ok wait, let's not get political :)
other reasons for not working on the start-up full time is that I'm not it will make money, I question my experience, and I am having trouble finding people to partner that have the skills needed including the passion and mindset to work hard and question things, including myself
other reasons for not working on the start-up full time is that I'm not it will make money, I question my experience, and I am having trouble finding people to partner that have the skills needed including the passion and mindset to work hard and question things, including myself
sometimes i wish that people in the US would fund startups here in the philippines. 1USD == 40Pesos. the funding would go a long way here. and in case the startup succeeds, labor is dirt cheap here - people speak english and they have skills.
It's all in your state of mind.
Best of luck.
I went at it full-time for 6 months when I first launched and it didn't fail, I just ran out of money to sustain a salary. That was 18 months ago, I'm still solvent and quitting working at it full-time was probably the best thing to do for the long-term viability. My goal has always been to get going on as little resources as possible so that if it failed, it wouldn't be a huge disaster. So far, so good.
That is, if I liked my day job, I wouldn't be looking for ways to fulfill my family finances by doing something else?
I build startups all day every day, so I'm comfortable with the field. I've got what I think is a good idea and a ton of execution on it so far. I have a small group of testers that (about 20% friends, the rest random strangers) and a desire to make a great product.
There is a great monetary upside potential, but I just don't have the resources at this time to quit and focus 100% on this. Of course, I sleep so very little that I spend at least as many hours "on the side" as I do at my day job, so it might be somewhat moot anyway.
#3 - I'm very committed to the people and project at my regular job and I like things there too much to want to leave.
#4 - my idea will only work with a good web interface. Web gui/design is not where my skills are at the moment.
#8 - this is something I want for myself. there's a chance others may want functionality but I know if I don't get the interface right I'll only confuse people and I'll only get one chance at a first impression.