Skip to main content

How I Make Money On Free Software by Ted Roche

I figured Ted's comment may have been a little directed at me , from my post a while back about supporting shareware and commercial authors.

He's makes a good point: "I'm in the business of consulting, not value-added resale. " But it doesn't answer the question for those who are in the "get rich or die trying" scheme (you know who you are).

The subscription model is the one I always think about when pondering "free software". We do it at MTI (http://www.mtihorizon.com) with our e-services - give away the tool but charge per transaction. It seems to work but it takes a long time for the "bricks+mortar" type businesses to move to that approach. They are used to selling a product, as opposed to a service.

As far as I'm concerned, it's the one that makes good sense for businesses to consider. All the big box stores (costco) offer "clubs" which are in effect annual subscription services, in exchange for some benefits. Annual maintenance and licensing fees are simply forms of "subscriptions".

Once the service stops being of value, you un-subscribe. What a great way of getting the message across to the vendor: I'll give you money as long as what you have works - when it stops, I stop paying you. Kind of like consulting, I'll give you money as long as what you do gives me value.

No value -> no money : what a concept.

Great post, Ted! - Thanks

Ted's Radio Weblog

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...