A fixed-scope assessment of a codebase and its architecture - what's sound, what's at risk, and what to do about it, in priority order. One to three weeks, ending in a written report I defend in person.
Three situations bring people to this engagement:
The review is independent by design: no follow-on work is assumed, so the findings have no sales agenda attached.
Agree the questions the review must answer, sign the NDA, and set up read access to code, infrastructure, and documentation.
Code and architecture reading, infrastructure review, and interviews with the engineers who live in the system.
Written report delivered, then a live session to walk the findings and pressure-test the recommendations.
Every review runs under NDA. Access is read-only and scoped to what the review needs; credentials are returned or revoked at the end. Findings go to you and no one else.
Read access to the repository and infrastructure, any existing architecture docs, and a few hours of interview time with the engineers closest to the system. The disruption to delivery is deliberately minimal.
Fixed price, quoted after a scoping conversation - it depends on the size of the system and the questions you need answered. No hourly meter.
It can, but it doesn't have to - the report is written to be executed by your own team or another partner. If you want help executing, that becomes a separate, clearly scoped engagement.
A 30-minute call to define the questions, the system boundary, and the timeline.