WORK.01 — CASE STUDIES + PATTERNS

Three client projects: purchase approvals, apartment payments and online retail.

Read three client projects, then explore examples of software for customer enquiries, document checks and document search.

Send a briefCompare services
/INDEX · 03 CASE STUDIES + 03 PATTERNS
CASE.01Every request has an owner.CASE.02Apartment repayments, controlled from contract to balance.CASE.03From source catalog to customer handoff.PAT.01Bounded agent deskPAT.02Checked document pipelinePAT.03Cited knowledge retrieval
CASE.01 — PROCUREMENT OPERATIONSOperational system delivered

Every request has an owner.

Follow one mining procurement request from accounting through cross-department approval, documents, inventory, and a complete decision trail.

Open the case study
CASE.02 — PROPERTY OPERATIONSOperational foundation delivered

Apartment repayments, controlled from contract to balance.

See how a property company connected apartment installment contracts, payments, allocations, balances, and audit history inside one controlled system.

Open the case study
CASE.03 — COMMERCE OPERATIONSTwo-phase platform delivered

From source catalog to customer handoff.

See how G3 synchronized thousands of products each day, controlled source purchasing, and connected office receiving to the final customer handoff.

Open the case study
PAT.01 — REPRESENTATIVE PATTERNAgent actions

Bounded agent desk

ai agentscrm
THE CONSTRAINT

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

THE SYSTEM PATTERN

This example sorts incoming requests, checks customer records and drafts replies or record updates. By default, a person approves before anything is sent, paid or changed in your records. You can choose to automate specific low-risk steps, such as routine reminders, agreed in writing. Unclear or sensitive cases wait for review.

REPRESENTATIVE SYSTEM MAPIllustrative control flow
01inbound queue
02retrieve context
03bounded action
04person approves
CONTROL SURFACE
/approval-gates/run-traces/confidence-routing
PAT.02 — REPRESENTATIVE PATTERNDocument operations

Checked document pipeline

harnessevals
THE CONSTRAINT

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

THE SYSTEM PATTERN

This example checks required fields in each extraction and sends failed checks to an agreed review process.

REPRESENTATIVE SYSTEM MAPIllustrative control flow
01document intake
02structured output
03quality eval
04fallback route
CONTROL SURFACE
/schema-validation/eval-thresholds/failure-queue
PAT.03 — REPRESENTATIVE PATTERNInternal knowledge

Cited knowledge retrieval

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 MAPIllustrative control flow
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.

Tell us what starts the task, who handles each step, and what needs to happen at the end.

Send a brief