Service 06

IT Consulting

We review what exists, map what is needed and give you a plan you can act on — including the parts that say "do not build this yet".

Scope

What is included

A second opinion with skin in the game. Everything below is part of the engagement unless we agree to cut it.

Architecture reviewWhere the current design will hold and where it will break as you grow.

Codebase health checkDependencies, test coverage, risky areas and what maintenance is actually costing you.

Technology selectionA decision record with trade-offs written down, not a preference asserted.

Migration planningA staged route off legacy systems that does not require a big-bang weekend.

Security assessmentAuth, access rules, data handling, secrets and dependency risk.

Delivery processHow work gets from idea to production, and where it currently stalls.

Architecture reviewThreat modellingCost analysisADRs

How we work

7 stages from first conversation to running system. Each one ends with something you can see and sign off, so progress is never a matter of trust.

01
Brief
A short session to understand the decision you are trying to make and by when.
You get: Agreed questions and scope
02
Gather
Access to code, infrastructure and documentation, plus interviews with the people who run it.
You get: Evidence collected
03
Analyse
Findings tested against the actual system rather than assumed from a diagram.
You get: Prioritised findings
04
Options
Two or three realistic routes with cost, risk and timeline for each — including doing nothing.
You get: Options with trade-offs
05
Recommend
A clear recommendation, said plainly, with the reasoning you can take to your board.
You get: Written recommendation
06
Roadmap
Sequenced work with dependencies, so it can be funded in stages.
You get: Roadmap you can budget from
07
Follow through
We stay available while you execute, whether or not we do the building.
You get: Review checkpoints

Questions

Will you recommend yourselves for the build?

If we are the right fit we will say so, and you are free to take the plan elsewhere. The deliverable is written so another team can execute it.

How long does a review take?

A focused review is usually one to three weeks depending on system size. We agree the boundary before starting.

Can you talk to our board?

Yes. The recommendation is written to be read by people who are not engineers.

Tell us the goal and the deadline. You will get a scope, a timeline and a figure.