Services
Taking over an existing project
Your developer disappeared, or the freelance relationship ended badly, or the codebase just needs someone who can actually read it. I take over Laravel and CodeIgniter projects regularly — it is a normal part of the work, not an emergency-only service. First step is always a fixed-fee code audit: what state it is in, what it would cost to fix versus rebuild, and an honest recommendation either way.
How does a project takeover work?
1. Audit (fixed fee, 2–4 days) — I read the code, check the database structure, look for security issues and note what would need to change. You get a written report either way, even if we don’t continue.
2. Stabilise — fix anything urgent (broken deploys, security holes, silent errors) before adding new features on top of a shaky foundation.
3. Document — so the project is no longer a black box only the previous developer understood.
4. Continue building — new features, on a codebase that is now actually maintainable.
Common questions
Yes, that is the most common version of this request. As long as I can get access to the code and the server, an undocumented project can be read and mapped — it just takes longer than one with good documentation, which the audit fee accounts for.
It depends entirely on the state of the code, and I only know after the audit — that is exactly what the audit answers. I have recommended rebuilds and I have recommended keeping the existing base; I do not default to the more expensive option.
Tell me about your project.
A couple of sentences about the problem is enough. WhatsApp is fastest.