Define the working decision
What exactly the system should prepare, who it helps and what it must not do.
MADAI / PILOT METHOD
A pilot is not a model demo. It is a bounded experiment with an owner, data boundary, evaluation set, operating controls and explicit criteria for continuation.
The methodology separates six decisions: purpose, data, baseline, quality, controls and operational readiness. Each decision requires evidence.
01 / FRAMEWORK
Architecture, data, models and automation are designed around specific work scenarios and tests, not around a general impression from a chat interface.
What exactly the system should prepare, who it helps and what it must not do.
Real tasks, correct sources, expected outputs and safety tests.
Identity, logs, approvals, monitoring, fallback and incident procedure.
02 / IMPLEMENTATION
The outcome must be repeatable, traceable and operable. A useful pilot separates baseline performance, retrieval quality, answer quality, tool actions, safety and human decisions.
Time, error rate, quality and cost of the current process.
Approved sources, sensitivity, permissions and retention rules.
Minimum quality, maximum risk and economic limit of the pilot.
Who approves changes to model, prompt, tool or data source.
03 / DECISIONS
The answers determine pilot scope, autonomy, model selection and operating cost.
Long enough to cover representative scenarios and real users. The decision evidence matters more than an arbitrary number of weeks.
Starting with a model before establishing a baseline, evaluation set and workflow owner.
When quality, safety, operations and accountability criteria are met and a regression plan exists.
We define the data, expected output, risks and evaluation set before choosing the model and integrations.