More and more SaaS companies are experimenting with usage-based pricing instead of the standard seat-based approach. The basic idea is simple, customers pay only for what they use. For the customers, that’s appealing. For the company, the challenge is to determine what features are most valuable for the customer, perhaps to price accordingly. Do you know which features of your product are most valuable to your customers? Do you know how valuable those features are? Can you construct a ranked catalogue of outcomes and values for your product from the customers’ point of view?
Value and the Feature Set
A given SaaS application has a variety of features to offer to customers. How many of them ever get used? What percentage of the feature set is used by the average customer? That question has been around for years and years, and the consistent estimation is that the average user only taps 10% of a product’s power — at best. Power users might go as high as 20%. The rest of those features, (possibly put in at the insistence of the sales department to hopefully close a deal?) remain untouched. What does that mean to a company considering actual usage pricing?
Case Study: The Customer Success Association Website

What did they read? What did they download from the Library? Where did they go afterward — did they click on an outbound link from a page in The Customer Success Directory or a Case Study? I want to know the category of the visitor and what they’re reading as the first step in creating a catalog of outcomes — and values. What can I offer that will bring them back?
Creating and Using the Catalogue of Outcomes and Values

Do you agree? Join us in The Customer Success Forum on LinkedIn for the discussion.




