Technical audit & due diligence
Know what you actually have, before you spend more on it.
A senior, independent read of your codebase, architecture and infrastructure, so you decide repair-or-rebuild on facts, not guesses.
12+ years of production experience · Fixed scope · You work directly with me
Sound familiar?
You'll know it's time when…
- You inherited code with little or no documentation and nobody can explain why it works.
- A developer or agency says "it needs a rewrite" and you cannot tell if that is true.
- You are about to commit budget, or buy a business, that depends on this software.
- Releases feel risky and nobody can say what will break.
What changes
What you get, in plain terms.
A clear verdict
Repair, refactor in stages, or rebuild, with the reasoning written down.
A ranked risk list
What is fragile, what is fine, and what to fix first, in plain language.
A budget you can trust
A realistic view of what the work would take, before you sign anything bigger.
Deliverables
What lands in your hands.
- A written assessment of code quality, architecture, and infrastructure risk
- A prioritised list of what is fragile, what is fine, and what to fix first
- A repair-or-rebuild recommendation with a rough scope
How it works
Simple, staged, no surprises.
-
Scope the audit
You tell me what you are deciding. We agree what is in scope and what you will get at the end.
-
Read the system
I go through the code, architecture, infrastructure and deployment setup.
-
Walk you through it
A written report plus a conversation, so every finding makes sense to a non-technical reader.
Best fit
Teams inheriting undocumented code, or deciding whether to repair or rebuild
Probably not for you
Not the right fit if you already know you want a full new build and just need a quote for it. That is a different conversation.
Common questions
Answered straight, before you ask.
Do I need to give you access to everything?
Read access to the code and the environments that matter for the questions you want answered. We agree the exact access when we scope the audit.
Will the audit just tell me to hire you?
No. The report stands on its own, and you are free to take it to another developer or fix things in-house. Sometimes the honest answer is that the system is fine.
I do not know what is wrong, only that something is off. Is that enough?
Yes. That is the most common starting point. Tell me the symptoms and I will shape the audit around them.