Dear @emmanuel @josh and team,
Here’s where I need your help (and I wonder if this could ultimately help with your pricing strategy too).
Can we please get a crystal clear understanding of capacity and rate limiting.
While your cost model may be complex with many variables and moving parts, shouldn’t your art be making it simple and understood by your customer base?
For context, I am using scheduled workflows and recurring events. My goals are to understand the capacity my app requires, design and optimize for a certain capacity and feature set (price), and then to plan for scaling in the future.
The questions:
What exactly is a unit?
What does each unit get me?
How does app rate-limiting work?
When my app gets rate-limited what happens next?
If my app gets rate-limited how many units should I add?
When I hit maximum capacity what is the expected behavior of my app?
My experience has been a mixed bag when my app gets rate-limited (which doesn’t seem to be consistent) from workflows disappearing all together, to workflows magically running 24 hours later. I shouldn’t have to guess and test and guess and test, your platform should be able to tell me what to expect!
In simple summary, as a customer I have no idea what’s going on with Bubble compute resources and the variability in performance is my biggest issue in regard to reliability, trust, and ultimately pricing. For me, product/platform/editor features come second to that.
Here’s an equation:
Clear expectations + performant product + simple pricing = happy customers.
Perhaps a bit of a counterintuitive suggestion for a growing tech startup to help you get “there”… SLOW DOWN! You’ve got something great, and in my opinion you can only mess this up!
P.S. - From what I’ve heard, and my experience, you could greatly benefit from spending a lot more time talking directly (in-person and/or by phone) with customers and users.
With Best Regards,
Alex