How we deliver
Every engagement follows the same four stages, scaled to its size. A two-week review moves through them quickly; a year-long programme returns to them with each release.
-
Understand
We start with the service, its users and its constraints: security classification, existing contracts, skills in the team, budget and deadlines. We agree what “done” means before designing anything.
-
Decide
We set out the realistic options, recommend one and record why. Decisions are reviewed through design authority, so they hold up in front of assessors, auditors and the next team.
-
Deliver
We build or oversee the build, staying close enough to the work to catch trade-offs as they appear. Risks are raised early and in writing, while there's still time to act on them.
-
Hand over
We leave designs, runbooks, patterns and a decision log your own people can run with, and we plan the handover from the first week rather than the last.
Senior-led, always
Every engagement is led by a 9fold principal who stays on it from the first conversation to handover.
Bad news travels early
If a design, supplier or timeline is at risk, you hear it from us first, in writing.
The right reliability, not the most
Not every service needs five nines. We work out what each one needs, then design and pay for that.
Independent by default
We don't resell cloud, licences or managed services, so our recommendations aren't shaped by what we'd earn from them.
Your standards, not ours
We work to the GDS Service Standard, the Technology Code of Practice, Secure by Design and your own architecture principles.
Vetted people
Everyone we put on a programme is SC-cleared or able to be, and works to our standards under a 9fold principal.
A name taken from the nines
Engineers describe reliability in nines. Each extra nine cuts the downtime a service can have by a factor of ten, and usually raises the cost of running it.
| Availability | Nines | Downtime a year |
|---|---|---|
| 99.9% | Three | 8.8 hours |
| 99.99% | Four | 53 minutes |
| 99.999% | Five | 5.3 minutes |
| 99.9999999% | Nine | 0.03 seconds |
No public service needs nine. The name is a reminder that the right number depends on the service, and that our job is to work out which one you need and design for that, rather than sell you the most.
See how this works on a real programme
Our case studies follow the same shape: context, approach and outcome.