|
I think there are a few takeaways here: * You have to charge from the very beginning. If you start a free service, and then try to establish a pay system afterward, your users will feel tricked and trapped and they will rebel loudly. Scribd seems to have been in a hurry to get adoption, so they made it free to host documents; as this guy said though, he much preferred hosting with Scribd over doing it manually on his university's web server. That could have been Scribd's value proposition, and a small yearly fee for that probably would have worked OK. * SaaS could get itself in trouble if there are too many incidents like this. I already hear from clients that are concerned about using online services; the most common questions are, "What if they change their terms?", "What if they go away?", and those are legitimate concerns. Many of my clients aren't the most computer-interested people, so if they have concerns like that, then that means that stories like this have penetrated very deep into the consumer market. |
If you lock behind a paywall things previously available for free, sure. And they'll be right too.
An other option is to add features which are only behind a new paywall. Issue then is providing additional services of value and a way for users to discover them.