Services
Architecture Review
An independent view of what you have built — and what it will cost you if it breaks.
Internal teams are rarely well-placed to audit their own infrastructure objectively. Context that felt like constraints at the time looks different from outside. The architecture review exists to give you an honest, documented assessment before a dependency becomes an incident, or a cost profile becomes a surprise.
What you get
- Dependency map — A clear diagram of your infrastructure: services, integrations, data flows, and the dependencies between them. Where the single points of failure are. Where a vendor exit would hurt most.
- Risk register — Identified risks ranked by severity and likelihood. Technical debt, vendor lock-in, unpatched surface area, data residency exposure, recovery gaps. Not a generic checklist — specific to your stack.
- Cost profile — An honest accounting of what your infrastructure costs now and how that changes as you grow. Where the per-seat traps are. Where you are paying for capacity you do not use. Where a small architectural change would materially reduce ongoing spend.
- Exit optionality assessment — For each major dependency: what does leaving it cost? What is the exit path? Where are you contractually or technically locked in and is that appropriate?
- Written recommendations — Prioritised, specific, actionable. Not "consider improving your security posture." Which control, why, and what effort it takes.
- Review session — 60 minutes to walk through findings and answer questions.
Process
- 1
Scoping call (30 minutes)
We agree the scope — which parts of the infrastructure are in scope, what documentation already exists, what the review is trying to answer.
- 2
Access and documentation review (1–2 weeks)
We work from architecture diagrams, infrastructure-as-code, contracts, billing data, and direct access where needed. We ask specific questions rather than broad ones.
- 3
Draft report
Delivered for factual review before finalisation.
- 4
Final report and review session
Findings, recommendations, and a clear path forward.
When it is the right fit
You should book a scoping call if:
- You are inheriting infrastructure from a previous technical team and you need an honest picture of what you have taken on before committing to a direction.
- Your infrastructure costs are growing faster than your usage and you cannot explain exactly why.
- You are planning a significant change (a migration, an acquisition integration, a new product line) and you want an independent view of the risk before you commit to the plan.
- You have had an incident and you want to understand whether it was a one-off or a symptom of a structural problem.
Sector relevance
Regulated organisations (healthcare providers, financial services firms, legal practices) frequently need architecture documentation for compliance purposes. An independent review produces documentation that satisfies auditor requirements while also giving the technical team a usable map of what they run. Two outputs from one engagement.
Book a scoping call
30 minutes. No obligation. We will tell you if it is not a fit.
Book a scoping call