FAQ · Delivery paths
How do you accept an AI Agent pilot?
FFDE acceptance is not "did we use AI?" — it is whether one Agent MVP shows measurable improvement across efficiency, quality, cycle time, cost, and knowledge assets, with human sign-off at three decision gates: intent alignment → scope confirmation → GO/NO-GO.
Key points
- Final bar: one Agent MVP + ROI review + release decision — then Phase 2, not endless PoC
- Acceptance vs activation: sign GO/NO-GO at pilot end; activation targets may include a 2–4 week post-pilot observation window
- Graduation criteria agreed at kickoff: timeline cap, value metrics, activation goals; expand if met, exit cleanly if not
- Three non-negotiable human gates: kickoff intent alignment, pre-build scope/contract confirmation, acceptance GO/NO-GO
- Launch ≠ activation: accounts provisioned is not success — stable daily use by target users is
- Acceptance trio: Spec (scope), Eval (golden Q&A / UAT pass line), Handoff (runbook and owner)
- ROI five dimensions: efficiency, quality, cycle time, cost, knowledge assets (7-day can simplify narrative; 2–4 week needs written record)
- All five pillars reviewed: missing data, security, or ops means not handoff-ready
How to do it
- Stages 0–1 / Day 1: freeze Top 1, Eval criteria, and graduation criteria; name acceptance signatory
- Stage 2 / before build: confirm Spec, data red lines, and Out of Scope in writing
- Stages 3–4 / trial: business trial and golden pass line; record activation baseline — daily habit by Day 7 is not required
- Stage 4 / Day 7: five-dimension ROI review + GO/NO-GO sign-off
- Stage 5: runbook handoff; review activation during the observation window in graduation criteria