Built it with Lovable, Bolt or Replit, and now it’s stuck?

• One change took the site offline

  The issue

  You asked the AI for a small change. It rewrote more than you asked for, and now every page shows an error. There’s no earlier copy to go back to, and each attempt to fix it makes things worse.

  The recovery

  Matt gets the site back up first, from the host’s backups if there are any and from what’s left on the server if there aren’t. Then he puts the code under version control with proper backups, so any change can be undone in a minute.

• The secret keys ended up in public

  The issue

  The build needed a key for payments, email or an AI service, and the tool put it straight into the page where anyone can read it. Somebody found it. Now there’s a bill you don’t recognise, or emails going out in your name.

  The recovery

  The exposed keys are cancelled and replaced the same day. Matt moves them to the server where they belong, checks what was done with the old ones, and goes through the rest of the code for anything else left on show.

• It works on your laptop and nowhere else

  The issue

  The app runs perfectly on your own computer. Getting it onto the web, with a real database, a domain and email that actually arrives, is where every guide stops making sense.

  The recovery

  Matt sets up hosting that suits what you’ve built, moves the app and its data across, and leaves you with a simple, repeatable way to publish changes. He explains what lives where, so it stops being a mystery.

• The shop takes orders but loses them

  The issue

  Checkout looks fine and customers are paying. But orders go missing, confirmation emails don’t arrive, or stock never updates, and you’re matching payments to customers by hand.

  The recovery

  Matt traces an order from the button to the bank, fixes the step where the payment provider and the shop stop talking, and reconciles what has already been taken so that no customer is left out of pocket.

• Every fix breaks something else

  The issue

  It was built by the boss over a few weekends, and now the business runs on it. It was quick at the start. Now the code has grown past what the AI can keep track of, each fix undoes the last one, and nobody dares touch it.

  The recovery

  Matt reads the code and maps what it really does. He puts tests around the parts your business depends on, then untangles the rest a piece at a time, so changes become safe again.

• Customer details open to anyone

  The issue

  There’s an admin page with no login, or a database that answers anyone who asks. Nothing has gone wrong yet that you know of, but you can’t be sure.

  The recovery

  Matt locks it down straight away, then checks the records to see whether anyone has been in. You get a plain account of what was exposed, and whether it’s something you need to report.

• “The agent keeps saying run this command”

  The issue

  The tool tells you to set up GitHub, add an environment variable, run something in a terminal, and you’ve no idea where any of that lives.

  The recovery

  Matt sets up the plumbing once: the repository, the hosting, the keys. He explains in plain words what each piece is for. You keep building; the plumbing stays done.

• “It works. I think.”

  The issue

  It looks right and runs without errors, but you can’t tell whether it checks what it should, whether customer data is safe, or what happens when two people use it at once.

  The recovery

  Matt tests it against what you meant it to do, writes down what’s missing in order of risk, and fixes what matters. You get a list you can act on, not a verdict.

• Back online first

  If you’re down, that comes before anything else. Explanations can wait until customers can reach you again.

• Find out what happened

  Matt reads the code and the hosting setup and tells you, in plain English, what went wrong and why.

• Keep what’s worth keeping

  We don’t start again unless starting again is genuinely cheaper. Most rescues are repairs.

• Close the gaps

  Passwords and keys left in the code, admin pages open to anyone, no backups: the things AI tools rarely mention.

• A straight answer

  If it can’t sensibly be saved, you’ll hear that on day one, along with what it would cost to do properly.

• Handed back in working order

  Documented and under version control, so you, or we, can carry on from firm ground.

The first look is free. Most rescues then take a day or more at £350 a day excluding VAT, and you’ll know what it will cost before it starts.