4–8 weeks, subject to data and access
Planning estimate, not a delivery promiseSponsor · Process owner · Representative users · IT/security · Privacy contact
Agree evidence before building
Set quality, handling-time, review-time and cost measures. Prepare an evaluation set containing ordinary cases, exceptions and deliberately difficult examples.
Choose buy, configure or build
Compare existing features with a configured enterprise service and a custom solution. Check contractual terms, access controls, export options and who maintains each choice.
Run a controlled trial
Keep human approval and a manual fallback. Record rejected outputs and user effort. Compare the complete new workflow with the baseline, not model speed alone.
Make the next decision
Review results with users and the sponsor. Proceed only if the agreed conditions hold; revise or stop when evidence fails. Preserve lessons even when the pilot stops.
What you leave with
- Pilot canvas and evaluation set
- Quality, time and cost record
- Proceed/revise/stop recommendation
Common mistakes
- Changing success criteria after seeing results
- Testing only clean examples
- Treating a demo as production readiness