How deep does an architecture or code review go?
I match the depth of the review to the decision you need to make.
Tracing one order through a pricing rule is a different job from reviewing dependencies across five services. We agree on the scope before work starts.
What documentation and access do you need?
For an existing application, I may need the relevant code, architecture notes, and information on storage, builds, tests, and deployment.
For an architecture design, I need the business goals, technical constraints and details of the systems involved.
I’ll tell you exactly what I need before I begin.
Can you review a prototype?
Yes. I can review a prototype’s structure and identify what it needs before people can rely on it.
That includes AI-generated code. I’ll start with the question you need answered, the stack, and the parts of the prototype that matter for the next release.
Take a prototype into production →
Can our own team implement the recommendations?
Yes. I document the findings and walk your developers through the reasoning so they can make the changes themselves.
I can also arrange follow-up sessions, support the implementation, or take on some of the development.
What does a review or architecture design cost?
Cost depends on how much of the system I need to examine, the question I’m answering, and how much evidence I need to answer it.
The people I need to consult and the detail you need in the deliverables also affect the scope.
I confirm the scope with you in advance. I can then give you a quote or work to an agreed budget.