David wrote a great post this morning on the 37signals blog titled, How did the web lose faith in charging for stuff? He is still surprised that people believe charging for apps is a somewhat novel idea.I fully agree with this sentiment. We (the greater development community) should be charging for our apps. Here’s one reason.
Using expens’d as an example, let’s see how much it cost to get it going. I worked on it for two solid weeks along with our designer Erika Greco. I’m going to use a standard rate of $150/hour for both design and development. This is a standard rate around Rails shops, and what would be billed if this work was for a client.
Design: 20 hours
Development: 224 hours (14, 16-hour days)
Total Hours: 244 hours
Standard Rate: $150/hr.
Total Investment: $36,600
That’s a significant chunk of change, and that’s just for starters. Keep in mind too that any additional design and development hours are another $150/hour investment each. If this app had required 2 developers, the price practically doubles.
To make that money back, we need to charge for the app. To continue adding features that our users request, we need to charge for the app. To run the site (server costs, support, etc.) we need to charge for the app. That doesn’t mean that we don’t, or won’t offer a free version. However in the long run, to keep adding value, we need to charge for the app.
Other Posts That Might Interest You