Software consultancy
Decide before it gets expensive
Not sure what to build or how? As a software development consultancy, we help you make the right technical decisions while they are still cheap to change.
Build or buy, decided properly
Does it already exist, well enough?
YesBuy it. Integrate it. Spend the saved months on what only you can build.
NoKeep going.
Is it the thing customers pay you for?
YesBuild it, and own it properly.
NoBuy, or defer. It will not be your advantage.
Can you still maintain it in three years?
YesBuild it.
NoBuy it, or budget for the team that will.
You had a problem. Now you don't.
Before
The costly decisions are made early, quickly, and usually by whoever is most confident. Build or buy. Rewrite or refactor. This platform or that one. Each is cheap to change in week one and structural by month six.
After
We have made these calls across 120+ products, and we will tell you what we would do and why — including when the answer is that you do not need us.
What we advise on
Build, buy, or wait
Whether the thing you are about to build already exists, whether the version you can buy is good enough, and what the real cost of each is over three years rather than three months.
Architecture and platform choice
Stack, hosting, data model, and the boundaries between services. Chosen for the team you have and the load you actually expect.
Rewrite or refactor
The decision nobody wants to make on a system nobody wants to touch. We assess honestly and stage the route, because a big-bang rewrite is usually the expensive answer.
Technical due diligence
Before you invest or acquire: what the codebase really is, what the risks cost, and what the team can carry.
Team and delivery
How to structure the team, what to hire, what to outsource, and where your delivery process is quietly costing you weeks.
Security and compliance readiness
What you need in place before an enterprise customer's security review, rather than during it.
How it works
- 01
Frame the decision
We establish what is actually being decided, what the constraints are, and what would make each option the right one. Half of consultancy is discovering the question was wrong.
- 02
Investigate
Code, data, infrastructure, and the people doing the work. Evidence rather than an opinion assembled from a briefing document.
- 03
Recommend, in writing
A clear recommendation with the reasoning, the risks, the costs, and the option we would take — written so you can disagree with a specific step.
Don't take our word for it
What differentiates them is that they always provide guidance and support that goes beyond their assigned tasks. It feels like I have a technical co-founder working with me.
Skilled professionals who deliver on commitments.
Stuff you'd normally have to email us about
Sometimes, and we tell you when the honest answer is off-the-shelf software, a different vendor, or nothing at all. A recommendation you cannot trust is worth nothing, and we would rather keep the relationship than win one project.
Yes — every engagement ends in a written recommendation with the reasoning and the costs. It is yours, and it is deliberately specific enough to hand to another team.
That is most of this work. We look at the code, the data model, the deployment path, and how the team actually works, then report what we find rather than what would be convenient.
An advisory call usually within days. A full assessment normally starts within a week or two.
Got a decision you'd rather not get wrong?
Tell us what you're weighing up. We'll tell you what we'd do and why.
Book a consultation