Architecture & Technical Review
Independent architecture reviews, codebase audits and technical second opinions — from a senior engineer who has built software at every scale from solo SaaS to enterprise.
The value
The most expensive decisions in software are architectural. The wrong database choice, the wrong multi-tenancy model, the wrong third-party dependency — these are the decisions that quietly compound into rebuilds, downtime, and the kind of tech debt that sinks product velocity a year later.
A short independent review at the right moment is one of the highest-leverage engagements in software development. A few weeks of a senior engineer's time can save a year of a full team's time downstream.
Engagements
Deep-dive review of a proposed or existing system design. Where are the expensive assumptions? Where are the scale cliffs? What would a senior engineer who's built at this scale before do differently?
A structured walk through your existing codebase producing a clear prioritised list of technical risks, tech debt, security issues and refactor candidates — ranked by real impact, not theoretical purity.
For investors, acquirers or founders: an independent read on the technical health of a target company or product. What are you actually buying?
When an external team or contractor is proposing a significant build, a short independent review can save months. I read their proposal, talk to them, and tell you honestly what I'd change.
Experience
If the review ends with “you actually need this built” — I can do that too via bespoke SaaS development. Or I can hand the findings off to your team or preferred vendor. Either way, the review is independent of any follow-on work.
Common questions
A written report with a prioritised risk register, clear recommendations, and (where appropriate) cost/effort estimates. Usually accompanied by a debrief call with your engineering leadership.
Most reviews take one to three weeks end-to-end. Short, sharp engagements by design — the point is clarity, not filling a consulting calendar.
Yes, standard mutual NDAs are fine. My background includes previously security-cleared financial-services and government work. Additional contractual or security requirements are reviewed before an engagement is agreed.
Yes. Many clients start with a review and follow on with implementation work via one of my other services — that's usually a good sign the engagement went well.
Tell me what you're weighing — I'll reply with a rough scope and timeline for the review.
Working with teams across the US, Canada, UK and Europe
From the resource library
Buyer’s guide · 3 min read
Review an AI-built app before launch: architecture, permissions, data integrity, testing, deployment and recovery. Decide what to keep, repair or rebuild.
Read the guide: Is your AI-built prototype ready for production? A practical review checklist →
Engineering notes · 4 min read
James Drummond explains an approach to AI coding agents built around clear requirements, architecture, human approval, testing and production ownership.
Read the article: How I use AI agents without handing over engineering judgment →
Buyer’s guide · 3 min read
Understand AI-assisted software development: where it saves time, its limitations, and the architecture, testing and human oversight buyers should expect.
Read the guide: AI-assisted software development: benefits, limitations and what buyers should expect →