3 ms·

I think if the product was good enough people would definitely pay for it. I would just need some stats and facts to back up my claim that it's worth it. That w

I think if the product was good enough people would definitely pay for it. I would just need some stats and facts to back up my claim that it's worth it. That would be the hard part. But if I can state "Use this service to reduce support emails by 30%" and have the data to back that up, then that's something people might pay for. If you spend 1 hour a day answering support emails, and you can cut that down to 40 minutes, then you're saving more than 6 hours of work a month. That's worth some money. The tough part is making it good enough to be a time saver.

keefe 17y ago
The reason I made that comment is that from what I see so far, it is rather trivial to implement. There's not a lot of detail in what I saw so far so maybe I am missing something. However, if all you have is a popup or tooltip to a FAQ - the cost to implement that is much, much less than the cost of writing effective documentation for each feature. I think the tough part is putting together some set of features that justifies not only the cost - but also the risk of adding an external dependency. I hate external dependencies, particularly those from unknown players that are not open source.