An architecture review by engineers who ship production AI.
Spot the expensive mistakes before they hit your balance sheet. Fixed fee, fixed scope, named engineers on the day you sign.
Built for teams who want senior eyes before the architecture sets
Four things. Written down. Yours to keep.
Every deliverable is written. Nothing verbal-only. The report stands alone — you can share it with your board or procurement team without us in the room.
Architecture assessment
Written review of current or planned architecture. Covers model selection, orchestration patterns, cost trajectory, governance gaps, and production readiness. Benchmarked against what we've seen fail in production — not against a generic maturity framework.
Prioritised recommendations
What to fix this quarter, what to fix next quarter, what to leave alone. Ranked by impact, not by how much work it creates for us. Each recommendation names the specific risk it closes.
Engineering working sessions
Engineer-to-engineer sessions during the review — not interviews with a consultant and a notepad. We're in your code, your architecture diagrams, your traces. Your team gets to challenge our thinking in real time.
Leadership readout
A 90-minute session with your engineering and technical leadership. Written report delivered before the session, clear enough that a non-technical board member can follow the findings.
From kickoff to written report in two to five days
Minimal time commitment from your team beyond access and the readout session. We work around your schedule.
Kickoff
Access, artefacts, and stakeholder alignment. We confirm what we need to read, who we'll work with, and what success looks like. You get a brief to share internally.
Review
We read your code, architecture diagrams, cost data, and runtime behaviour. Working sessions with the engineering team — collaborative, not interrogative. We flag things as we find them.
Synthesis
Report drafted and reviewed internally before delivery. We synthesise findings into a clear, prioritised document — not a running log of observations.
Readout
Written report delivered before the session. Live Q&A with engineering and technical leadership. We answer the awkward questions in the room, not in a follow-up email.
Fixed fee. Fixed scope. No surprises.
Two engagement sizes. Choose based on the depth of review your situation requires — the output format is the same for both. The engagement is scoped before it starts; you know the deliverables, the timeline, and the cost before you sign anything.
- Architecture assessment
- Prioritised recommendations
- Engineering working sessions
- Written report
- Leadership readout (90 min)
A scoping call is free and takes 30 minutes. No obligation.
- Everything in Standard, plus
- Detailed cost analysis and spend trajectory
- Model-selection benchmarking
- Extended engineering working sessions
- Board-ready report format
A scoping call is free and takes 30 minutes. No obligation.
What this is not
Architecture decisions made in design are cheap. The same decisions revisited six months into production — after you've built around them — are not.
Delivered personally by Richard O'Flynn & George Lovejoy.
Twenty years of shipping bespoke production systems together. No associates, no delivery team.
Ready to get a second opinion?
A 30-minute scoping call is free. We'll confirm whether the review is the right fit, and give you a clear timeline and cost before you commit to anything.
Common questions
Do you sign NDAs before engaging?
Yes, standard. We sign before we see any code, architecture diagrams, or cost data. You can use your form or ours. We don't retain copies of your internal artefacts after the engagement closes.
What access do you need to our systems?
Read access to your codebase, architecture diagrams, and infrastructure configuration. Access to cost and usage data from your model providers and cloud accounts. We don't need write access to anything. If access is restricted, we can work with documentation and walkthroughs — though direct access produces sharper findings.
How long from kickoff to final report?
Two to five working days for the review, plus synthesis before the readout. Standard 2-day reviews typically run across three to four calendar days to allow scheduling. Deep 5-day reviews typically complete within a working week. We agree the schedule during the scoping call.
Who actually conducts the review?
Named partners. The engineers on your SoW are the engineers who show up. No associates, no offshore review team. We name the people doing the work before you sign.
Can we share the report with our board or procurement team?
Yes. The deep review is explicitly written for board and procurement distribution — structured executive summary, clear recommendations with business context, and technical appendix for the engineering team. The standard review can be adapted for board distribution on request.