Technical audit
An honest review of your website or application: what's fine, what's a risk and what to do about it.
- Review
- Risks
- Speed
- Report
- Arrangement
- One-off commission
- Indicative timeframe
- 1 – 2 weeks
- Billing
- A single payment
- Ideal for
- Before investing or changing supplier
What's included
In the price
State of play
How it's built, with what, and what condition it's in today.
Speed analysis
How long it takes to load and exactly what's slowing it down.
Risk detection
What could break, what's out of date and what leaves you exposed.
Report with priorities
Ordered by real urgency, not by what suits me to sell.
What isn't
Quoted separately
Fixing what I find
The audit diagnoses. Carrying out the fixes is another commission.
Legal audit
I don't cover regulatory compliance or data protection; that's for a lawyer.
Penetration testing
I review the obvious, but a deep security audit is a different speciality.
What you take away
01
Full report
What I reviewed, what I found and what it means, in plain language.
02
Action plan
What to fix first, what can wait and roughly what each thing costs.
03
Review meeting
An hour to walk you through the findings and answer questions.
How it works
- 01Day 1
Access and context
You give me access and tell me the story of the project: who built it and what worries you.
- 02Days 2 – 6
Review
I analyse its state, its speed, basic security and how it's built.
- 03Days 7 – 9
Report
I write up the findings ordered by severity, with an estimated cost to fix each.
- 04Final day
Presentation
I explain it live, without jargon, and we clear up any questions.
Price and terms
It's a self-contained commission: you pay for the analysis and its conclusions, not for whatever comes next. If you decide to carry on with me, what you paid here is taken into account when quoting the project.
Price
Fixed
A single payment
Agreed before we start and it doesn't move. No extra hours, no unexpected extensions.
If you carry on
It counts
It counts towards the project
If you commission the build afterwards, what you paid here is taken into account in the quote.
If you don't
Yours
The report is yours anyway
You can take it to another supplier. It's written so anyone can act on it.
Common questions
I'm going to tell you the truth about the technical state, without dressing it up or being harsh. If the work is well done, I'll say that too — it happens more than you'd think.
The more access, the deeper the review. Read-only access to the code and the server is usually enough.
No. The value of this is precisely that the conclusion doesn't depend on you hiring me. If the best thing for you is to do nothing, I'll say so.
Yes, it's written for that. Any professional should be able to work from it without starting from scratch.
Not sure what state your site is in?
I'll review it and tell you what you really have, what the risks are and what I'd do in your place.