Real-world stories that can show you how -- and when -- to start charging for your Web service. Without starting a riot.
On the Web, services such as Google, Facebook, and Twitter are the undisputed kings of free, providing robust services at no charge to users. But a host of other companies use free in a much more traditional way -- as an enticement for paid upgrades. The model is known as "freemium," and while it may not make headlines, proponents say it can make millions.
Unfortunately, finding the right balance between free and paid in the freemium model can leave a new business in uncharted waters, with few hard and fast rules to follow. Here, three entrepreneurs using the freemium model with services in different stages of development explain how it's being implemented in their businesses, and how it might be implemented in yours as well.
Don't Miss: Another Take On Freemium -- From LogMeIn
Set Expectations From The Beginning
If paid Web services have an evangelist, it may very well be Jason Fried, partner at 37signals, a Web-based software company that offers a suite of online applications. Basecamp, the company's flagship product, helps companies of all sizes collaborate on projects with their clients through a simple but powerful Web interface. The privately held company is tight-lipped about revenue, but with more than 3 million user accounts in Basecamp alone, Fried says that both revenue and profit are in "the multi-million dollar area."
As for when a Web service should start charging, Fried's answer is simple: immediately. Charging from the outset tells users that the product has a specific value, Fried says. Trying to charge for something that was previously free can undermine the product's value, causing potential customers to ask why the service is suddenly worth more than it was in the past.
"My feeling is that you should begin charging right from the start... The longer something is free, the less it's worth," he says.
Chris Nagele, principal at Wildbit, offers a slightly different perspective. Starting as a free service can work, he says, if the addition of paid plans is done correctly. His company's flagship product, Beanstalk, a version control service that helps software developers and designers track and save changes to a project, launched with only a free plan, but that free plan came with the understanding that paid plans would soon be available.
When the paid plans launched, the free plan was left unchanged. The new plans simply offered more features for a monthly fee. Adding a price only works if you're adding value as well, Nagele says.
Scratch Your Own Itch To Find A Compelling Product When creating a service that users will pay for, the best source of inspiration is often to solve your own problem, according to Fried.
37signals began as a Web design firm, but in working with clients Fried and his partners became frustrated with existing project management software. They developed Basecamp for their own use before offering it to the public in 2004. As a result, the company stopped doing contract work a year later. It now devotes 100% of its efforts to developing and supporting its own applications.
"We consider ourselves the target, and then we go out and find other people who are exactly like us," he says.
Sachin Agarwal, CEO of Posterous, tells a similar story. He and his co-founder, Garry Tan, wanted an easy to use, premium blogging platform for their own use. The result was a service in which creating (or updating) a blog is as simple as sending an e-mail. (Try it by e-mailing post@posterous.com.) Attachments of almost any kind -- images, videos, audio -- are automatically converted and posted along with any text.
The 15-month-old startup has yet to generate revenue, but plans to introduce paid features to complement its free offerings, Agarwal says.
Find The Natural Break Points
Unfortunately, creating the product is often the easy part, at least for those companies that already possess adequate technical talent. Splitting a product into free and paid tiers that provide sufficient value to users while turning a profit -- creating a sustainable business, in other words -- is more difficult, and sometimes comes down to trial and error.
At 37signals, Fried says, he and his partners look for the natural "break points" in a product, and create tiers accordingly. Basecamp, for instance, specializes in project management, so each paid plan is distinguished by the number of projects it allows a user to create. The free plan limits users to one project. The Basic plan, at $24 per month, increases that limit to 15 projects, and so on.
"The best advice I can give regarding pricing is this: Have a price. Don't be afraid to charge for your work. And make it a number you'd pay yourself," he says.
With Beanstalk, plans are differentiated by the number of storage repositories that users can create, and the amount of overall storage space available to them. The free plan limits users to one repository with 100 megabytes of total storage, while the first paid plan ups that to 10 repositories with 3GB of total storage for $15 per month.
Beanstalk's paid plans are further separated from the free plan by the ability to deploy completed software to production servers, and the use of encryption for greater security. The latter two features have been the most common reasons users cite when upgrading, Nagele says.
The company did quite a bit of research into prices at other services and did its best to estimate potential costs when creating its price structure, but in the end, some of those decisions were simply educated guesses, Nagele says.
"There's no real how to for it, because there's so many conditions," he says.
Posterous plans to charge only for those advanced features needed by businesses and the most technically advanced users, and for storage space greater than that offered in the free plan, according to Agarwal.
Next Page: Understanding Who Will Pay
