Live data from Hacker News

How to make $100k in Open Source by working hard

mikeperham.com

21–30 of 96 posts

Re: How to make $100k in Open Source by working hard

#24
"Making Money in Open Source" can have several meanings. Selling software is just what most people think of when reading the title. I myself can say I made about $150k in Open Source this year. But it wasn't by selling software, it was by doing freelance jobs and consulting that involved free software only. Money wasn't coming in on autopilot, I had to get up every day and go to work at several places. But for me, free software is the reason I live a very comfortable life, doing things I love to do. It just isn't selling software, but everything else around it. I always tell my friends that I am the perfect example that Open Source brings in more than enough money.

Re: How to make $100k in Open Source by working hard

#26
Charging a flat rate ($500) per company is leaving a lot of cash on the table. Have you considered a tiered model based on number of servers in use?

As well as increasing fees from Megacorps, the flipside is you could also offer discounts to non-profits, early startups, and so on, and in exchange for links on their homepage.

Re: How to make $100k in Open Source by working hard

#29
post #12

It's encouraging to hear this can work. Of course that guy was extremely fortunate to be making something everyone was interested in, so it's still a risk (but then again: what isn't?).

You say fortunate, I say foresighted. In any event. I imagine that he started building it to meet his own needs and the growth of revenue now is a happy side-effect.

It's probably always a bit of both, but I'd say that level of success doesn't come without the necessary context (several things have to conspire for it to happen). Anyway, it's an inspiring story!

Re: How to make $100k in Open Source by working hard

#30
post #12

It's encouraging to hear this can work. Of course that guy was extremely fortunate to be making something everyone was interested in, so it's still a risk (but then again: what isn't?).

There was no fortune to it, it was years of OSS work on lots of Ruby projects followed by a realization that existing solutions were terrible and I had the knowledge to make something better. Nothing like years of experience to put you in the right place at the right time.
Post reply on HN