How we work
A small first decision before a larger build.
The process reduces uncertainty before implementation, keeps consequential judgement human and leaves the operating knowledge with the organisation.
Public method / v23 stages
- Stage 01
- Workflow Assessment
- Stage 02
- Bounded Implementation
- Stage 03
- Handover
- Across all
- Measurement and human control
- What this cannot conclude
- A fourth service line, an open-ended transformation programme or a guaranteed result.
01 / Assessment
Make the build decision explicit.
The Assessment maps the current workflow and creates a decision record. It is paid, fixed-scope work—not a free discovery exercise disguised as sales.
Method block / Assessmentdecision gate
- Input
- One workflow, a named owner, access to representative evidence and known constraints.
- What happens
- Observe the present process, establish a baseline, map judgement points and test feasibility.
- What you receive
- Workflow map, baseline, control boundary, option assessment and implementation recommendation.
- What this cannot conclude
- That implementation should proceed when the evidence, lawful access or ownership is insufficient.
02 / Implementation
Build only what the decision record supports.
Scope, acceptance and release controls carry into delivery. A material change returns to a decision instead of becoming invisible expansion.
Method block / Implementationbounded delivery
- Input
- Approved decision record, access plan, acceptance tests and named release owner.
- What happens
- Implement, evaluate and document the bounded capability against the agreed tests.
- What you receive
- Working capability, evaluation record, operating controls and issue register.
- What this cannot conclude
- That performance outside the tested workflow, data or operating conditions is supported.
03 / Handover
End with ownership, not dependence.
Release is not completion unless the organisation can understand the system, operate its controls and make the next decision.
Method block / Handoverclient-owned
- Input
- Accepted implementation, outstanding issues and agreed operating roles.
- What happens
- Transfer access, documentation, runbooks, limitations and the measurement comparison.
- What you receive
- Handover pack, operating walkthrough and explicit support boundary.
- What this cannot conclude
- That CortexLabs remains an unbounded operator or permanent dependency.
Commercial boundary
Know the shape before work starts.
Fit Call
Free and time-boxed. It checks structural fit and does not produce an Assessment deliverable.
Assessment
Paid, fixed-scope and fixed-fee, with a written decision output.
Implementation
Separately scoped only after the Assessment supports a build decision.
Support
Any post-handover support is explicit and separate—never implied as an open retainer.