6 ms·

It's great that you're ready to take the leap in to making profitable side projects. Typically most side-projects fall in to two categories: 1. They never laun

It's great that you're ready to take the leap in to making profitable side projects. Typically most side-projects fall in to two categories: 1. They never launch 2. They never make any money If you can avoid these two pitfalls, you will likely achieve one or more of a) earning; b) learning; c) increasing your 'luck surface area'. So, it's a good opportunity if you can do it. There are plenty of reasons why you wouldn't have launched including: - you kept your idea secret - you tried to do too much - you underestimated the areas that you're not skilled at - you assumed that if you built it they would come - More here: http://www.startupclarity.com/blog/launch-first-product-what-not-to-do/ http://www.startupclarity.com/blog/launch-first-product-what... The reasons for not making any money, or rather not making enough money that you wish to pursue it are multitudinous but include: - you didn't choose a profitable product idea - you underestimated the slow ramp of death: http://businessofsoftware.org/2013/02/gail-goodman-constant-contact-how-to-negotiate-the-long-slow-saas-ramp-of-death/ http://businessofsoftware.org/2013/02/gail-goodman-constant-... - you charged too little - you didn't solve a problem for people who were willing to pay you - More here: http://www.startupclarity.com/blog/find-profitable-product-ideas/ http://www.startupclarity.com/blog/find-profitable-product-i... I hope that helps and Good Luck!

augustflanagan 12y ago
I think this is a great answer that covers the common pitfalls with launching any side-project. I would add another often repeated, but important, point to the list - try to build something that solves a problem you're having. Earlier this year I launched a side-project[1] that has become profitable and is continuing to grow. The impetus for building it was that I was trying to find a good solution to my own problem and wasn't happy with existing solutions. I knew that it was a niche product, but I figured at the very least if I built this I would use it. Before building it I also talked to a couple of friends who said "Oh, yeah, I'd pay you for that." That was enough validation for me to spend a weekend building a basic version with a friend of mine. After that I started using it immediately and had those two friends sign up (and pay). Their feedback, and my own usage, gave me the motivation to keep improving the product. The other thing I would mention is expectations setting. The "build it and they will come" mentality is really hard to overcome when you're excited about your side-project. You figure you will turn it on and people will immediately start signing up. In my case it was several weeks (maybe even closer to two months) before I had a paying customer other than those first two friends. It's easy to be discouraged during that time and completely abandon your project. Have a basic marketing plan, stick with it, and don't set your expectations too high. It will take time. 1 https://cronitor.io https://cronitor.io
- amelius 12y ago
  > try to build something that solves a problem you're having Why not try to build something that solves a problem somebody else is having? They could be your first customer!
  - perlgeek 12y ago
    Because it's so easy to misunderstand a problem. If it's a problem you're having yourself, you'll likely notice pretty quickly when you're solving it in the wrong way (or not all, merely thinking you are solving it).
    - amelius 12y ago
      Good point. But unfortunately, my own problems cannot be solved by mere programming :)
      - infinite8s 12y ago
        There's nothing in your life that couldn't be solved with a bit of automation?
kcurry 12y ago
What a great encapsulation of essential knowledge.
hackerboos 12y ago
I just want to point out that Gail Goodman talk is amazing.

augustflanagan 12y ago

I think this is a great answer that covers the common pitfalls with launching any side-project. I would add another often repeated, but important, point to the list - try to build something that solves a problem you're having. Earlier this year I launched a side-project[1] that has become profitable and is continuing to grow. The impetus for building it was that I was trying to find a good solution to my own problem and wasn't happy with existing solutions. I knew that it was a niche product, but I figured at the very least if I built this I would use it. Before building it I also talked to a couple of friends who said "Oh, yeah, I'd pay you for that." That was enough validation for me to spend a weekend building a basic version with a friend of mine. After that I started using it immediately and had those two friends sign up (and pay). Their feedback, and my own usage, gave me the motivation to keep improving the product. The other thing I would mention is expectations setting. The "build it and they will come" mentality is really hard to overcome when you're excited about your side-project. You figure you will turn it on and people will immediately start signing up. In my case it was several weeks (maybe even closer to two months) before I had a paying customer other than those first two friends. It's easy to be discouraged during that time and completely abandon your project. Have a basic marketing plan, stick with it, and don't set your expectations too high. It will take time. 1 https://cronitor.io https://cronitor.io

amelius 12y ago
> try to build something that solves a problem you're having Why not try to build something that solves a problem somebody else is having? They could be your first customer!
- perlgeek 12y ago
  Because it's so easy to misunderstand a problem. If it's a problem you're having yourself, you'll likely notice pretty quickly when you're solving it in the wrong way (or not all, merely thinking you are solving it).
  - amelius 12y ago
    Good point. But unfortunately, my own problems cannot be solved by mere programming :)
    - infinite8s 12y ago
      There's nothing in your life that couldn't be solved with a bit of automation?

kcurry 12y ago

What a great encapsulation of essential knowledge.

hackerboos 12y ago

I just want to point out that Gail Goodman talk is amazing.