Engagement models
Short advisory reviews or longer embedded partnerships — it depends on what you need. Scope and fee are agreed before work starts, and if the scope changes we say so before the invoice does.
Advisory review
Best for: A decision that needs an independent read: an architecture you have inherited, a migration you are weighing, an investment you are evaluating.
A bounded assessment with a written answer at the end. Long enough to understand the system properly, short enough that the findings are still current when you act on them.
- Discovery across the systems and the people who run them
- Prioritised written findings with the reasoning shown
- A walkthrough session with your team
- Clear separation of what was measured from what was inferred
Embedded partnership
Best for: Work that has to land, not just be recommended: a modernisation programme, a platform build, an integration layer nobody currently owns.
Working alongside your team for a defined period, with fixed scope and fixed fee. Not a body in a seat — a named set of outcomes with someone accountable for them.
- Architecture and design ownership for the agreed scope
- Implementation support through delivery
- Decision records for the choices that will be questioned later
- Handover built so your team can maintain what was built
Standing advisory
Best for: Leaders who have the decision but not the sounding board — or teams making a run of choices that will be expensive to reverse.
Ongoing counsel for engineering leaders, on a regular cadence. A second opinion from someone who knows your context and has no stake in which way you go.
- Regular sessions on a set rhythm
- Decision records for the choices that matter
- Availability between sessions for questions that cannot wait
Not sure which one fits
That is a reasonable place to start from. Describe the situation and we will tell you which shape it needs — including when the answer is that you do not need us.