How we work
We draw the map, then walk it with you.
Most architecture work fails in the handover between the people who design and the people who build. We avoid that handover: the architects who set the direction stay to help build it, then leave governance your teams can run.
Four steps, one direction
Step 1: Discover
We assess what you run today, what it costs and where it constrains you. Typically a fixed-scope engagement.
Step 2: Architect
We define the target state, the principles and the sequence. Decisions are recorded, so they survive staff changes.
Step 3: Build
Our architects work inside your delivery teams on the hardest parts first.
Step 4: Govern
We leave behind lightweight governance (a tech radar, decision records, review rituals) so the architecture stays current after we step back.
Ways to engage us
Fixed-scope assessment
A short, defined engagement: current state, target state and a sequenced roadmap, with the decisions that need making first. Our standard assessment takes four weeks.
Delivery alongside your teams
Our architects and engineers join your teams to build the hardest parts: landing zones, platforms, integrations, the first AI use case.
Advisory retainer
A senior architect on call for design reviews, decision records and governance, for as many days a month as the work needs.
Embedded architects
Enterprise architects and solution architects placed in your own team on an ongoing basis. They share your rituals and backlog, keep the target architecture current and record decisions as they are made. It fits when architecture needs to be a continuous part of how your teams work, not a periodic review. It starts with a short alignment on scope and ways of working, and either side can end it as the need changes.
Our playbooks
4-Week Architecture Assessment
Discovery, current state, target state and a prioritised roadmap in four weeks.
PlaybookCloud Adoption
Foundations first, then migration waves.
PlaybookInternal Developer Platform Build
From platform backlog to a 12-week adoption programme.
PlaybookEnterprise AI Readiness and Implementation
A phased programme, or 12 weeks to the first production use case.
What happens in week one
The first week is for listening and mapping. By the end of it, we agree which decisions the engagement exists to support.
- Interviews with the people who make the decisions and the people who live with them
- A review of the documentation and diagrams that already exist, however incomplete
- A first map of systems, integrations and owners
- An agreed list of the decisions the engagement has to support
Standards and methods we work with
We use the standards your organisation already knows, and only as much of each as the decisions need. We have no product to sell you.
- TOGAF
- ArchiMate
- C4
- AWS, Azure and Google Cloud Well-Architected frameworks
- FinOps Framework
- ITIL 4
- SAFe 6.0
- Scrum
- MEGA HOPEX
- LeanIX
Set your North Star.
Thirty minutes with an architect: where you are, where your estate is drifting, and the first decision worth making.
Book an architecture callWe reply within 1 business day.