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
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
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
Find out everything you need to know in our new uptime monitoring whitepaper 2021