2 ms·
The problem with this is: billable hours are what make you money, not working in the product. Juggling those becomes very difficult. I've been following this
by davidw 11y ago
The problem with this is: billable hours are what make you money, not working in the product.
Juggling those becomes very difficult.
I've been following this space for years, and there are no easy answers.
I think the model where the 'secret sauce' is proprietary, and you give away the infrastructure, like, say, Ruby on Rails, seems to work ok. Produces some good open source software and is still an 'easy'/straightforward business model, because you're selling a product.
- icebraining 11y agoThe problem with this is: billable hours are what make you money, not working in the product. The two are not incompatible. Most of our new features are paid for by our clients, some of which we then include into our main product. Maintenance comes from other sources of revenue, though - hosting, for example, since many companies would rather not deal with that, even if they could.