Ways to start
Production readiness review
Someone reads the system end to end and writes down what is actually true about it.
A written assessment of a system that already exists: authorisation boundaries, data integrity, money paths, failure modes and what happens under load. Increasingly this is a codebase that was largely generated and has never been read end to end.
What is examined
- Authorisation boundaries — every query that returns a list, and what scopes it
- Money paths — what the ledger says after an operation runs twice
- Data integrity — what state a multi-step write leaves behind when step two fails
- Failure modes — timeouts, third-party behaviour, and what the user sees
- Load behaviour — where latency comes from and what queues behind it
What you get
A written assessment, findings ordered by what breaks first rather than by severity label, each with the specific code path it was found in. Yours to act on with us or without us.
Suited to
- A system already live, or close to it
- A codebase largely written by an agent and never reviewed end to end
- A team shipping faster than it can review
- A first enterprise customer asking questions nobody has had to answer yet
Not this
- A greenfield project with no code yet — there is nothing to read
- A prototype intended to be thrown away
Ways to start
The other doors.
Fixed scope
Compliance readiness assessment
What a reviewer will ask for, what you can already answer, and what you cannot.
Project
Build
The system, with the parts that are expensive to add later included from the first release.
Monthly
Accountable architect
A named person owns the boundary, and is still there in eighteen months when it breaks.