You built something real with an AI builder, and now it will not hold together. A fix breaks something else, the assistant keeps proposing the same change, or a feature works on screen and fails when it matters. A human developer reads the code, finds the actual cause and hands the project back so you can keep building. We work from Melbourne for founders and small businesses across Australia.
Send enquiryNot quite what you are after? If the app works and you want it put in front of customers, that is launching a vibe-coded app. If you mainly worry about leaked keys or open data, start with the security check. If you would rather have the site rebuilt in WordPress that you can edit, see how we did it in the Lovable to WordPress case study.
Australian team
Based here, working your hours, not a timezone away
projects delivered
Over 10+ years building and maintaining sites for Australian businesses
One developer, start to finish
The same person every time: no re-explaining your site
Straight answers, on your terms
We only take work we can finish. Ask us anything first: no obligation
The assistant only sees part of the project at a time. Early on that is enough. As the app grows, each new prompt is answered without the full picture, so a change in one place quietly undoes work in another. Re-prompting to repair the damage adds more changes on top of the confusion. The result is the loop most people describe: the same bug fixed, broken and fixed again, with every round making the code harder to read.
Reads the whole thing first. We trace the failing behaviour to the line that causes it instead of patching the symptom, remove the duplicated and contradictory code that earlier prompts left behind, and add a check around the repaired path where it is practical, so the same fault is noticed next time. You get a plain-language note on what was wrong and why, so the next prompt you write is better informed.
Yes, and that is usually the goal. The work is done in your own project and repository, in the style the tool already uses, so you can carry on prompting. Where a tool tends to overwrite a hand-fixed file, we tell you which files to leave alone and how to word prompts that avoid them.
Login that works for the builder but not for new users, forms that save nothing, payments that complete on the provider and never reach your database, data that shows for one account and not another, pages that load slowly because every visit fetches everything, and environment settings that differ between your preview and the live version. Most of these have a single cause once someone looks at the code rather than the screen.
A fixed-quote investigation is $249 AUD. We look at the app, reproduce the problem and tell you what is wrong, what fixing it involves and roughly how long it will take. If you go ahead, the work is billed at $100 an hour, itemised. If the honest answer is that a section should be rewritten rather than patched, the quote says so, with the reasons.
Any that produce code you can export or connect to a repository, including Lovable, Bolt, v0, Cursor, Replit and code drafted in Claude or ChatGPT. If the tool keeps the code locked away, the first step is getting access to it.
We need access to the code and to whichever services the app depends on, such as the database and payment provider. Access is limited to what the fix needs, and it is removed when the work finishes.
Only if patching would cost more than rewriting, and we would say that before any work starts. Most apps need targeted repairs, not a restart.
No. New prompts can still introduce new faults. What we can do is fix the cause of the current ones, leave the code easier to read and tell you what to watch for.
Sometimes it is a setting, a plan limit or a service outage. We check that first because it is the cheapest answer, and we say so if it turns out to be the case.
Tell us what is happening and we will come back with a fixed quote and a timeline, usually within one business day.
Get in touchVibe-coded app now breaking? A developer finds the real cause, repairs it and hands the project back so you can keep building. Melbourne, Australia-wide.
Get in touchEvery CloudyWP project runs the same way, whether it is a one-page site or a store with a thousand SKUs. Here is exactly what happens.
A single scoping call, then a written plan: what gets built, what it costs, and when it ships. No discovery-phase invoices, no moving targets.
48 hrs to your quote
Custom WordPress or Shopify on clean code you own outright. Every build ships fast, passes Core Web Vitals, and is handed over documented.
95/100 average PageSpeed
Your site talks to the tools you already run: CRM, invoicing, email, stock. The repetitive admin stops being someone's job and starts running itself.
15 hrs saved every week
