Services
Technology consulting and architecture
An outside read on the system, the roadmap and the spend. Written down, prioritised, and specific enough to act on this quarter.
Where the system will break next
We read the code, the data model, the deployment path and the incident history, then write down what will fail as load or headcount grows, ranked by cost of doing nothing. You get a document your engineers agree with, not a slide deck.
Two to four weeks
Fixed scope, fixed fee, written report and a working session.
Before you buy or invest
An independent read on a target company's code, team, licences, security posture and key person risk, written for a commercial reader as well as a technical one.
The question asked properly
Total cost over three years, switching cost, and the parts of your product that are genuinely differentiated. Most teams build things they should have bought, and buy the one thing that was their edge.
Spend that grew quietly
Cloud bills, licence seats and third party services, mapped against what actually gets used. Savings are usually found in idle capacity and forgotten environments rather than in heroic rewrites.
Why delivery feels slow
Branching, review, release cadence and on call. We look at how work reaches production and where it waits, then suggest the smallest change that moves the number.
What we build with
Consulting engagements are deliberately short and fixed in scope. If the answer is that you do not need us, that is a valid outcome and we will say so.
How the work runs
Frame the question
We agree what decision the work has to support and who has to be convinced. A review with no decision attached to it is expensive reading.
Gather the evidence
Code, dashboards, bills, incident history and interviews with the people who run the system. Findings are traced to evidence, not to opinion.
Write it down
A written report with findings ranked by cost of doing nothing, each with a recommended action and a rough effort estimate.
Sit with the team
A working session with your engineers and your executives, and a follow up once the first actions have been attempted.
Questions we get asked
What do we actually receive?
A written report with findings ranked by cost of doing nothing, each with a recommended action, a rough effort estimate and the evidence it rests on. Plus a working session with your team.
Will you recommend yourselves for the build?
Only if you ask. The report stands on its own, and plenty of clients take it to their own team or to another supplier. Saying that you do not need an outside build partner is a normal finding.
How much access do you need?
Read access to the repository, the monitoring and the cloud bill, plus time with two or three of the people who run the system. We work under a mutual confidentiality agreement.
Can you act as an interim technical lead?
For short periods, yes, usually alongside a search for a permanent hire. We are explicit about the end date from the start.
How quickly can you start?
Usually within two to three weeks. Due diligence with a transaction deadline can often be pulled forward, so tell us the date you are working to.
Need an outside read?
Tell us the decision you are trying to make. We will propose a scope, a fee and a date you will have the answer.