Industries
Twelve sectors, and what actually breaks in each one.
Every industry has one constraint that decides how its software has to be built, and it is rarely the one the brochures name. These pages set out how we approach software development in each sector: what we build, the rules that shape it, where AI earns its cost, and where we are still early.
The index
Pick the one you live in.
Each page states the constraint, what we build against it, the regulation that applies, where AI earns its cost and where we stop. Where we have a case study or a client review, the page shows it. Where we do not, it says so.
How we work across sectors
The sector changes the constraint. It does not change the method.
What is different every time
- The regulation, and whether it is enforced by an auditor or by a customer walking away.
- The load shape. A school bell, a campaign, a storm and a trading day are four different problems.
- What failure costs, which sets how much engineering the business case can carry.
- Who the user is, and whether they can be trained or have to be accommodated.
- How long the system has to live, which decides how boring the technology should be.
What never changes
- A senior engineer replies within one business day, and the first call is with an engineer, not an account manager with a deck.
- A written approach with a cost and time range within a week, then a fixed proposal with a like-for-like comparison against conventional delivery.
- Tests before the rewrite, always, including on the parts nobody wants to touch.
- Repository access from day one, and the code and IP transfer to you on final payment.
- Five times faster at a fifth of the cost of conventional delivery, or we tell you we are not the right firm.
Next step
Tell us which rules your software has to live by.
A senior engineer reads every enquiry and replies within one business day with an honest view of what it will take, including when we are not the right firm for your sector.
