4 ms·
I can see some problems with your "per-exception" pricing model. If your product works and adds value, it will result in the reduction of exceptions. A reducti
by dclaysmith 15y ago
I can see some problems with your "per-exception" pricing model.
If your product works and adds value, it will result in the reduction of exceptions. A reduction in the number of exceptions will result in web sites requiring a smaller plan. Smaller plans will result in lower revenue. The more useful your app is, the less money you will make (a bit of a generalization but you get the point).
Could you not migrate to page loads? Fire off an event on every page, regardless of whether or not there was an exception?
- rakeshpai 15y agoThanks for the feedback, Clay. I considered that model for a really long time. But there were two problems with it. (a) Actually just handling large amounts of hits wasn't really a huge cost for me, and (b) I don't think the usefulness will reduce for people who actively deploy regularly. If people don't deploy regularly, they'll likely be happy with the free plan anyway. :)
- richardmarr 15y agoCharging per exception also adds a nice synergy to bugfixing.