Prove one governed workflow before expanding the platform.
A Matechi pilot begins with one recurring decision, representative inputs, named users, explicit controls, and a measure that can determine whether the work should advance, change, or stop.
Week 0: decision and boundary
Confirm the workflow owner, source evidence, exceptions, systems, user roles, action authority, representative sample, and baseline measure. No integration begins before those boundaries are accepted.
Weeks 1-2: mapped proof
Configure or prototype the decision path against representative work. Review expected findings, false positives, missing data, role handoffs, and the first operator-facing output.
Weeks 3-4: controlled use
Run the workflow with named reviewers, retain inputs and decisions, compare results against the baseline, and correct the rule, data, or interface where evidence requires it.
Weeks 5-6: decision and handoff
Deliver the working proof, configuration and rule artifacts, run evidence, measured result, operating boundary, integration plan, and a go, revise, or stop recommendation.
Typical deliverables
Workflow map; data and integration inventory; configured product or proof application; review and action controls; test set; findings or output record; operator session; measured pilot report; scale recommendation.