Engineering
for others.
Client work runs on the same architecture patterns, review discipline, and deployment infrastructure as our own products. Engagements are not a separate quality tier — they inherit a stack already carrying live software. Engineering, design, brand, and growth can be commissioned together or independently.
Commission any of them on their own or in combination — the scope is yours to set. A large share of the work is repairing and extending systems that already exist rather than building new ones.
Nine practices,
one standard.
Commission one or several. Each practice has its own page with the full scope of services and what you receive.
How the work
actually runs.
Identical across all nine practices. Every phase ends in an artifact you can read, run, or audit — if a phase produces nothing, it did not happen.
Diagnose
1–2 weeks
Read the system
Constraints, existing code, commercial goal, and the failure modes that matter. Ends in a written brief with what we recommend and what we advise against.
- Technical brief
- Risk register
- Scope and non-scope
Architect
1–3 weeks
Decide in writing
Data model, service boundaries, integration surfaces, and interface structure. Every significant choice gets a decision record naming the alternative we rejected.
- Architecture note
- Decision records
- Interface prototype
Build
Milestone-based
Ship in reviewable increments
Two-week increments, each deployed to a live environment and demonstrable. Reviewed, tested, and observable before it counts as done.
- Live environment
- Increment demos
- Test coverage
Harden
1–2 weeks
Break it deliberately
Load, failure injection, access review, restore rehearsal, accessibility and performance passes. The phase most vendors quietly skip.
- Assurance report
- Restore rehearsal
- Performance budget
Operate
Ongoing or handover
Leave it survivable
Runbooks, monitoring, and a documented handover — or a retainer if you would rather we kept carrying it. Your choice, not a lock-in.
- Runbooks
- Handover session
- Support terms
Three ways
to buy engineering.
Pick the shape that matches your constraint. All three carry the same operating standard, the same review discipline, and the same named accountability.
Project delivery
Defined scope, defined outcome — A bounded build with an agreed specification, milestone sequence, and handover. Best when the destination is clear and the path needs engineering.
Embedded engineering
Our engineers, inside your team — Dedicated engineers and designers working in your stack, your standups, and your repository. Capacity without a hiring cycle, under our review discipline.
Technology leadership
Fractional CTO and architecture authority — Senior technical judgement on retainer — architecture calls, delivery review, stack and hiring direction — without a full-time executive appointment.
Capability is one axis.
Sector is the other.
The same nine practices apply across sixteen industry sectors, from logistics and travel through to financial services, healthcare, manufacturing, and the public sector. Where we operate a product of our own in a sector, we say so.
Commission one practice or the whole programme
Tell us what you need built, designed, branded, repaired, or grown. Engineering is our core, but you do not need a platform programme with us to commission any of the rest.