Dear enterprises, we're tired of your subscriptions

23 Jan 2024

Shreyas Prakash headshot

Shreyas Prakash

When you build a SaaS app, how do you price it? The first option which comes to everyone’s mind is a monthly/yearly subscription model

While building Clarity notes, I was stuck with a usual question when it comes to building a SaaS—How should I price the app? We settled on the usual monthly/yearly pricing structure. It included a free version to allow users to try out the YouTube note-taking feature as well as a Pro Plan involving all the advanced features not available in the free version. We also tailored an Academic Plan, offering students an affordable option to take notes on YouTube.

We had a successful initial launch on Product Hunt, #3 Product of the day, and later being a finalist in the Golden Kitty Awards.

We had a successful initial launch on Product Hunt, #3 Product of the day, and later being a finalist in the Golden Kitty Awards.

I was not an expert in pricing while launching this app. However, it took me time to explore the various options available for pricing in general. If we take the mythical thirty thousand foot view, no matter what we’re actually doing with pricing, whether it’s a — non profit, retail, SaaS, DTC etc — we’re ultimate in the business of value creation. Price, after all, is the exchange rate on the value we’re creating in the world. In Pricing 101, the monthly subscription plan is just one of the many possibilities to set the pricing. There are multiple such value metrics, such as — per seat per 1000 visits, per CPA, per GB used, per transaction etc.

Circling back to the value metric of a monthly subscription we tried out for Clarity Notes, when viewed in isolation, this case might appear appealing — after all, who wouldn’t be tempted by a service costing less than a cup of coffee a month?

Yet, when considering the broader context of numerous SaaS apps and subscriptions vying for a user’s attention, the allure diminishes. In today’s gig economy, there’s a growing trend towards renting rather than owning everything — from daily news sources like the New Yorker to music playlists on Spotify, and even on-demand video services like Netflix and YouTube.

Most SaaS models come with a monthly/annual subscription plan with an option to try it out for a limited period of time

Most SaaS models come with a monthly/annual subscription plan with an option to try it out for a limited period of time

Sure, there are some costs associated with running software — ranging from customer support, cloud storage etc that could justify the monthly subscription model?

I came across this graph in Lenny’s newsletter which depicts the opportunity cost of not setting the pricing to the right value metric. We’re missing out on revenue by charging just a flat monthly pricing.

If you remember back to your high school or college economics class, the professor put a point on a demand curve for the perfect price and said “the revenue a firm gets is the area under that point.”

The problem here is — what about all that other area under the curve? You’re missing out on that revenue by charging a flat monthly fee. 

37signals rolled out an antidote to SaaS monthly subscriptions models with Once, which is a heretic to what it calls the “Church of Recurring Revenue” by selling software the old fashioned way: pay once and host the software. Just because software isn’t sold in a box doesn’t mean it has to be a subscription. “The post-SaaS era is around the corner,” promises Jason Fried, CEO of 37signals.

SaaS still makes sense for many products, but its grip will slip. Installation and administration used to be hopelessly complicated, but self–hosting tech is simpler now and vastly improved. Plus, IT departments are hungry to run their own IT again, tired of being subservient to Big Tech’s reign clouds — Jason Fried

Enterprises might also be facing various other hidden costs apart from hosting tech and providing customer support. Take this software for example — Audionotes.pro

The wrapper on top of another wrapper on top of another wrapper

The wrapper on top of another wrapper on top of another wrapper

It’s an application helping you take automatic transcriptions of your audio notes. Audionotes is basically a Bubble application made on top of a GPT-4 API helping process and summarise notes better. It’s a wrapper on top of a subscription wrapper (Bubble) on top of another subscription wrapper (GPT4 API). And we pay for all the wrappers together (as a subscription)

In the long term, the users pay the brunt and might churn from opting into these subscriptions. (It’s one big pyramid scheme of subscriptions for the user). We also cannot blame the enterprises as they are also heavily dependent on various other enterprises offered as subscriptions.

Taking these factors into account, I’ve realised that Clarity notes is not just competing with other Youtube note taking apps, it’s also competing with Youtube, Netflix, Spotify etc. All of us are eating into the same monthly salary, piece by piece.

Which makes us think — Are there any alternative pricing models when it comes to SaaS products?

We’re seeing various innovations in SaaS pricing. Let’s look at five different software pricing models that don’t default to a monthly subscription model.

Lifetime deals

Once you purchase and redeem a lifetime deal, you have access to that tool for the lifetime of the product.

This might seem like a great option for users. You pay once and forget about it. The company also can benefit from the immediate capital injection. They are phenomenal for getting early adopters onboarded FAST.

However, growth might slow down when the lifetime deals end. In this regard, monthly subscriptions are considered a more sustainable offer for the enterprises.

Not just that, with lifetime deals, there is also this risk of complacency in updating and adding new features. However, in subscription models, this comes as a part of the package. Indiehackers place their apps in SaaS boutiques such as Appsumo for getting more visibility.

Framer keeps the feature updates visible through their highly active Discord community (Big fan of Benjamin’s community strategy BTW)

Framer keeps the feature updates visible through their highly active Discord community (Big fan of Benjamin’s community strategy BTW)

Lifetime deals + Monthly subscriptions

iA, the popular writing software has a very contrary take on their SaaS pricing. They offer both. They provide the customers and option to either buy or subscribe.

We tried different things before. We tried high prices, mid-range prices, low prices, free, and freemium. Getting Android users to pay for software is not for the feeble-hearted. So far, offering a free basic version with a choice between paid and subscription seems to be the only thing that works. And that doesn’t mean we buy yachts, it means that we might be sustainable in one or two years.

Surprisingly, the revenue share between one-time payments and monthly subscriptions for iA has been a tie—50/50.

Buy Once + Host on your own server

If we circle back on the definition of a lifetime deal — Once you purchase and redeem a lifetime deal, you have access to that tool for the lifetime of the product.

Apart from the quick capital injection, it might not be sustainable for the enterprise as one might still need to pay for the hosting. These marginal costs might creep up over time.

Jason Fried, the CEO of Basecamp has a new spin to the pricing story. Through Once, they plan to provide users the ability to host the software. They just have to pay one-time for the software, and the rest is up to them to host it the way they would like.

Introducing ONCE, a new line of software products from 37signals. Pay one time, own forever. We write the code, you get to see it. We give you the software, you get to host it. Simple and straightforward, not enterprisey and bloated. For one fixed price. Once.

From the landing page of Once

From the landing page of Once

Pay per task

Zapier, a company valued at $5 billion, revolutionized its pricing structure by introducing a “pay-per-task” system, moving away from the traditional monthly subscription model.

Pay-per-task, as an emerging model, reflects a nuanced understanding of customer preferences and a commitment to meeting their specific needs. This shift is likely driven by growing dissatisfaction with monthly subscriptions. Take, for instance, our annual expenditure of approximately $40,000 on Figma. Each monthly bill is a reminder of the disconnect between our usage and the costs incurred.

Alternatives like pay-per-pixel, pay-per-project, or one-time purchases are increasingly becoming more appealing.

Software Couture Houses

Recently came across Andy’s !Boring — an independently owned software couture house.

Under the !Boring umbrella, Andy has launched a suite of apps — WeatherCalculator, and Timer(Not Boring) Habits wildly amplifying a pretty mild-mannered category, tearing down the traditional approach in favor of eye-popping aesthetics, zingy haptics, spiffy 3D animations, and plenty of the delight and fun that nabbed the app its 2022 Apple Design Award.

They are designer-labelled, contrarian, and far from the default. As the title claims to ‘ditch the default, and to support interesting’ —

“It’s about adding something extra,” says Allen. “You can write a to-do list on a piece of paper and it works just the same, right?” If strict practicality is your goal, the app ecosystem is swimming in weather apps and habit trackers, and Allen is the first to admit that (Not Boring) apps aren’t for everyone. “But,” he says with a smile, ”they’re definitely really for some people.” — Apple Developers

How does the pricing work? — You pay for the membership and get access to the entire range of apps that are developed by Andy. It’s more like a SaaS, but instead of paying for one app, you pay for the whole gamut of apps. It’s a bit different from an aggregator such as Appsumo as it’s not a collection of curated applications.

I foresee many such software couture houses.

What’s next?

Historically, we have always taken the stance of function over form, and to just GET THE JOB DONE. However, this very act has backfired in some cases. People don’t just seek utility, but also fun and delight.

I just wanted to conclude this incomplete essay with a quote by Verganti, a pioneer in design-driven innovation—People don’t buy products. People buy meanings.

Dear enterprises, we’re tired of your subscriptions. We seek newer meanings and want to rethink our relationship with software.

It’s nice to see various such relationships emerge, as shown from the earlier examples — ranging from renting, to owning, to renting partially, to owning a suite of apps, to even renting a suite of apps. Software is eating the world. And let’s make sure that it eats the world the right way.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. Life lessons and hot takes from my 30slifestyle
  2. Building a skill for coherent science illustrations
  3. My agentic engineering workflow (step by step)agentic-coding
  4. Every darn thing is a kekulean loop if you notice itdesign-thinking
  5. Hammock driven developmentagentic-coding
  6. Peculiar ways number three fits into our funny little brainsmental-models
  7. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  8. How I write essays in 2026writing
  9. Authority in the guise of evidencecritical-rationalism
  10. Map is not the territoryphilosophy
  11. Self hypnosis as a manifestation ritualmeditation
  12. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  13. How I prepare for tough negotiations nowadaysnegotiation
  14. When should we steelthread somethingproduct-development
  15. Learning and re-learning my mother tongue in Malayalam
  16. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct
  17. Healthy conflict in teams have a tipping pointteam-building
  18. How I deslopify AI writingwriting
  19. How I started building softwares with AI agents being non technicalagentic-coding
  20. Read raw transcriptswriting
  21. Legible and illegible tasks in organisationsproduct
  22. L2 Fat marker sketchesdesign
  23. Writing as moats for humanswriting
  24. Beauty of second degree probesdecision-making
  25. Boundary objects as the new prototypesprototyping
  26. One way door decisionsproduct
  27. Finished softwares should existproduct
  28. How I periodically rank my rough draftsobsidian
  29. Flipping questions on its headinterviewing
  30. Vibe writing maximswriting
  31. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  32. How I build greenfield apps with AI-assisted codingagentic-coding
  33. We have been scammed by the Gaussian distribution clubmathematics
  34. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  35. I was wrong about optimal stoppingmathematics
  36. Thinking like a shipmental-models
  37. Hyperpersonalised N=1 learningeducation
  38. New mediums for humans to complement superintelligenceagentic-coding
  39. Maxims for AI assisted codingagentic-coding
  40. Virtual bookshelvesaesthetics
  41. It's computational everythingtrends
  42. Public gardens, secret routesdigital-garden
  43. Git way of learning to codeagentic-coding
  44. Style Transfer in AI writingagentic-coding
  45. Understanding codebases without using codeagentic-coding
  46. Vibe coding with Cursoragentic-coding
  47. Virtuoso Guide for Personal Memory Systemsmemory
  48. Writing in Future Pastwriting
  49. Publish Originally, Syndicate Elsewhereblogging
  50. Poetic License of Designdesign
  51. Idea in the shower, testing before breakfastsoftware
  52. Technology and regulation have a dance of ice and firetechnology
  53. How I ship "stuff"software
  54. Writing is thinkingwriting
  55. Song of Shapes, Words and Pathscreativity
  56. How do we absorb ideas better?knowledge
  57. Read writers who operatewriting
  58. Brew your ideas lazilyideas
  59. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  60. Compound Interest of Private Noteswriting
  61. Conceptual Compression for LLMsagentic-coding
  62. Meta-analysis for contradictory research findingsdigital-health
  63. Proof of workproduct
  64. Gauging previous work of new joinees to the teamleadership
  65. Task management for product managersproduct
  66. Beauty of Zettelswriting
  67. Stitching React and Rails togetheragentic-coding
  68. Exploring "smart connections" for note takingwriting
  69. Deploying Home Cooked Apps with Railssoftware
  70. Repetitive Copypromptingwriting
  71. Questions to ask every decadejournalling
  72. Balancing work, time and focusproductivity
  73. Hyperlinks are like cashew nutswriting
  74. Brand treatments, Design Systems, Vibesdesign
  75. How to spot human writing on the internetwriting
  76. Can a thought be an algorithm?product
  77. Opportunity Harvestingcareers
  78. How does AI affect UI?design
  79. Everything is a prioritisation problemproduct
  80. How I do product roastsproduct
  81. The Modern Startup Stacksoftware
  82. In-person vision transmissionproduct
  83. How might we help children invent for social good?social-design
  84. The meeting before the meetingmeetings
  85. Design that's so bad it's actually gooddesign
  86. Lessons learnt interview prepping for product rolesinterviewing
  87. Obsessing over personal websitessoftware
  88. English is the hot new programming languagesoftware
  89. Better way to think about conflictsconflict-management
  90. The role of taste in building productsdesign
  91. Dear enterprises, we're tired of your subscriptionssoftware
  92. Products need not be user centereddesign
  93. World's most ancient public health problemsoftware
  94. Pluginisation of Modern Softwaredesign
  95. Let's make every work 'strategic'consulting
  96. Making Nielsen's heuristics more digestibledesign
  97. Startups are a fertile ground for risk takingentrepreneurship
  98. Insights are not just a salad of factsdesign
  99. Minimum Lovable Productproduct
  100. Methods are lifejackets not straight jacketsmethodology
  101. How to arrive at on-brand colours?design
  102. Minto principle for writing memoswriting
  103. Importance of Whytask-management
  104. Quality Ideas Trump Executionsoftware
  105. Why I prefer indie softwareslifestyle
  106. Use code only if no code failscode
  107. Self Marketing
  108. Personal Observation Techniquesdesign
  109. Design is a confusing worddesign
  110. A Primer to Service Design Blueprintsdesign
  111. Rapid Journey Prototypingdesign
  112. Visualise detailed file structures on CLIcli
  113. Do's and Don'ts of User Researchdesign
  114. Design Manifestodesign
  115. Complex project management for productproducts
  116. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  117. Pedagogy of the Uncharted — What for, and Where to?education
  118. Future of Ageing with Mehdi Yacoubiinterviewing
  119. Future of Tacit knowledge with Celeste Volpiinterviewing
  120. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  121. Future of Equity with Ludovick Petersinterviewing
  122. Future of work with Laetitia Vitaudinterviewing
  123. Future of Mental Health with Kavya Raointerviewing
  124. Future of unschooling with Che Vanniinterviewing
  125. How might we prevent acquired infections in hospitals?digital-health
  126. The why to endure any howentrepreneurship
  127. Design education amidst social tribulationsdesign
  128. How might we assist deafblind runners to navigate?social-design