Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



In 2006, venture capitalist Fred Wilson wrote a blog post describing his favourite business model: “Give your service away for free, possibly ad supported but maybe not, acquire a lot of customers very efficiently through word of mouth, referral networks, organic search marketing, etc., then offer premium priced value added services or an enhanced version of your service to your customer base.” He ended his post by saying that he didn’t know what to call this model and asked his readers for suggestions. He got over 30 responses and e-commerce executive Jarid Lukin suggested the perfect name – freemium (an amalgamation of free and premium) – that’s still used to describe it.
Skype, Dropbox and Evernote are among the many companies that have successfully used this model, but even small businesses and start-ups can use it successfully if their services have the right characteristics. First, you need a high-quality service that potential customers want and need. Second, you need the ability to duplicate and distribute your service digitally. Finally, your service needs the potential to reach a large audience, since only a limited number of customers will purchase something from you.
If your product has these three characteristics, you then need to evaluate the following aspects of your business to determine if you should use a freemium business model.
Your success will depend on your ability to convert free customers to paid customers, so it is essential that you have a clear message that convinces them of the value to do so and makes it easy for them to upgrade.
Evaluate your business plan, and consider using the freemium business model if you think you can attract a large customer base and make them true believers.
Share this
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
Find out everything you need to know in our new uptime monitoring whitepaper 2021