In January 2010 I launched Preceden, a free web-based timeline tool. In May I migrated to a freemium plan, where users could add a certain number of events for free but had to upgrade to the pro plan in order to create more than that. After some experimentation with different limits and prices, I settled on 5 events for free and a one time payment of $30 to upgrade to the pro plan.
In June I started working on jMockups, a web-based high fidelity mockup tool. From June until the beginning of December I hardly touched Preceden. At the beginning of December I started reviewing Preceden’s stats and realized Hey, this is actually bringing in some decent money so I decided to start dedicating some time each week to working on it. (For a more detailed explanation of why I wasn’t watching it closely, read my 2010, 2011, and a $4K/month challenge post.)
Removing the Free Plan
Looking over the revenue figures I wondered: What would happen if I completely removed the free plan? Instead of a user being able to create 5 events for free, new users would have to pay first to use it.
After about three minutes of planning, I decided to go ahead and implement the change.
I wanted to change as little as possible so that the results of the experiment would be accurate. After all, you can’t change several variables at once and then attribute the changes to only one.
That being said, I made a few small changes to the site which may have affected the results.
1) I dropped the price from $30 to $29
2) I changed the background color the header from #112a40 (dark blue) to #244386 (a lighter blue) and reduced its height
3) I made some layout and copy changes on the homepage
4) I removed the reCAPTCHA form from the sign up page
I shouldn’t have made these changes, but at the time I was more focused on the potential increase in revenue than on running a proper experiment.
Before and After Screenshots
Click to view full size:
Sign Up Page
Notice at the top of the new sign up page it indicates what step of the process you are on (1. Create an Account, 2. Checkout, 3. Create Timelines). I also changed the copy on the button from “Create my Account” to “Create Account and Proceed to Checkout”. The wording will come into play later.
(Only present on the pay-first version)
Results and Analysis
- The number of homepage and sign up page visitors was taken from Google Analytics by looking a the number of new visitors to those particular pages.
- Promotions refers to users I upgraded because they are bloggers and bloggers can get upgraded to the pro account for free.
From Nov 1 – Dec 4, 3287 new visitors came to the Preceden homepage, 894 visited the sign up page, 567 created an account, and 22 upgraded to a paid account. That’s a 0.67% conversion rate from new visitor to paid user.
From Dec 6 – Jan 1, 3343 new visitors came to the site, 528 visited the sign up page, 210 created an account (oops), and 5 upgraded to a paid account. That’s a 0.15% conversion rate.
Users who were able to test Preceden before paying were 347% more likely to upgrade to a paid account than those who weren’t.
Also — and this is definitely my fault — 205 people filled out the sign up page and then abandoned the process on the Checkout page. Why? Most people probably didn’t realize they had to pay before using it. Sure, the Pricing page said “$29 for Unlimted Access” without mentioning a free account and Step #2 of the sign up process was called “Checkout”, but overall the copy didn’t clearly indicate that you had to pay before you could use the app.
Another problem is that the site doesn’t include a demo. It includes examples, but nothing the user can create on their own. Adding a demo section so that new users can get that “Oh cool” moment would have gone a long way.
The good news is that about 4% of the people who created an account converted to the paid plan when they were able to test the product first. Even if the pay-first experiment resulted in better figures, I feel more comfortable letting users test the product before paying. I think this depends a lot on your app and your business model, but for a tool like Preceden there’s no reason not to let people try it for free first. Accordingly, I’m switching back to the freemium version starting today.
- If you run a web app and start building a new product, don’t neglect what you’ve already built. Dedicate some time each week to analyzing your key performance indicators and to making small changes — they’ll add up in the long run.
- The best way to test this would have been to run the experiment on a fraction of visitors to the site. For example, show a pay-only version to half of the visitors and a free plan version to the other half.
- Don’t change several variables at once when you run an experiment. Every change you make will affect the results.
- The time of the year matters. Measuring only the number of paid users would be a bad way choice because a lot of the customers are teachers and I don’t imagine a lot are on the market for a new teaching tool in December. Measuring the conversion rates is better, but there still may be a “Oh I’ll wait till after the holidays to pursue this” mentality among some of the visitors, which could have affected the results. Running this experiment simultaneously would have yielded better results.
Over the next few weeks I’m going to experiment with A/B testing and AdWords to see what’s possible. I’m also going to email the 205 people who signed up during this experiment but didn’t pay; I’m sure they’d be interested in trying it out.
Can you think of anything else that might improve the conversion rates? Leave a comment below and I may test it out.
If you enjoyed this post, you should subscribe to the RSS feed for this blog to get future updates. Also, if you’re a web designer or developer I’d love to get your thoughts on jMockups, my new web design startup. Drop me a note at email@example.com or @jmockups on Twitter. Thanks!