Loading
Technology Consulting
We do not resell anything, and we are not certified partners of anyone. That is the point of asking us.
01Why it matters
Some decisions are cheap to change and some are not. Choosing a component library is cheap. Choosing an integration platform, a content infrastructure or a commerce engine is not — and those decisions are usually made under time pressure, on the basis of a vendor demonstration and a reference call arranged by the vendor.
We are engaged to give organisations a second, independent read. That might be an architecture review before a build starts, a supplier evaluation run against your actual requirements rather than a feature matrix, or a technical assessment of a system you have inherited and cannot yet judge.
We also do this work after things have gone wrong. When a programme is late and nobody can say why, an outside team with no stake in the previous decisions can usually establish the position in a fortnight.
02What we do
The work inside the engagement.
- 01
Architecture review
An assessment of a proposed or existing architecture against the load, team size and change rate it will actually face.
- 02
Supplier and platform evaluation
Structured evaluation against your requirements, including total cost over five years and the cost of leaving.
- 03
Technical due diligence
An independent read of a codebase, delivery practice and team capability, written for a non-technical audience.
- 04
Delivery recovery
Establishing the real position of a programme that has lost confidence, and the shortest credible route out of it.
03A typical engagement
One or two senior people, working directly with your technology leadership. Short, intense, and deliberately not a retainer.
- Typical duration
- Two to six weeks
- What you receive
- A written assessment with the evidence behind each finding
- A recommendation, and the alternatives we rejected
- Risks stated plainly, with the cost of ignoring them
- A briefing for the people who have to approve the decision
04Proof
All workWhere this work has been done.
Nordvik Energy
Making a wind portfolio legible to the people who finance it
An operator whose asset data was accurate, complete, and impossible for anyone outside engineering to interpret.
Read the case study
Meridian Rail
One design system across nine customer products
A passenger operator whose nine digital products had drifted into nine different interfaces, brought back into one system with accessibility as the organising constraint.
Read the case studyNext step
Tell us what is not working. We will tell you what we think.
A first conversation is an hour, costs nothing, and usually ends with a straight answer about whether we are the right studio for the problem.