Commissioned systems
One workflow carries your business. We build the software it runs on.
Then we put it into production and keep operating it. Most of what we build replaces a spreadsheet that three people understand and nobody can afford to lose.
How an engagement runs.
Five stages. You can stop after the specification and keep everything it produced.
- 01
Consult
We sit with the people doing the work and map what actually happens, including the parts nobody documented. You get an honest answer about whether software is the right fix, and we will say so when it is not.
- 02
Design
We write the specification: what the system does, where it sits in the work, and what it must never get wrong. It is yours whether or not you continue with us, and it is the document the build is quoted against.
- 03
Build
We build the smallest system that carries real work and put it in front of the people who will use it. You see working software, not status reports.
- 04
Validate
The old process stays standing. We migrate deliberately and run both in parallel until the numbers agree. Nothing goes live on a Friday, and nothing goes live because a date said so.
- 05
Maintain
The engineers who built it stay responsible for it: monitoring, changes, and the call at eleven at night. This is the part most studios do not offer, and it is the reason the systems we ship are still in production years later.
How we arrive at a number
We gather the specification first, and quote against it.
We do not quote a build before we understand the work. The specification is what makes a number mean anything: it is written with the people doing the work, it says what the system must do, and the build is priced against that document rather than against a conversation. If the specification says do not build this, that is a result, and you keep it.
- Specification
- gathered with the people doing the work
- Build
- quoted against the specification
- Operate and support
- agreed once the scope is fixed
A system we still run.
All workLuxury commerce · live in commercial use
A wrong record here is a commercial event, not a support ticket.
Individual products from $10,000 to $500,000 and a catalogue worth tens of millions, run on a system we built and still operate.
- individual product value
- $10k – $500k
- catalogue value
- Tens of millions
- operated by
- the team that built it
Client withheld under confidentiality. Figures published with sign-off.
Describe the workflow.
A paragraph is enough: what happens today, who does it, and what it costs when it goes wrong. It reaches the engineer who would be responsible for building it.