Suggestions from Fans of the new Pricing Structure

[keith]

@andrewgassen let me break it down for you:

Here’s how Bubble is marking up outbound API calls (literally one million percent, and actually further):

[New Thread] More context on our changes to pricing - FAQs answered

@rico.trevisan and @casheets123: I am out of zingers with respect to this one. And @tatiana.a, it’s good to see you here. I believe we’ve met in person, have we not? Now, Bubble’s business is Bubble’s business and they can make whatever decisions they want. But a whole bunch of people – smart people, who also happen to be Bubble customers – have pointed out some serious flaws in the new pricing model. @gaimed is one of these. And nobody from Bubble is responding in a realistic way. I was very …

Here’s how Bubble is marking up AWS lambda executions (upwards of 4.7 million percent, more on lower tier plans):

Workflow Units & Plugins

It’s not even that it’s “greedy”. It’s that the markup over the commodity price for the given feature is so large (pretty much between 10,000 and 100,000X) that there’s no room for your own markup over your Bubble costs, if you want to build something that you could possibly monetize. OK, so here’s some info on SSAs: I tested my simplest/most trivial SSA, “Flow State Single SSA” (from List Popper and Friends). This is basically the simplest Bubble lambda that you could build - it takes the inp…

Here’s what I think about that:

Workflow Units & Plugins

Yeppers @ihsanzainal84. Another thing that I find wild is that this (the WU chart) allows us to see exactly what Bubble thinks is a cost component of my app and figure out the approximate (or even exact) markup for certain features, even under the current pricing model. When you look at it this way, apps like my GRUPZ app are apparently wildly profitable under the current model on a pure cost-to-execute model. Obvs, this doesn’t by itself cover things like full-time employees and such, but the…