> Flat-fee diagnosis of a Lovable, Bolt or Replit project that stopped moving forward, then a stabilization plan and an honest repair-or-rebuild verdict.

Canonical: https://augustynglowacki.com/services/vibe-coded-rescue/

AI edits that can't break your site.

# Vibe-coded site rescue

This is for a site or app an AI tool built that has stopped moving forward - every new feature breaks something else, nobody on the team can explain what a given file does, and the AI agent that used to help now makes it worse. I diagnose what's actually wrong for a flat fee set in the intake call, before any work starts, and hand you a stabilization plan plus an honest verdict on whether to repair it or rebuild it. Most owners want the first option for reasons that have nothing to do with the numbers, and I say so before I quote either one.

[Get the diagnosis](#lead-form)

## How the diagnosis works

### How do you know this market exists?

Because **it's already documented, loudly, in places that don't sell GEO audits**. Fiverr launched a branded campaign in July 2025 with named services for fixing broken AI-generated projects, targeting Lovable, Bolt and Replit by name. A freelancer told 404 Media he "works with around 15-20 clients regularly, with additional one-off projects throughout the year" ([404 Media, via Slashdot](https://developers.slashdot.org/story/25/09/13/054206/the-software-engineers-paid-to-fix-vibe-coded-messes)). The Hacker News thread "I'm tired of fixing customers' AI generated code" carries 541 points and 330 comments.

### What does the diagnosis actually cover?

I read the codebase, trace what's actually running versus what the file structure implies, and identify the specific failure classes - usually some mix of missing auth checks, no error handling on user input, a database schema that grew ad hoc, and dependencies nobody chose deliberately. I hand you a written stabilization plan. **This is flat-fee: codebase size alone doesn't tell you how broken something is, so I don't price it sight unseen**. A missing design system shows up constantly too - colors, spacing and layout hardcoded per section instead of tokens with roles, so a relaunch means rewriting **fifty-plus sections** by hand, the redesign you'll want in two years, priced into today's architecture. On one project, **one real token** (the brand color) was reused; everything else got hand-propagated, including one layout bug fixed by hand in **sixteen copies**.

### Repair or rebuild - how do you decide?

On the actual state of the code, not on how attached you are to it, though I take the attachment seriously too. "Vibe coding is a bit like DIY plumbing. You can do it yourself a bit and then later when water starts gushing all over your bathroom you hire an emergency plumber at a high fee." Owners resist a rewrite for reasons that are emotional, not economic ([iMagazine, summarizing 404 Media reporting](https://imagazine.pl/2025/09/13/vibe-coding-czyli-programowanie-na-czuja-ai-mialo-zastapic-programistow-a-stworzylo-dla-nich-nowy-rynek-pracy/)). **I name which case yours is, in the stabilization plan, before you spend another dollar either way.**

### What happens after the diagnosis?

You get the stabilization plan and the verdict either way, whether or not you hire me for the next phase. If it's repairable, I fix the specific failure classes I found, in order of what's actually breaking things. **If a rebuild is the honest answer, I say so and scope that separately** - it's frequently faster and cheaper than continuing to patch.

### What if the scope is bigger than one engineer?

Then I say so early. One engineer is the right shape for a marketing site, a rebuild, or a rescue - not for a platform that needs several people shipping in parallel to hit a fixed date. I work at [Bejamas](https://bejamas.com/) day to day, so for that kind of scope I will introduce you there instead of stretching a solo engagement to cover it. **You get the capacity the work actually needs, and I would rather hand the project on than miss your deadline.**

## The process

### You send the repo

What's broken, what an AI tool built, and what's stopped moving forward. One paragraph and read access to the codebase is enough to start.

### You get a flat fee after the intake call

Codebase size alone doesn't tell you how broken something is, so the fee is set once I've actually looked, not sight unseen.

### You get the plan and the verdict

A written stabilization plan and an honest repair-or-rebuild call, whether or not you hire me for what comes next.

## Get the diagnosis

Contact form on this page: name, email, and what you need. [Get the diagnosis](#lead-form).