(no title)
filipcte | 15 years ago
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|15 years ago
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.