On this page
It is the first question almost everyone asks, and the honest answer is: it depends. But it does not depend on luck. The same few things decide whether a fix takes an afternoon or a month.
What makes a fix small
- The problem is in one place, like logins or one broken feature
- The app uses common tools that many developers know
- You can describe the problem clearly and show how to repeat it
- There is a working version saved somewhere
Settings problems, like a login redirect or a missing environment variable, often take a few hours at most.
What makes a fix bigger
- Security gaps across the whole database
- The same bugs coming back after every change
- Real users and real data that must not be lost during the work
- A move to another backend or platform
A full cleanup of a small app usually takes days to a few weeks of work. A migration off a platform can take longer.
How to keep the cost down
- Stop asking the AI for more fixes on top of a broken state. Each round can make the job bigger.
- Write a clear brief. Our guide on briefing a developer shows what to send.
- Start with a review. A short code or security review tells you what really needs work before you commit to more.
- Fix safety first, polish later.
Fixed price, not open-ended
Whatever the size, insist on a fixed estimate before work starts. Every request sent through Handfixed gets one, free and with no obligation. Describe your app here.
Built by AI?
Fixed by hand.
If your project has the problem this post describes, a specialist can look at it and send a fixed estimate.
Request a repair crewKeep reading
How to brief a developer when your app was built with AI
A good brief gets you a faster, cheaper and more accurate estimate. Here is exactly what to send, even if you do not know the technical words.
Should you fix your AI-built app or start over?
Starting over feels clean. Fixing feels cheaper. The right answer depends on a few things you can check yourself.