Great to see a misstep acknowledged, rather than a political non-answer.
For a pricing model to stand on its own, it has to encourage organic growth. Which in bubble’s case would primarily be users like me looking to release a SAAS MVP and then bring it to scale.
The database rows limit is an absolute non-starter for this - given the data needs of any modern business.
From previous posts you have also elaborated on the difficulties Bubble faces in balancing the associated costs into set plans, when all apps vary significantly in their number of users vs data usage vs feature complexity.
So my suggestion is to allow the app owners to strike that balance themselves.
Provide a core feature set based pricing model, plus separate selectable bolt on options for GB storage, user limits.
E.g.
Feature based plans
(With default user limit + storage GB limit)
- Free Features
- $ Standard Features
- $$ Pro Features
Plus
Selected User limit Increases
- $ Additional X monthly users
- $ Additional XX monthly users
Plus
Selected Storage limit Increases
- $ Additional X GB storage
- $$ Additional X GB storage
This would target costs at the apps incurring them, and hopefully meet both Bubbles and app owners individual needs.
Food for thought.
Thanks