WORK.01 — SELECTED BUILDS

The work, with the control layer visible.

Client names and implementation details stay private. The operating pattern, safeguards and measured change do not.

CS.01 — ANONYMISED BUILDRegional logistics

Agent desk for a regional logistics group

ai agentscrm
THE CONSTRAINT

Manual triage makes every inbound request wait for an operator before the real work can start.

THE SYSTEM PATTERN

The system pattern pairs classification and live context retrieval with bounded CRM actions. Ambiguous or sensitive cases stop at a human gate.

REPRESENTATIVE SYSTEM MAPClient-specific architecture withheld
01inbound queue
02retrieve context
03bounded action
04human gate
CONTROL SURFACE
/approval-gates/run-traces/confidence-routing
CS.02 — ANONYMISED BUILDFintech operations

LLM harness for a fintech document pipeline

harnessevals
THE CONSTRAINT

Document pipelines fail quietly when model output is accepted before structure, evidence and fallbacks are checked.

THE SYSTEM PATTERN

The control layer validates each extraction against a schema, evaluates quality and routes failed passes through a deterministic fallback.

REPRESENTATIVE SYSTEM MAPClient-specific architecture withheld
01document intake
02structured output
03quality eval
04fallback route
CONTROL SURFACE
/schema-validation/eval-thresholds/failure-queue
CS.03 — ANONYMISED BUILDProfessional services

Second brain for a 200-person consultancy

second brainsearch
THE CONSTRAINT

Institutional knowledge is only useful when retrieval respects permissions, cites the source and makes uncertainty visible.

THE SYSTEM PATTERN

The system pattern synchronises source permissions, retrieves the smallest useful evidence set and returns a cited answer with a trace.

REPRESENTATIVE SYSTEM MAPClient-specific architecture withheld
01permission sync
02retrieve evidence
03cited answer
04query trace
CONTROL SURFACE
/access-control/source-citations/retrieval-evals
NEXT.01 — YOUR SYSTEM

Bring us the workflow that should stop being manual.

Start a build