BusinessOS
Agreeing the pilot
A short brief to discuss with the process owner, finance and IT. It outlines a future pilot agreement; actual scope, timing and prices are agreed with your company.
Allow 1–3 weeks to start piloting after agreed materials and access are available. Timing for a specific task is agreed separately.
Task and output
One process. For example: item list and supplier replies → comparison with price sources and questions. State what is excluded.
Materials and customer involvement
A completed example, approved data and access. Name the process owner, subject expert and acceptance participants. Agree their involvement before starting.
Quality and acceptance
Compare output with source documents. Check missing data, ambiguity and permissions. Agree tolerances and who reviews the result.
Impact
Compare manual time, turnaround, completed volume and corrections. Distinguish released capacity from cash savings.
Total cost
Show setup, recurring BusinessOS and engineering, included changes, extra work, external models and infrastructure separately.
Timing and checkpoints
Agree the start after materials arrive, interim review and acceptance date. Changes to scope or data access can affect timing.
If the result is not accepted
Record gaps and decide on work within the agreed scope, a revised task or stopping. Agree financial consequences before starting.
After the pilot
Continuation requires agreed scope, volume, support, request handling, engineer cover and a process for new work.
If the engagement ends
Agree delivery of outputs, access to data and rules, revoking access, retention and deletion of copies, and continued operation.
Start with your task
In 20 minutes, discuss inputs, the required output and where a person is needed. Then agree what to test and which materials are necessary.