What gets delivered
Unlike an exploratory pilot, an implementation project is engineered for production. The deliverable is a running agent that completes a specific workflow end-to-end with measurable KPI improvement, not a slide deck or notebook.
- A production-deployed agent with documented architecture diagrams.
- Integrations to source systems via MCP servers, REST APIs, or RPA.
- Golden test set of 30–100 representative tasks with CI gates.
- Tracing and evaluation dashboards (Langfuse, LangSmith, Braintrust, or Arize Phoenix).
- Human-in-the-loop approval flows and audit logs.
- Runbooks for on-call, retraining, and prompt change management.
Typical phases
Most implementations run 6–10 weeks following a four-phase cadence.
- Discovery (1 week) — workflow mapping, KPI selection, data and permission audit.
- Design (1–2 weeks) — agent topology, tool inventory, eval set, governance plan.
- Build (3–5 weeks) — agent implementation, MCP/API wiring, eval harness, UAT.
- Launch (1–2 weeks) — staged rollout, traces in production, KPI baseline → impact.