Week by week, from kickoff to live traffic.

Twenty-one business days, broken into four phases with a named artifact at the end of each. You know what is due from you, what is due from us, and exactly which dependency causes the date to move — which is almost always access to recordings or calendar credentials.

The four phases

• Days 1–4 — discovery: recordings, service menu, pricing rules, escalation policy.
• Days 5–11 — build: knowledge base, prompt, integrations, escalation handlers.
• Days 12–16 — evaluation: scenario suite, failures fixed, regression pass.
• Days 17–21 — soft launch on partial traffic, then full cutover.

What causes the date to slip

In practice, one of two things: call recordings arriving late, or calendar and CRM credentials stuck behind someone on leave. Both are on the customer side, which is why the twenty-one-day clock starts when those arrive rather than at signature. Everything else is inside our control and is on us.

What the soft launch looks like

The agent takes overflow and after-hours traffic first while your team still answers primary hours. Every call is reviewed for the first three days. Full cutover happens when escalation rate is stable and no eval regressions have appeared — not on a calendar date, which is the point of measuring it.