bubble maintenance
Someone has to keep it running.
We take over Bubble apps whose original developer has gone, and we run them properly: bugs fixed, billing working, Workload Units under control. Most of these apps should stay on Bubble, and we will say so rather than sell you a migration.
for app owners
What is covered
Bug fixes
Web and mobile, triaged by what is actually costing you users rather than by what is loudest.
Stripe and subscriptions
Plans, proration, failed payments, dunning, and the reporting that tells you whether any of it works.
API integrations
Third-party services, webhooks, and the retry logic that stops a silent failure becoming a support ticket.
Admin dashboards
The internal screens the original build skipped, so your team stops asking you to look things up.
Performance and WU optimisation
Finding which workflows are burning Workload Units and fixing them. On a heavy app this is usually the fastest way to bring the bill down.
Plugin issues
Broken, abandoned or duplicated plugins get replaced, pinned, or removed where they are not earning their keep.
Database restructuring
Data types and privacy rules that grew organically and now make everything slower than it needs to be.
A monthly note
What changed, what it cost in Workload Units, and what we would do next. One page, no meeting required.
terms, stated plainly
Scope discipline is the whole business model
This works because it is small and bounded. Every term below exists so the work stays predictable, for you as much as for us. If any of them is a dealbreaker, that is useful to know now rather than in month three.
Capped hours
A fixed number of hours a month, agreed up front. Unused hours do not roll over and overruns are quoted before they happen. There are no surprise invoices in either direction.
Two-business-day response
Not two hours. If your app needs somebody inside two hours, you need a team on a rota, and we will say so rather than sell you a retainer that cannot deliver it.
Asynchronous by default
Written updates, a shared board, one call a month if you want it. No standups, no Slack presence, no calendar tetris.
No on-call
Nights and weekends are not covered at any price. This is the constraint that makes the rest of it sustainable.
published, not hidden
What it costs
- Light retainer
- €900 / mo
- 10 hours a month. Bug fixes and small changes, Workload Unit monitoring, a monthly note.
- Standard retainer
- €1,700 / mo
- 20 hours a month. Everything above plus feature work and integrations.
- Ad-hoc work
- €90 / hour
- For apps that do not need a retainer. Minimum half a day, scheduled in advance.
- Agency subcontract
- on request
- White-label, under your brand, billed to you. Rate depends on volume and notice.
retainer spots are limited
This is not a scarcity tactic. It is one person’s calendar, and the work only stays predictable while the list is short. When there is no room left this line says so, and what is on offer becomes the audit or an ad-hoc block instead.
for agencies
Overflow maintenance, under your brand
The short version is here. The terms, the signed non-solicit and the rate ceiling have their own page, because the question an agency actually needs answering does not fit in two bullet points.
White-label overflow
We work under your brand, direct with you or direct with your client, whichever you prefer. Your client relationship stays yours and we do not market to them, before, during or after.
15% on migrations passed through
When a client of yours outgrows Bubble and you would rather not do the migration, pass it over. You get 15% of the migration fee and the relationship stays with you.
Including the signed non-solicit, what we will not take on, and the ceiling your rate is priced under.
Not sure it is worth a retainer?
The audit answers that too. It will tell you what the app actually needs, how much of your Bubble bill is avoidable, and whether a retainer is the right shape at all, including when the answer is that it is not.