[davidroetzel]

Three approaches come to mind:

1) Sell professional support

This is how most open source software companies make money. This usually includes some horrendous subscription fee and guaranteed SLAs.

I never quite understood, why this works. My only explanation is, that many customers are comfortable with this, because this is what they are used to from buying proprietary software.

2) Sell a hosted version

This is classic SaaS. If you find a way to automate setup of instances of your software and offer this for an attractive price, this could appeal to people who shy away from the cost of running their own server and installing and maintaining the software.

I firmly believe that SaaS and Open Source do not contradict each other, but I only know one example that seems to be successful: http://www.teambox.com

3) Open Core

Sell a paid version of your software that has features not in the open source version. This is generally frowned upon by open source people, and rightfully so. At least you run the risk of destroying the healthy developer community you seem to have.

In your case, I would gather that you have a huge advantage when it comes to choosing the right approach. If you know who owns the hundreds of sites that already run your software then you already know some of your potential customers.

Talk to them and try to find out why they use your software, if they make any revenue of it, what their pain points are (if any) and what they would be willing to pay for.

[runT1ME]

>This is how most open source software companies make money. This usually includes some horrendous subscription fee and guaranteed SLAs. I never quite understood, why this works. My only explanation is, that many customers are comfortable with this, because this is what they are used to from buying proprietary software.

I think Jonathan Schwartz had a decent answer to this question. It was basically that there are two types of customers, the kind with more time than money, and the kind with more money than time. If your company stands to lose thousands of dollars for an hour of downtime, minutes, isn't paying a subscription fee with 24 hour support worth it, even if it's almost never utilized?

Another way to make money is to backport bug fixes to previous versions that customers are on. With companies who have more time than money, this won't bother them, they can compile their own versions and do their own merges of bug fixes. For companies making boatloads of cash, why waste developer effort doing this for a negligible fee?

[filipcte]

Thank you, great insight! I think I'll go ahead and contact existing users and see if there's a business opportunity there.

Regarding the 3 approaches:

1. Support is tough and it's not scalable. Maybe we could make a living out of it, but barely stay afloat.

2. We've actually built a prototype of a hosted version, but when we looked at the numbers (cashflow projections), they didn't look too good. However, it's still the one approach I believe can work.

3. Oh, we did that almost 2 years ago and it was a disaster. We created a premium version, with a few important extra features, and sold licenses. We sold 5 of them in 2 months. Our focus shifted towards the premium version and we neglected the open-source version. The community was angry, we were loosing "karma" and not even earning money.

[noodle]

1) support isn't scalable, but if you're looking to pull yourself out of stagnation, then you shouldn't discount options just because they won't scale well.

2) this is the option that scales the best. how long ago did you look at the numbers? hosting something like this is quite cheap, and this is the option that gives you the most possibilities to monetize with multiple levels of plans.

3) sounds like a management issue to me, not an issue with the concept

edit: i've worked with jobberbase and submitted fixes to it in the past, and i've worked with other job board software. i've seen people drop thousands of dollars on terrible, outdated job board software without even having a full license or support. you have a market if you can just reach it. jobberbase isn't easy to find unless you go digging and know what you're looking for. most people who are looking to host a new job board do not know what they're looking for.