Independent audit before you scale: a second opinion that's actually independent.
Two to three weeks. A senior architect reviews your system, finds the cracks before they cost you. Honest, actionable, no upsell.
Why this engagement exists.
Architecture reviews from your potential build vendor are not really independent: there's always an implementation upsell at the end. We do reviews as a standalone engagement, scoped and priced on its own, with no follow-on proposal baked into the deliverable. The report is the deliverable, and we do not pitch implementation unless you ask. Most clients walk away with a roadmap they can take to any vendor.
Deliverables, not promises.
Every engagement ships these artefacts. Nothing here is fluff. Each item is something your team will hold in their hands at the end.
Architecture diagram
Current-state diagram of the system as it actually is, not as it was documented to be.
Risk register
Scale, security, reliability, dev-velocity risks ranked with rationale.
Improvement roadmap
Prioritised by effort × impact, with rough sizing and dependency mapping.
ADRs
Decision records for the major architectural choices we recommend you formalise.
Final presentation
Walkthrough presentation for the engineering team + a shorter exec summary for stakeholders.
Implementation support
Optional. Most clients take the report to their own team. We can help if you want.
The process, step by step.
No mystery, no consultant theatre. This is how the work actually flows from kickoff to handover.
- Step 1
Code + infra read
Read-only access, one engineer-week of reading. We see the actual system, not the wiki.
- Step 2
Interviews
Founding engineers, current leads, on-call rotation. Different views surface different cracks.
- Step 3
Diagnostic write-up
First draft of findings. Architecture diagram. Risk register.
- Step 4
Prioritisation workshop
Stakeholders in the room ranking the risks together. The risk-register isn't a one-way doc.
- Step 5
Final report + presentation
Final report + walkthrough. Engineering team gets the long version; execs get the summary.
Our team has reviewed systems at serious scale: high-traffic consumer platforms, behavioral health platforms handling PHI, and pre-Series A products that needed an honest read before the next raise. The report stays the same in scope; the conversation around it scales.
The questions that actually come up.
No. The review is scoped and priced as a standalone engagement; there is no follow-on proposal in the deliverable. If we are a genuinely good fit to implement, we will say so plainly when you ask, but the report is the product.
Related services
All servicesAI Strategy & Roadmap
A 4-6 week engagement that takes you from "we should do AI" to a roadmap, an architecture, and a team plan you can defend in the next board meeting.
Architecture & Performance
When the product outgrows the architecture, we re-platform without re-writing. Pure performance work or full architecture redesign, sized to the actual bottleneck.
Discovery Workshop
A two-week sprint that takes "we should build something" into a fully-scoped project with budget, timeline, and a definition of done.
Ready to scope Architecture Review?
A 30-minute call. We map your situation against the engagement, give you a real estimate, and tell you honestly whether we are the right team for this.