Industries
We do not claim every sector. These are the six where we have enough scar tissue to be useful on day one.
Domain knowledge is not a marketing claim
An engineer who has never seen a reconciliation break will write a lending system that reconciles beautifully in testing and fails on the first weekend.
What follows is an honest map of where we have that experience and where we do not. If your sector is missing, we will say so and, where we can, point you somewhere better.
Logistics and Supply Chain
Route planning, fleet telemetry, warehouse systems, and the unglamorous integrations that hold a supply chain together.
Our longest running engagement, since 2018, is a dispatch engine that plans 40,000 consignments a day.
Financial Services and Fintech
Lending, payments, and reconciliation systems where a rounding error is a regulatory event.
We have taken two platforms through their first regulatory audit with no findings on the security review.
Healthcare and Life Sciences
Clinical and patient facing systems, built with the assumption that data handling will be scrutinised.
Data residency and access logging are designed in at the start, because retrofitting them is far more expensive.
Retail and Commerce
Storefronts, catalogues, and the order pipelines behind them, at volumes where caching stops being optional.
Most commerce work we inherit is not slow because of the storefront. It is slow because of the order pipeline.
Education Technology
Learning platforms, assessment engines, and the reporting that institutions actually run on.
Term start is a load test with a fixed date. We build for that day, not for the average.
Manufacturing and Industrial
Shop floor data, maintenance scheduling, and connecting equipment that predates the internet.
The hardest part is rarely the software. It is agreeing what the machine data actually means.
Sectors we decline
We do not take work in gambling, high frequency trading, or safety critical embedded systems such as medical devices and avionics.
Not because the work is beneath us. Because the failure modes demand a specialisation we do not have, and pretending otherwise would put someone at risk. In those cases we will tell you on the first call.
Before we accept an engagement
Four questions we ask ourselves, and answer to you:
Tell us what you are building. We will tell you what it takes.
No sales script. A working engineer reads your brief and replies with a scope, a team shape, and an honest estimate.