Your developer is gone. How to fix your live app without coding

A freelancer or an agency built your app. It went live, people use it, and then the developer moved on. Now there's a bug on the signup page, a customer is asking for a small change, and nobody is left who knows the code.

You don't have to learn to code, and you don't have to start over. Here's how to get fixes made and shipped again.

Why it feels stuck

• The person who knew the code is gone, and nothing was written down.
• You may not have the logins to the code, the server or the domain.
• A new developer has to learn the app before they can fix anything, and you pay for that.
• Every change feels risky, because nobody can say what it might break.

1. Get the keys before anything else

Make a list of every account the app needs and check you can log in to each one: the code (usually GitHub), the hosting, the domain, the database, email and payments. If the developer still holds any of them, ask now, politely, while they still answer. The code matters most. Once it's in a GitHub account you own, anyone you hire next, a person or an AI agent, can start from it.

2. Write down what the app is for

One short paragraph: who uses it and what it should do for them. Then a few lines on what works today. You know this better than any developer did, and it saves explaining the app from scratch every time.

3. List the fixes as small tasks, worst first

"The app is buggy" is hard to act on. "The Save button on the profile page does nothing on a phone" is easy. Write each problem as one small task you could explain in two sentences, and put the one that hurts customers most at the top. Small tasks are easier to check and easier to undo.

4. Make sure nothing ships untested

The worst outcome is a fix that breaks something else. Each change should pass the app's tests before it goes live. Many apps handed over by an agency have few tests or none, so make adding them one of the first tasks. It makes every fix after it safer.

5. Approve the work, and let agents build it

This is where NimbleHQ comes in. It works on the code in your own repository, so nothing is locked away again. You add your app as a project with the paragraph from step 2, then add the tasks from step 3. AI agents build each one you approve, run the tests and ship it to your live app. If something is unclear, the builder asks you one plain question instead of guessing.

You don't manage a developer or read code. One email each morning tells you what shipped, what's stuck and which ideas are waiting. You decide what gets built; the agents do the building.

Not sure what state your app is in? Ask for a free review and a person will tell you what's wrong and what it would take to fix it.