I’ve run multiple web apps for years now, and over the years they’ve had different pricing models, from completely free to paid-only, with free trial periods of differing lengths.

As web app owners, we all know that one of the best things to do is to just get the first version of your product out of the door so that you can see how the market responds, instead of overanalyzing decisions before they can be tested in real-world conditions and with real customers. But of course, once you get your product out into the market, you should always be keeping an eye on things to see what you can be doing better, and improving on things that are working.

One of the things that I’ve messed up on repeatedly (but am constantly working on) is pricing. When Chris and I launched Are My Sites Up, we had totally free accounts that could check 60 sites at once. We didn’t even do the math about how much it would cost us, or how many sites we could reasonably check from each server… the numbers just sounded right. We immediately had server-crushing “success”, because people signed up like crazy for it, but quickly we realized that we could only afford to offer monitoring of 5 sites for free, and dialed the plans back.

With apps I launched after that, such as Are My Sites Up White Label and the original version of Dispatch, I used the lessons that I learned from launching AMSU to inform my pricing choices. In the case of both, there was no free version at all, only a free trial. My mistake there was not requiring credit cards on the trials, though, so many people would sign up and never convert after the trial period. Some would even sign up, promptly forget that they signed up, then never use the app again.

As a web app developer, it’s nice to see that a bunch of people are signing up for your trials… but it just makes you feel worse later when only 1% of them actually stick around and pay you for your product. What really matters at the end of the day is that you have a product that is helping people to do something more effectively, and that it’s making enough money for you to keep it going and support the users who need your product most. Also, as an independent developer, it’s also very important for me to minimize time spent dealing with users who will never give me money for my product.
I was always afraid to require a credit card on sign-up because I feared that it might cause people to close the browser tab and not bother signing up at all. I’m not afraid of that anymore because I know that now when I see a new signup, it’s someone who is actually actively interested in what I have to sell. Thinking about my own behavior when I see a signup form that requires a credit card: If I am truly interested in the service, but not ready to fully commit to testing it out, I’ll just bookmark it and come back when I’m serious and have time to use it, because I know that there’s a time limit before I need to make a decision, or my card will get charged.

Also, I’d much rather have a situation where I have 50 people who sign up for a trial, and 30-40 of them stick around than one where 300 people who aren’t serious about using the product sign up for the trial, cause a drain on support resources that could be used to help paying customers, and then have only a few of them even stick around after that.

Instead of letting them filter themselves out after trying your product and deciding that it isn’t right for them, let people self-select themselves out of even signing up for your trial by cutting out trials that don’t require a credit card. You won’t regret it. Recent apps that I’ve launched, like Stunning and the latest version of Dispatch have had trials with credit card info required since Day 1, and I’m starting to go back through my older apps and do the same thing. You should too. Learn from my mistakes!