Business use case — at a glance

  1. Step 1Scope & architecture agreed
  2. Step 2Auth & tenants work
  3. Step 3CRM & integrations UAT
  4. Step 4Voice/RAG when in scope
  5. Step 5Go-live checklist

Sign off each phase—skip modules you did not buy.

Delivery phases and acceptance criteria

Milestones tailored to selected modules—projects without voice or RAG should not pay for those gates.

PhaseDeliverablesAcceptanceTypical timing
0 — DiscoveryProcess maps, requirements, architecture, risk registerBuyer signs scope priorities2–3 weeks
FoundationAuth, tenant isolation, core schema, environmentsRole/tenant tests passWeeks 3–6
Business workflowsCRM, leads, workflows, integrationsAgreed E2E scenarios passWeeks 6–14
AI & voice (if scoped)Agents, knowledge, telephony, handoffTest calls & eval scripts passParallel or follow-on
Production readinessMonitoring, backups, security checks, runbooksRelease checklist signedPre go-live

Planning bands (INR): product page packages table.

Next step

Configure modules, budget band and timeline on the product page—or read engineering evidence on the case study.

Open scope estimator Technical case study

More in this cluster