Bending Spoons' Price Ceiling Experiments

The core insight is that Bending Spoons treats pricing like a product surface that can be rebuilt after an acquisition, not a fixed policy. Once an app is moved onto its shared payments, analytics, and experimentation stack, the team can test many paywalls, plan mixes, and free tier limits quickly, then push prices up until churn starts to outweigh higher ARPU. That is how a mature app with slow user growth can still produce a step change in cash flow.

• This works best on apps with a large installed base and weak monetization discipline. Evernote is a clean example. It kept broad free access for years, then after the acquisition its free plan was tightened to 50 notes, which turns casual usage limits into a direct upgrade prompt.
  1 sacra
• The shared Spoon Engine matters because it lowers the cost of running pricing experiments across many apps. Bending Spoons already has common payments, A/B testing, analytics, and a data lake wired in, so a team does not need to build a custom billing and experimentation stack inside each acquired product before testing higher prices.
  1 sacra 2 sacra
• The closest comparables are software consolidators like Constellation, Vista, and Thoma Bravo, but Bending Spoons applies the playbook to consumer subscriptions where price changes can be shipped in the app and measured in days. In note taking, that also means testing against substitutes like Notion, OneNote, and Apple Notes, where users can leave if the price jump outruns product improvement.
  1 sacra

Going forward, the model points toward tighter paywalls, more segmented plans, and cross app bundles that raise revenue per user without needing breakout user growth. As more acquired products run on the same infrastructure, Bending Spoons should get faster at finding each app's price ceiling and more systematic about turning neglected consumer software into high margin subscription businesses.