> If I don't understant the business model and how much I could be locked-in, I don't even bother wasting 1 minute on the product
Personally I do it the other way around, first I try it out and see if it's useful, then I'd figure out if I'm willing to accept the tradeoffs of pricing/lock-in.
If you do it the way you suggest, wouldn't that mean you can't actually understand if the business model is fine because of the benefits you get? Seems backwards to me.
100% agree. Why even question the business model if that's not a product that I would use. First should be "Can I use it?"(meaning does it run on my devices etc.), then "Do I find it useful?" before anything else.
If I know the price is something I'd be willing to pay for a thing that is useful, I evaluate as such. If I know that it's a price I'd never pay, I still want to see what it is and try it because I'm curious. Don't hide information from me.
Example: enterprise licenses that are meant for a huge org rather than an individual let me know that I shouldn't get excited about a tool because it's not for me. Happens a lot because I'm very into networking and automation.
Personally I do it the other way around, first I try it out and see if it's useful, then I'd figure out if I'm willing to accept the tradeoffs of pricing/lock-in.
If you do it the way you suggest, wouldn't that mean you can't actually understand if the business model is fine because of the benefits you get? Seems backwards to me.