4 ms·
I don't like either of those ideas. Problem is, if you don't have either time nor money to implement the idea yourself, why should a partner/freelancer impleme
by nostrademons 17y ago
I don't like either of those ideas. Problem is, if you don't have either time nor money to implement the idea yourself, why should a partner/freelancer implement it for you and then let you keep the profits?
If I were you, I'd do one of two things:
1. If you really believe in the idea, take a leave of absence from college and pursue it full-time. Build a prototype, put it out there, validate it, and then if it still looks like a good idea, enlist people to help. You'll have a much better bargaining position then anyway.
2. If you don't believe in the idea enough to do #1, put it up for adoption and let someone else run with it. Or just forget about it and let it die.
One of the hard lessons I've learned is that you can't serve two masters. I tried the volunteer-website-with-classes-on-the-side in college, and I tried the startup-on-the-side-with-a-full-time-job afterwards. With the former, I barely managed to graduate, and the website took far longer to do than it should've. With the latter, my job performance suffered and I found the code I wrote for the startup was so bad that I threw it all away and started fresh once I quit. If I come up with another good idea for a startup, the first thing I do (after validating it and making sure it's feasible) is to quit my job and pursue it all the way.