Architecture counsel
Structural decisions, made deliberately and written down
Architecture is the set of choices that are expensive to reverse. We help you make fewer of them by accident.

Architecture counsel suits teams that are about to design something significant, split a monolith, introduce a new integration layer or choose between platforms. We join for a defined number of days across several weeks, usually working with a lead engineer or technical director and the supplier if there is one.
Our role is to widen the set of options considered, test them against your real constraints (budget, team skills, regulatory environment, expected growth) and record the reasoning so that future engineers understand why things are the way they are. We prefer boring, well-understood technology unless there is a clear reason not to.
What we work on together
Boundaries and responsibilities
Which part of the system owns which data and behaviour, and how parts talk to each other without becoming entangled.
Data movement
Where records originate, how they flow to reporting, finance or partner systems, and how consistency is maintained when something fails halfway.
Build, buy or adopt
An honest comparison of writing a component, buying a product or adopting an open-source option, including long-term running cost and lock-in.
Operational shape
How the design will be deployed, observed, scaled and recovered, considered at design time rather than after launch.
Supplier proposals
Independent reading of an architecture proposed by a vendor or agency, with questions you can put to them.
What you keep afterwards
Decision records. Short documents recording each significant choice, the options considered and the reasons.
A current-state and target-state view. Plain diagrams your team can maintain, not decorative posters.
A sequenced path. The order in which to make changes so the system keeps working throughout.
Planning something structural?
Tell us what is being decided and by when.