Bubble App Takeover & Audit
Taking over a Bubble app you can’t fully explain
The developer moved on. The app kept growing. Every change is a gamble. I map the whole thing from the export and your walkthrough, audit it, document it — and then get your feature backlog moving again. Sydney-based, working remotely worldwide.
What I can help with
From ‘nobody knows how this works’ to ‘here’s the map, here’s the risk list, here’s what we build next’.
Bubble app takeover
Inherited a Bubble app, or lost the developer who built it? I step in, map the whole thing, and become the person who can safely change it.
Bubble app audit
A full read of your app from the export: privacy rules, exposed backend workflows, autobinding, race conditions, dead workflows, test-vs-live config. Findings ranked, and checked against the running app before I raise the alarm.
Documentation that people actually read
Not a PDF. A linked tree of short pages: data model, roles and access, each workflow in plain English, every page deep-linked into the editor. Your next developer starts on day one, not week three.
Ongoing support & features
Once the app is mapped, new features stop being a gamble. Scoped, built, and validated against the export so you can see exactly what changed and nothing else did.
Security & handover clean-up
Rotating keys that have left the building, closing endpoints that were never meant to be public, and tidying the roles that grew up by accident.
Straight advice on what’s next
Stay on Bubble and invest, add AI to it, or plan a move to code — an honest read on which, based on the app you actually have.
How a takeover runs
The same method every time, because it works — and because it’s what makes the app safe to change.
Export first, opinions second
Every Bubble app exports as a single file describing every page, workflow, field and rule. My tooling reads it in an afternoon, so the audit is grounded in what the app does, not what anyone remembers.
Your walkthrough is the map
An hour or two of you narrating the app is the most valuable input on the whole engagement. It’s the only source that captures why things are the way they are.
Every claim carries a source
Findings cite the export, the walkthrough timestamp or the ticket they came from. Where sources disagree, I write down the disagreement rather than guess.
Nothing changes until it’s mapped
I don’t touch a workflow I can’t explain. Once the app is documented, changes are scoped, built and validated — and you can see the diff.
Working together on an inherited Bubble app
You work with me directly. When something needs a full team, I bring in Momentum — the agency I founded — so you can scale up without starting over. Same person, same standards, more hands when it counts.
One-to-one with me
Freelance or contract — direct and senior.
- A defined build, prototype, integration or advisory piece
- You want one experienced pair of hands close to the work
- Fast and flexible — day-rate or fixed scope
- A direct line to me throughout
- Remote-first, so location is no barrier
Scaling up with my team
When it's bigger, I bring in Momentum — my agency.
- A full team: design, build, marketing and support
- Multiple workstreams running at once
- Ongoing delivery with cover and process
- The same standards, at greater scale
- A smooth step up when you're ready to grow
Selected work & ventures
Frequently asked questions
What do you need from me to start?
Three things: the app export (from Settings in the Bubble editor — and rotate your API keys first, because they’re inside it), a narrated walkthrough recorded in your test version, and whatever documentation exists, untidied: Looms, Jira, Confluence, Figma, Google Docs, Slack threads. Tidying first only delays things.
How long does a takeover take?
Typically two to four weeks from export to a documented, audited app, depending on size. The last one I mapped had two dozen pages and close to two thousand workflows; the static read took an afternoon and the walkthrough review and write-up took the rest.
Can you take over an app you didn’t build?
Yes — that’s most of them. The method doesn’t depend on remembering how it was built; it reads the app as it is today and mines your walkthrough for intent.
Is my data safe with you?
The raw export never enters any shared tool. It’s scanned for keys and personal data, then analysed on a sanitised copy. Walkthrough videos are transcribed locally on my machine and never uploaded. You’ll get the same standard applied to your own handling of the export.
Will you tell me if we should move off Bubble?
If it’s the honest answer, yes — and I’ve done the measurement work on what a move actually costs, including how much of a typical app lives in third-party plugins. Most apps I see should stay on Bubble and be looked after properly. Some shouldn’t. You’ll get a straight read either way.
Do you offer ongoing support after the takeover?
Yes. Most takeovers turn into a standing arrangement: a monthly block of hours for support and small features, with larger features scoped and quoted separately. For bigger rebuilds I can bring in my team at Momentum.
Read more
Taking over a Bubble app nobody fully understands
The full write-up of how I read a Bubble app now: the export, the walkthrough, every other source, the audit, and then features — with the gotchas.
Bubble.io development
New builds, MVPs, integrations and AI features on Bubble, from someone who has shipped and taught it for years.
Got a Bubble app nobody fully understands?
Send me the export, the last few Looms and whatever documentation exists, in whatever state it’s in. Rotate the keys first. I’ll tell you honestly what shape it’s in and what it would take to get it moving.
Tell me about your projectLet's talk about your project
Tell me what you're building or where you're stuck. I'll reply personally, usually within a day.
Thanks for reaching out!
I'll get back to you soon.