Price Sensitivity
I’m a fan of the freemium business model, but it’s rare that I encounter a company that has done a proper analysis of price sensitivity. If you’re going to charge a customer for your service, you need empirical evidence to prove you’ve got the right pricing model.
If you could model your customers’ responses to changes in price via a reliable function (linear or otherwise) then you could use some simple math (stuff you likely saw in high school) to maximize revenue, but that’s very unpractical for real world web services. Instead, I love it when I see a company that has done either A/B testing or a cohort analysis in order to determine the optimal price through iterative testing.
A/B testing is the most statistically clean way to optimize pricing. You have your control, or A, as your current price and then your B, B’, B”, B”’ etc are the various other price points you want to test. You test all these prices at the same time live on your site, and after the end of some period of reasonable churn, you can conclude which price point is optimal based on the amount of relative revenue earned from the group.
The drawbacks of A/B testing are in the details of the implementation. Most A/B testing is implemented by cookies. If a user logs into a computer and is assigned a B” cookie, then they’ll see B” cookie pricing on the site. If you give a special deal to B users but not B” users, then one of the B users might blog the special deal and the site will look discontinuous (or buggy) to B” users because not everyone will see the same price at the same time. Side Note: Google employs this method of testing ALL THE TIME (hundreds of A/B test going on at once testing multiple variables), and that’s why sometimes you’ll see a blog post about a new Google feature that you can’t see yourself.
To avoid the inconsistant experiences of A/B testing, you can a cohort analysis instead. In this situation, the control is your current weekly revenue, and then the variables are changes in pricing that are done to the site in sequential weeks. So, if you started doing a cohort analysis at the beginning of February, the users that signed up to pay for your service in the first week of the month would be in the first variable group, and then the users that signed up at a different price in the second week would be the second variable group, and so on… After a reasonable amount of time has passed to allow for churn, you can see which cohort maximized revenue.
The plus side of a cohort analysis is there is no inconsistant experience because everyone is seeing the same pricing at the same time. The downside of a cohort analysis is it introduces an additional variable into your experiment: time. You can’t control for time in a cohort analysis, so if there’s a significant event in the real world (or a big event on your site) that would lead to different behaviors amongst your cohorts, then you have noise in your study. For example, you could never do a cohort analysis around Christmas season because people’s spending decisions fluxuate too much from week-to-week during that time. Similarly, if you were doing a cohort analysis of price sensitivity during Oct 2008, you would have to throw out your experiment because the huge drop in the stock market during those 4 weeks would introduce too much noise into people’s purchasing decisions.
These are my two favorite methods of doing pricing studies, but there are plenty more. I hope that if you’re using a freemium business model you start experimenting with your pricing, because it’s really low-hanging fruit in terms of maximizing revenue. If done properly, you could significantly increase revenue without changing a single feature in your service.