Software Architecture Services
Four ways to work together. Which one fits depends on whether the system already exists, is still on paper, or needs to move.
All four work the same way: fixed scope against defined deliverables rather than an hourly meter. You keep the written artefacts, and every recommendation comes with the reasoning attached so your team can argue with it. I take on one or two new engagements per quarter alongside my ongoing work.
The four services
Architecture Review
An independent read on the system you already have: what it will and won’t survive, and what to fix first. Two to four weeks, ending in a risk register, a prioritised remediation roadmap and an executive readout.
System Design
End-to-end architecture for a platform you have not built yet. Service boundaries derived from volatility, data and messaging architecture, deployment topology, and the decision records behind each choice.
AWS Migration
The target architecture and the order you move in. A treatment decision per workload, a sequenced plan with rollbacks, and a cost model with its assumptions exposed.
Technical Consultancy
A senior architect on call for the decisions that are expensive to reverse, without hiring one full-time. Priced per month against agreed scope.
Which one do you need?
- The system exists and you’re worried about it → architecture review.
- The system doesn’t exist yet → system design.
- The system exists and needs to be somewhere else → AWS migration.
- You keep making decisions you aren’t sure about → technical consultancy.
- You’re not sure → a discovery call is free, and hearing that you don’t need me is a perfectly good outcome.
Get in touch
Start a conversation, or read more about my background.