Cloud Architecture Review

Who this is for

Engineering teams running production workloads on AWS, Google Cloud, or Azure where the platform has grown organically and nobody has stepped back to look at it as a whole. Usually surfaces when the cloud bill stops being explainable, a major outage exposes a structural gap, or an enterprise customer asks for an architecture document you don’t have.

The problem

Most scale-up cloud platforms are the accumulated decisions of three to five engineers working under deadline pressure over several years. Each decision was reasonable at the time. The result is a platform that works but carries hidden tax: overpaid services, single points of failure nobody’s mapped, security posture that won’t survive an audit, and a deployment story that only the original authors fully understand.

A review done right isn’t a rebuild proposal. It’s a clear-eyed snapshot of what you have, what’s at risk, what’s worth fixing now, and what can wait — written so the engineering team agrees with the findings and can act on them without an outside consultant in the room.

What you get

• Current-state architecture map across compute, data, networking, identity, and observability
• Cost analysis with specific, prioritised savings opportunities (typical finding: 15–30% reducible without disruption)
• Reliability posture review — single points of failure, blast-radius analysis, recovery readiness
• Security and compliance gap assessment against your target frameworks (SOC2, ISO27001, IRAP)
• Multi-region, disaster recovery, and data residency review where relevant
• Prioritised remediation roadmap with effort estimates and sequencing
• Written architecture decision record (ADR) template and example for the team going forward
• Read-out session with engineering leadership and, where useful, the board or audit committee

How it works

4–6 weeks
Week 1	discovery, access provisioning, stakeholder interviews
Weeks 2–3	technical deep-dive, cost analysis, architecture mapping
Weeks 4–5	findings synthesis, remediation roadmap, draft report
Week 6	leadership read-out, ADR template, handover

Duration depends on the number of accounts, services in scope, and the depth of the compliance overlay.

Optional people co-engagement

When the review surfaces structural issues that are really team-shaped — unclear platform ownership, missing on-call rotation, no career path for platform engineers — Molly can run a parallel track on the operating model. Scoped separately.