Technical audit for your codebase and infrastructure
A technical audit is a two-week, fixed-scope deep-read of your codebase, infrastructure, and team practices that produces a prioritised list of risks and fixes — so you know exactly what's slowing you down and what to do about it.
What's in the report
You get a written, prioritised assessment, not a vague verdict: architecture and code quality, security and data-protection gaps, infrastructure and deployment risks, test coverage, and the team practices behind them. Every finding is ranked by impact and effort, with a concrete recommendation — the difference between 'your code has issues' and 'here are the five things to fix first, in order, and why.'
When to get one
Before you acquire or invest in a product and need technical due diligence; when velocity has quietly collapsed and nobody can say why; before a rewrite, so you don't throw away what works; or when a previous team left and you've inherited a codebase you don't trust. An audit is the cheapest way to find out what you're actually dealing with.
How it runs
Two weeks, fixed fee, fixed scope. I read the code, the infra, and the history, talk to the people who built it, and reproduce the problems that matter. You get the report and a walkthrough call — and if you want the fixes implemented, the audit rolls naturally into a build or fractional-CTO engagement.
What you get
- A prioritised, written risk register — ranked by impact and effort
- Architecture, security, infrastructure, and test-coverage review
- GDPR / data-protection gap check
- A walkthrough call to talk through the findings
- A clear, ordered remediation plan you can hand to any team
Fixed fee, confirmed in writing after the intro call
- Two weeks, fixed scope
- Written risk register, ranked by impact and effort
- Ordered remediation plan any team can execute
- Walkthrough call with you and your team
- Work under NDA on request
Technical Audit — questions
What is a technical audit and what's in the report?
A technical audit is a two-week, fixed-scope review of your codebase, infrastructure, and team practices. The report is a prioritised risk register — architecture, security, GDPR, infra, and test gaps — each finding ranked by impact and effort with a concrete recommended fix.
How long does an audit take and what does it cost?
Two weeks, fixed scope, fixed fee. The price is in the Pricing box on this page and it doesn't move once the scope is agreed. You get the report plus a walkthrough call, and if you want the findings implemented the audit can roll into a build or a fractional-CTO retainer.
Can the audit cover GDPR and EU data residency?
Yes. Data-protection and GDPR gaps are part of every audit, and recommendations include EU-resident hosting and architecture changes where data residency matters.
Related work
Let's talk about what you need.
A 30-minute intro call, a written scope, and a concrete number — no surprises. I reply within 48 hours.