Company · Team/05

Small teams, against real operations.

Six disciplines, organised so that the people who build the platform are the people who watch it run in a customer's warehouse. Nobody here works only from a requirements document, and nobody hands work over a wall to an implementation function that had no say in it.

See open roles How we work

Six disciplines·Distributed across Europe·10:00–16:00 UTC overlap

Disciplines · 6/01

The disciplines.

What each one owns, and the thing it is measured on. The measure is deliberately not output volume in any of them.

PLTPlatform engineeringThe ledger, the document model, permissions, and the API surface. Measured on whether the record stays coherent as modules are added — not on features shipped.

AIAI and agentsRetrieval, grounding, agent scopes, and the evaluation set each agent clears before release. Measured on citeable answers and on scope violations, of which the target is zero.

DELDelivery and implementationProgrammes, waves, migrations, and go-lives. Measured on whether the first process reached production in the first weeks and whether the published wave plan held.

DESProduct and designWhat the operator sees at 06:00 on a loading bay and what the controller sees at period end. Measured on task completion in the field, not on screens produced.

CUSCustomer engineeringSupport that can read the stack trace, plus the escalation path into the team that wrote it. Measured on time to a correct answer, not on tickets closed.

SECSecurity and infrastructureIsolation, keys, deployment topologies, and the audit trail. Measured on recovery drills actually run and on how quickly a customer is told something.

Structure/02

How the teams are put together.

Four structural choices, each of which we would have to undo deliberately rather than drift out of.

Cross-discipline by defaultA team carries platform, AI, design, and delivery together against one outcome. There is no separate implementation department receiving finished software.

On site, at least onceEveryone who builds for a vertical visits one. A warehouse at shift change teaches you more about the stock module than a month of tickets.

Engineers take support rotationsThe people who wrote it answer for it on a rota. It is the shortest feedback loop we have found and the least popular one we keep.

Distributed, with a real overlapAcross European time zones with 10:00–16:00 UTC held in common. Asynchronous by default, and written well enough that this works.

Footprint/03