Consulting
Plain advice on what to do with your software
Whether your software is already running or still a plan, we look at it properly and tell you what we would do.
When to call us
Most people come to us with one of these. If yours is not here, tell us anyway.
You inherited a system
Nobody left notes, and the people who built it have moved on.
Build, buy or fix?
Every option has someone arguing for it, and you have to choose one.
Slow, fragile or costly
Something keeps breaking or the bill keeps climbing, and nobody can say why.
A second opinion
You have a quote or a proposal and want someone independent to read it.
What we look at
Each job decides which of these matter. These are the places we usually start.
The code
How it is put together, and how hard it is to change safely.
Infrastructure
What it runs on, such as AWS or a rented server, and what that costs.
Data
What is stored, where, and whether you could get it back.
Security
Who can get in, and what they could reach if they did.
Running costs
What you pay each month, and what you pay for but do not use.
Services you rely on
Outside services, such as payment or email providers, and what happens when one goes down.
How changes ship
Testing, reviews and releases, and how often a change breaks something.
Who knows what
Which parts only one person understands, and what that risks.
What you get
Whatever your question needs. We agree which on the first call, along with the price.
Advice on a call
We talk it through in a session, and you leave with an answer.
A written assessment
We go through your system and write up what is there, what is wrong, the options and what we would do. It suits an answer others have to act on or sign off.
Someone on your side
We join you over time as a tech lead or solutions architect.
How it works
From the first call to an answer you can act on.
A free first conversation
A short call. You tell us the problem, and we tell you whether we can help and what we would look at.
We agree the shape
A session, a written assessment or an ongoing role, whichever fits, and what it costs.
We do the work
We go through what you show us, such as the code and the infrastructure, and talk to the people who know it.
You get your answer
On the call, in writing, or from us working alongside you, so you can decide with confidence.
What happens next
The advice is yours, whoever acts on it.
Do it yourself
Your own team works through it, in the order we set out.
Hand it to another team
Any developer can pick it up and carry it out.
Have us build it
We already know the system, so we can start where the advice ends.
Tell us the problem
One email is enough. We reply with whether we can help and what we would look at first.