Pricing strategy

Without wanting to get into another conversation about Bubbles recent price increase I am curious about the strategy given that I am about to tackle this with my own app.

As I see it the new pricing structure means a prospective user is unable to quantify what the cost will be. They don’t know what a WU is or how many they will use in their not yet develped app (is 175,000 a lot?).

Since my app cost is directly related to the number of WU’s consumed I’m wondering if I can get away with this sort variable pricing? Why don’t I just pass on the pricing in WU’s? Is this something that the market is likely to accept?



Most people are familiar with paying for things like storage, number of seats, specific features, counts of actions for specific feature oriented actions.

Most people will not understand WFU pricing and likely wouldn’t subscribe to a SaaS that prices in that metric.

Bubble has made it exceptionally more difficult to price our own apps now. You could try to create some averages for actions and extrapolate what that equates to for a more real world oriented pricing structure. Bubbles WFU pricing structure is living in a Bubble, not the real world.


You get a 100k WU for free in a dev environment to figure it out. This is on top of the WUs included in whatever pricing package you choose.

Since pricing is month-to-month, your risk is minimal. Plus, you can throttle workload capacity when you need it and cap spending so you don’t break the bank.

They released some nifty tools recently that easily expose inefficiency in your app making it easier for you to optimize. More tools are on the way for additional refinement.

The reality is that some apps are incredibly complex while others are relatively simple. Bubble’s pricing to its customers, and our pricing to our customers, will reflect individual requirements.

To answer your question, since you’re just starting, you can do it on the cheap.

@boston85719 isn’t new here, @chrismilleratx.

1 Like

I’m aware, but he didn’t address the question. It was more of a rant comparing units of measure. Furthermore, him being a veteran with years of building, likely means that his circumstances vary from the new guy’s, wouldn’t you say?

I don’t think either of you have legs to stand on. Bubble just landed on a pricing model with unlimited scalability that basically replicates the old one. It doesn’t matter how it works.

YES, it’s more expensive than you thought it might be.

@kurt_fireball is still confused.

Things are going to either be cheaper or more expensive (than they anticipated) for them. That is all.

There’s no conflict here. Pricing is what it is. The bigger issue is user base (being selfish for a moment). There’s no significant user base here (needs to be 100-1000x to support an “ecosystem”). As a result, I’m leaving. (Pricing didn’t drive me out. There’s simply not enough clueful clowns to support my efforts. I’d be more worried about that if I were you.) Sorry-not-sorry to be honest about this.



Storage, seats, features etc are all known and the costs can calculated up front. This where I’m getting stuck. If you start new with bubble, nobody can tell you what its going to cost. I don’t know how to price my app as a result. It’s seems I can’t peg what I charge to what it costs me because I won’t know that until after the fact.

It’s very confusing and troubling. I don’t know how to move forward.

1 Like

Where to @keith?

1 Like

Yeah, where to @keith?!!

We’re building a pretty heavy duty enterprise app on Bubble and I’d be so keen to follow you along if there exists a better alternative!!


here my findings of some alternatives more on the low code side than no code (Noodls or Fluetterflow with Firebase or Flutterflow with Supabase)…if you want a new no code solution weweb+xano or backendless added recently the front end feature allowing you to create a full stack app with them …i did not use them yet i just saw couple of video but i think it worth to have a deeper look…also with bubble if you are able to afford the custom tier than you don’t need to worry about WU if i understood right…not 100% sure :v:

1 Like

@ecosistemanocode here is a big thread where bubblers discuss alternatives, so let’s not transform this thread in another one tools discussions :slight_smile:


thanks i could not find it this morning :joy:

I’m curious too.

If you care to, can you elaborate? Where are you needing support? Are those things more of something the community can help you with or more of a Bubble engineering thing?

In any case, you should at least stay until l release my next plugin this coming Monday (I know I said I’d release it this last Monday but I’m really really going to this Monday). I need your scathing review :grinning_face_with_smiling_eyes:

I think what Keith is saying, there’s not enough people around here to use his services (Or, clueful clowns, as he so lovingly put it) to be profitable, at least that’s how I read it.

The bigger issue is user base. There’s no significant user base here (needs to be 100-1000x to support an “ecosystem”). As a result, I’m leaving.

1 Like

That is true, but as you build it, you will come to know what it costs to perform the operations you make available to your users. So, over the course of development and initial release, you should be able to isolate the cost of each operation, and then through following the trend over the release you can get some guesstimate of what it costs per user on average per month.

Pretty much did address every part of the question that I focused on, which was the aspects of would his SaaS be able to get away with the variable pricing as Bubble is. My answer was NO, because of how people are familiar with SaaS pricing.

I did not attempt to get into whether or not 175,000 WFUs is a lot because, yeah, kind of very arbitrary as I have no understanding from the question what his app does and how his users are likely to use it.

I think you may have to think about flipping things on it’s head and likely do what Bubble did in a sense, which is to start out with thinking, how much is the market willing to pay for an app that does X…then set out to build an app that does X and see if you can get an idea of what the average user of the app would utilize it for, and how that may affect the costs of operating on Bubble.

Had you from the beginning thought about using Bubble to run your app indefinitely and scale with Bubble all the way through? Most Bubble users do not, and they build initially, gain some traction and then make decisions about whether or not they can scale on Bubble, and if not, they migrate off platform. I’ve had several clients who went this route, and after only 6 months after launch they reached their MRR targets that validated the platform, then set out to rebuild off Bubble.

What Bubble’s pricing change has done is make it so that maybe more people will be thinking this way from the get go.

One strategy is to start off with the expectation that you will move off platform if after building you see the costs as prohibitive for your app, and begin the project with a separate backend. Since the cost of API calls and Bubble database calls are the same as well as the costs of data return per character, you can build all data functionalities elsewhere without necessarily having a higher variable cost than if you just used Bubble’s backend…the difference though, is that you will have a fixed cost that is higher (the cost of the external database), however, you could save on server side workflows since those would be done in the external database…a lot of people are talking about Xano and Firebase for something like this.

With that strategy, you can then expect if you need to leave Bubble because you run too many workflows on the page, or page loads are killing you, or the amount of data being sent between your external backend and Bubble is so much that Bubble API call costs are killing your app, you just need to migrate the front end, and you would do that while pausing efforts to grow your app user base and launch it with a heavy push to promote new user acquisition.

But in the end, nobody even knows if their app is ever going to have any kind of issues with Bubble pricing strategy killing their applications prospects at success.

I think people just need to determine if Bubble is the tool they want to use for their project and create a strategy around how they will use it, with short term and long term goals understood.

I personally have a 6 month, 12 month and 18 month strategy written down for my personal app that I made only after the new pricing announcement and alterations to the costs. Parts of those plans are to learn a new tool for certain parts of my app, and to isolate heavy abusers of WFUs and figure out how I as the developer can set ways to reduce their overconsumption of my precious WFUs, and as a business owner, ways to extract some value from their heavy consumption of my WFUs.

So, this is an example of the strategy I am taking. Others will have their own strategies. Hope this helps.


Well said! Sadly, this really does position Bubble more of an MVP bulider than a solid long term solution - which of course would be ideal :confused: That’s not a bad thing since people can test ideas out cheaply, but definitely seems like a big missed opportunity if true.

Say it ain’t so, @keith! I’m a better Bubbler because of you, and I’m sure others share the same sentiment. ListShifter alone has enhanced so much of what can be built on here.


I’m really bummed that you are leaving @keith

Thanks for building List Shifter and List Popper – my app wouldn’t have been possible without them!