Ask HN: Is it OK to charge people for my product?
I have this cool idea, however it would be a stand alone peice of software. I'm worried that if I were to sell it as is, or offer it's use as a service on a website, that developers would balk at this. These days developers are very altruistic, producing amazing free software like rails, django, mongodb, linux, git, etc.
It seems that these days the primary way for startups to make money from tools for developers is to force them to use storage/bandwidth/cpu on the startup's servers, which isn't always necessary. I was curious as to HNs position on selling stand-alone software, particularly if it isn't GUI heavy.
(
10 comments
| 11 points
| on HN
)
There very well might be some folk on HN (or off of it) who will never pay for your software. That's OK. There are more fish in the sea. In particular, many of them work at companies which happily pay money to solve business problems.
Note that "solves business problems" is much much more likely to make money than "cool idea."
GUIs are not a pre-requisite to making money with software. It all depends on who that software is used by and what it does. There exists a particular company which sells 20 line shell scripts for several thousand dollars. The shell scripts control the operation of equipment worth six figures where miscalibration is a Really Big Deal (TM).
But it makes one wonder, why would they give this away for free if they could make money? I agree with the altruism and desire to give for the good of other developers, but i feel like you could do that and make a small profit.
There are a variety of reasons why people might give code away for free even though they could sell it. The most common one is that "they" are megacorporation selling something other than code, and that investments in the OSS are of strategic value to them even if they're non-rivalrous (i.e. we don't need to be the only people using this for this to be worthwhile). Selling software is also a whole lot of work relative to writing software, as you're probably going to discover in short order.
I absolutely agree with this statement. I'm curious, looking at the relative difficulties of selling software vs. selling service (i.e. bandwidth/cpu/storage + features) if I would be better investing my efforts in the latter.
I know it's the bandwagon argument, but I can think of a lot of cool startups offering tools. I can't think of any offering tools offline.
You're selling pain relief. It isn't terribly important whether the pain relief comes in a blue bottle or a red bottle. Your primary challenges are not going to be the bottle. They're going to be a) finding people in pain, b) communicating that you have something which provides pain relief, and c) convincing them to buy it.
There are many, many reasons to prefer being in the business of selling red bottles versus selling blue bottles, but that is a discussion for another day. (For one thing, it is vastly harder to steal red bottles.)
One reason is that you can't usually just flip a switch and sell it: moving from "throw up some stuff on github", even some pretty good, well-maintained stuff, to "sell to people for money" implies a significant step-up in commitment. People who pay for software often expect support, though there are some areas (like Wordpress templates) where that isn't true. Plus, free code on github that's useful will more or less market itself, whereas code you're trying to sell to people for money usually requires effort to sell (unless you get lucky).
Another is that many people with code on github have day jobs in the tech industry, and giving away an evening/weekends project for free is less of a legal minefield than running a tech business on the side of your tech day job.
If you're looking for more concrete answers, please tell us what kind of solution you're working on.
Rails, django, git, etc. were all developed to build something that makes money. 37Signals was building Basecamp when rails was created. Django was for news websites.
Rails isn't why Basecamp makes money. It was just a useful thing that happened to come out of the development of Basecamp.
Build your product. Charge for it. If you happen to build something cool while working on your product and it is NOT core to your business idea, give it away.