How it works

How a review works, from first conversation to follow-up.

A review runs in a fixed order, and you know the scope and the fee in writing before you commit. Here is each step, what I need from you and what you receive.

Start the conversation Read the FAQ

How it works

Seven steps, one at a time.

1
First conversation
Start by email if you want a written record, or on a call if you prefer. Tell me what you have, what worries you and what decision the review feeds. Anything agreed on a call is confirmed in writing.
2
Scope and fixed fee, in writing
I set out the scope and a fixed fee in writing before you commit. Payment is 50% on engagement and 50% on delivery of the report.
3
Confidentiality and access
We agree confidentiality first: I review and sign your NDA. You then give me read-only access, preferably to a staging environment with seeded data rather than live records. The timescale runs from the day I have the material and confidentiality is agreed.
4
The review
I run the application and test it myself, and I do not delegate the work. I form my own view from the code, the running system and the configuration before discussing design with your developers. If the material is materially bigger or different from what you described, I tell you within the first two days. The longer options include a mid-point check, where I say whether the scope looks lighter or heavier than planned and we agree what to do.
5
The report and a walkthrough call
You receive a written report in plain English, with findings ranked by severity and each one backed by evidence and a recommended fix. A walkthrough call goes through it with you, and I can walk your developer through the fixes.
6
Follow-up
The longer options include 30 days of follow-up questions by email. The longest option also includes a re-check of the critical findings once they are fixed, within 30 days of the report.
7
Optional: stay on as fractional CTO
Fractional CTO work is a separate engagement, offered after the review and only if you ask. It has no bearing on the review.

Scoping

What I will ask you first.

Tier and fee follow from the answers. A rough answer is fine, and if you do not know, say so. I confirm the tier and one fixed figure in writing before you commit.

What does it do, and who uses it?
Who built it, and how: in-house, an agency, a freelancer, or with AI tools?
What decision will the review feed: going live, a funding round, signing it off, taking it over, or whether to continue or rebuild?
What does it handle: personal data, payments, or anything regulated?
Roughly how many parts does it have: applications, services, third-party integrations?
What can I get access to: the code, a staging environment, documentation and someone who can answer setup questions?
When do you need the answer?

What I need from you

What to have ready.

None of this needs to be perfect. If something does not exist, tell me and we work out what to use instead.

A short description of what the software does and what decision the review will feed.
Read access to the code repositories.
A read-only role in the cloud account, and viewer access to the hosting.
A staging environment with seeded data that I can run the application against.
Any architecture documentation, even if it is rough.
Your NDA, for me to review and sign.
Someone who can answer factual questions about how the system is set up.
Material that contains no production personal data.

What you get

What you receive.

A written report in plain English.
Findings ranked by severity, each with the evidence behind it and a recommended fix your developer can act on.
A plain statement of whether to continue, fix first or rebuild.
A walkthrough call to go through the report.
On the longer options, a mid-point check and 30 days of follow-up questions by email.
On the longest option, a re-check of the critical findings once they are fixed, within 30 days of the report.

How long it takes

Typical durations.

The clock starts when I have the material and we have agreed confidentiality.

The shortest option runs for 5 business days.
The middle option runs for 7 to 8 business days.
The longest option runs for 10 to 12 business days.

The options are set out on the code and architecture review page.

Early stop

If the answer is clearly rebuild.

You choose what happens next. You can stop with a short written verdict, with the evidence and an outline of what to keep and what to replace. The 50% paid on engagement covers the work to that point, with no further fee.

Or I can re-scope the remaining days to the rebuild question, covering the approach and what to salvage, at the same fee.

Tell me what you have.

Send a short description by email or arrange a call. Anything agreed on a call is confirmed in writing.

Get in touch

Seven steps, one at a time.

First conversation

Scope and fixed fee, in writing

Confidentiality and access

The review

The report and a walkthrough call

Follow-up

Optional: stay on as fractional CTO