Technical audit
Know exactly what is wrong with your software in ten days.
A written review of your code, infrastructure, security and roadmap risk. Then a walkthrough call and a fix plan priced as options.
- 10 daysfrom access to report
- Fixedprice, agreed up front
- Yoursto act on with anyone
What we review
Four areas, one honest picture.
Your last developer said it was fine. Your new agency says it needs a rewrite. An investor wants answers by next month. You need someone with no stake in the outcome to read the code and write down what is true.
Code: structure, tests, dependencies and how hard it is to change
Infrastructure: hosting, backups, monitoring and cost
Security: access, secrets, data handling and known vulnerabilities
Roadmap risk: what breaks first as you grow
Access
Day one
You grant read access to the code and the cloud account. We sign your NDA first.
Review
Days two to seven
Senior engineers read the code and the infrastructure. AI helps us cover a large codebase quickly, and a person checks every finding.
Report
Days eight and nine
A written report in plain language, with a technical appendix for your developers.
Walkthrough
Day ten
A call to go through every finding and the fix plan. Bring anyone who should hear it.
Sample report outline
What the report contains.
A one page summary for owners and investors
The risks, ranked by impact and urgency
Code quality, tests and dependencies
Infrastructure, backups, monthly cost, and what breaks first as you grow
Security findings and what to fix first
A fix plan priced as options
Do it yourself, hand it to your team, or have ours do it.
After the audit
When the report says act, we can help.
Rescue and modernization
Rescue and modernizationTake over the app your last developer left, and move it forward.
A straight answer
When an audit is the wrong call.
You want a rubber stamp
We write down what we find. If that is uncomfortable, the report says so anyway.
Nobody can give us access to the code
We cannot review what we cannot read. Sort out access first, and we can help with that.
You already know what is broken
Then skip the report and fix it. Our rescue work starts there.
Investment
From $2.5k, fixed.
You get a fixed price after the call, based on the size of the system.
recommended
Technical audit
from $2.5k fixed
A written review of code, infrastructure, security and roadmap risk, in ten days.
- Written report
- Walkthrough call
- Priced fix plan
- NDA before access
Questions
What owners and investors ask about an audit.
What do you look at?
The code, the infrastructure, security and the risks on your roadmap. We also read the documentation and the release history when they exist.
What access do you need, and will you sign an NDA?
Read access to the code and the cloud account, nothing more. We sign your NDA before we see anything.
What format is the report?
A written document with a one page summary, ranked findings and a priced fix plan. A technical appendix gives your developers the detail.
How long does it take?
Ten working days from access to the walkthrough call. Very large systems may take longer, and we tell you before we start.
What happens after the audit?
The report is yours to act on with anyone. If you want our help, the fix plan already has options and prices.
Can you audit a company we plan to buy or invest in?
Yes. We review the target's software before the deal closes and report to you. The report is written for decision makers, not only engineers.
Next step
Find out what you really have.
Thirty minutes to agree the scope and the price. The audit can start as soon as access is in place.