Fifteen years building software that stays in service.
Software built around how you already work.
We are a team of developers. Not a consultancy that subcontracts the building, and not an agency that hands over a design and leaves. The people who scope your system are the people who write it and the people who still answer the phone about it three years later.
We work with organisations that have outgrown the software holding their operation together: the spreadsheet nobody dares touch, the licensed product that fits eight of their twelve processes. We replace it with a system shaped around the way the business actually runs.
Years the oldest system we still maintain has been running
0
Projects subcontracted out
What we are actually trying to do
A solution, not a deliverable
The job is not to ship software. It is for the problem you brought us to stop existing. When the right answer turns out to be a change of process and half a screen, that is what we propose, even though it is the smaller invoice.
The process before the code
Automating a bad process makes it faster, not better. We spend the first weeks learning how the work is done today, and part of what we hand back is a list of the steps that do not need to exist at all.
The working day should not be tedious
People use this software for eight hours a day. Taking the repetitive part out of that day is not a nice extra, it is most of the value. What should be left is the work that needs a person's judgement.
Measured against the business, not the backlog
A project has gone well when the business can do something it could not do before. That is the conversation at the start, and it is the same conversation we come back to at the end.
How we operate
Four commitments on every engagement.
Written scope first
Nothing is developed until the deliverable, the price and the date are agreed in writing.
Weekly releases
Your users operate the system from early in the project, so feedback arrives while it is cheap.
In-house delivery
The engineers who scope the work are the engineers who build it. Nothing is subcontracted.
Long-term support
Systems we delivered a decade ago are still maintained by the same company today.
The technology we build on
We specialise in the Microsoft stack rather than covering everything. Working with one platform is why we can estimate accurately and still support a system years after it went live.
Our editorial articles explain engineering decisions behind business software: data ownership, integration, deployment and ongoing operation. They link to technical references and distinguish illustrative examples from named client projects.
Necessary cookies keep the site working. With your permission we also use analytics cookies. Google receives basic measurement signals without analytics cookies before you accept or if you reject. You can change your cookie choice at any time. See our cookie policy.