Agency plans are for folks building apps for other people, like a development firm building apps for clients. Whenever the developer is ready to transfer ownership to the client, the app will appear under the client’s Bubble account, and the client will be responsible for paying the app plan subscription. Having an app built under an Agency doesn’t change the cost of the app plan in the end for the client.
It sounds like, perhaps, you might want to consider a Team plan instead, which lets you built a Primary app and then create Sub-Apps from it. A sub-app is essentially a clone of the primary, but it’s got its own domain and database. In this scenario, you would be the paying Bubble account for the Team Plan of the Primary and individual plans for each sub-app (they can be lower than Team). So, you’d want to bill your bars accordingly to cover the cost.
If you are building a single product that you want to sell to multiple, un-related bars (i.e. the bars are your customers), then the sub-app route is preferred here.
If bars are hiring you to build an app that they will ultimately take ownership over (they access the back-end, they pay for it, etc.), then you can get yourself an Agency plan to build it and then transfer ownership when it’s done.
The Agency plan allows you to build apps with all the paid features available before placing the app on a plan. The trade-off is the app will have a username/password lock because Bubble wants you to eventually put it on a plan.
Hope that helps. If you want to add in a few more details on the ideal relationship between you / the bar(s) / the app(s), I’m happy to answer more questions.
Gaby at Coaching No Code Apps (formerly Coaching Bubble)
Courses & Products, Tutorials, Private Coaching, and High-level Development
Start Learning Today