Five expertises
What this family is
An expertise is a capability applied inside an organisation that already runs. Five of them carry twenty specialties, and any specialty can be bought in six forms — fixed price, time and materials, short placement, long placement, permanent placement, or a named seat.
The five divide by what the work changes. Design changes the interface and the process behind it. Product changes what gets built and whether it worked. Engineering changes the system and the estate it runs on. Scale with AI puts models and agents behind decisions that already exist. Performance answers what an estate costs, how fast it answers and what it emits.
Each specialty is a section on its expertise page, not a page of its own. That is deliberate: a specialty is a declension, and giving nineteen of them their own addresses would produce nineteen thin pages competing with each other for the same queries. The sections are addressable — each has a stable anchor — without being separate documents.
Every specialty page states its proof honestly. A sub-capability is proven when a published case carries a sourced figure, held when a named operator carries it without a case, and declared when it is in scope with nothing published behind it. GreenOps is declared, three sub-capabilities deep, and says so on the page rather than borrowing the credibility of the two beside it.
The six purchasing forms are where most of the negotiation happens, and they are not interchangeable. A design system is rarely bought by the day because its value is in the consistency it enforces over time; a platform team is rarely bought at a fixed price because the scope moves as the estate is understood. Each specialty carries the forms that suit it rather than all six by default.
An expertise is also the honest answer when a client arrives asking for a programme they do not need. Where the destination is already agreed and only the capability is missing, applying that capability inside the existing organisation is cheaper, faster and easier to stop.
What this is not
An expertise is not a team for hire. The forms include placement, but a placement is calibrated against a named gap and carries the practice with it.
It is not a transformation. An expertise applies a capability inside an organisation that already runs; when the organisation itself is the thing that has to move, that is a Programme.
It is not a technology menu. The unit is the capability and the proof behind it, not a list of tools — and the tools that appear on these pages are the ones seen on mandates, not the ones a buyer might expect to read.
Six ways to buy
- Fixed price
- A closed scope, a fixed figure, an acceptance condition written before the start.
- Time and materials
- A capacity bought by the day, against a backlog the client owns and arbitrates.
- Short placement
- One operator inside the client team for weeks to a few months, on a named gap.
- Long placement
- The same, over quarters, where the gap is structural rather than a peak of load.
- Permanent placement
- The operator is recruited into the client organisation; ARCHITEKT holds the search and the calibration.
- Named seat
- The expertise is carried by an interim C-level seat rather than bought as a capacity.
Each specialty carries the forms that suit it, not all six by default. A design system is rarely bought by the day; a platform team rarely at a fixed price.