That said, there was a recent blog post about how one HNer dramatically increased his revenue by changing his pricing model. Rather than charge for features, he adopted a few tiers of service, each one targeted at one type of customer's use case.[1] I don't know your exact situation, but that might be worth trying as opposed to configurable add-ons. In general, speaking in the language of use cases resonates with the buyer more, and is more likely to result in a purchase.
Comments
Good data, thanks.
That said, there was a recent blog post about how one HNer dramatically increased his revenue by changing his pricing model. Rather than charge for features, he adopted a few tiers of service, each one targeted at one type of customer's use case.[1] I don't know your exact situation, but that might be worth trying as opposed to configurable add-ons. In general, speaking in the language of use cases resonates with the buyer more, and is more likely to result in a purchase.
[1]: http://www.extendslogic.com/business/what-i-learned-from-inc...