Engineering
We take on systems where being wrong is expensive.
Clinical, financial, regulated, audited. The products came out of this work, not the other way round.
What we do
Both of our products started as work for a specific customer with a real deadline and a real inspection ahead of them. That is still how we prefer to work: build what one customer actually needs, under the constraints they actually have, and turn it into a product only after it has held up in use.
You get the same people who worked out what you needed. There is no account manager and no delivery manager passing messages between you and the engineers, and nobody joins your project without first reading the standard it has to meet. We all work on Indian time, which overlaps the European and Gulf working day by several hours, so a call in your morning is normal rather than a favour.
How it goes
Three stages, and you can stop after any of them.
01
Discovery, paid and short
A few weeks looking at what you actually have — the documents, the data, the system being replaced, the deadline that is really driving this. It ends in a findings report and a fixed scope. If the honest answer is that you need a product configured rather than software built, the report says so and that is where it stops.
02
Delivery in phases, each one usable
Every phase ends with something the person who asked for it can actually use, not a demonstration. If we are running late you see it within weeks rather than at the end, and you can stop after any phase and still have working software.
03
We run what we build
Systems in regulated industries are not finished at handover. They get inspected, upgraded and moved onto new versions. We stay on for that: checking that a change still produces the same results before it goes anywhere near the live system, running the long re-sync overnight so nobody loses a working day, and writing the upgrade note in language the customer can act on. That is the part customers talk about when somebody rings them for a reference.
What we don't
The work we turn down.
- Anything an off-the-shelf product would do well once configured. We will tell you if that is the answer.
- Consumer apps, marketplaces and growth work. It is a different craft and ours does not carry over.
- Extra pairs of hands on somebody else’s team. We take responsibility for a whole system, not for filling a seat.
- Rescuing a system when nobody who built it is still reachable.
Talk to the people who would build it.
There is no sales team to go through first.