Fix or audit an app that is stuck
Broken, half-finished or AI-generated code: find what is wrong, fix it, and make it safe to keep building.
What you get
- A written audit: what works, what is broken, what is risky, in order of priority.
- Fixes for the issues that block you, with tests around them.
- A clear answer on whether to repair or rebuild a part.
- Notes your next developer can follow.
Who it is for
- Founders with an app made by an agency that left, or by an AI tool that got stuck.
- Teams with a demo that breaks when real users arrive.
- Owners who want a second opinion before spending more.
How it works
- Read accessI read the code and run it. Nothing changes yet.
- AuditA written list covering bugs, security gaps, missing tests and risky dependencies.
- Fix in priority orderSmall, reviewable changes, each one explained.
- StabiliseTests on the key flows, a clean build, and a README that matches reality.
A small first step
A fixed-scope audit with a written report. You decide after reading it whether to continue.
Related work
Questions
Can you work on code generated by AI tools?
Yes. It often runs but hides missing validation, weak access control and duplicated logic. Those are the things I look for first.
Will you rewrite everything?
Not unless it is cheaper than repairing. The audit says so, with reasons.
Do you need my production credentials?
No. I work from the code and a staging copy. Keep production secrets to yourself.
What if the original developer is gone?
That is common. I work from the repository and whatever notes exist.
Do you sign an NDA?
Yes, if you need one.