Business use case — at a glance

Step 1Owner per integration
Step 2API + idempotency
Step 3UAT with real samples
Step 4Cutover & monitoring

A simple webhook and a legacy sync are not the same effort.

Integration planning checklist

Use in discovery—a basic webhook and a two-way legacy sync do not have the same effort.

Per integration, document

☐ System name and business owner
☐ API type: REST, GraphQL, SOAP, file drop, database view
☐ Auth: OAuth, API key, mutual TLS, VPN
☐ Direction: inbound events, outbound actions, or both
☐ Idempotency: provider event ID for webhooks
☐ Rate limits and backoff policy
☐ Field mapping source of truth (CRM vs external)
☐ PII fields and retention
☐ Sandbox credentials and test accounts
☐ Rollback if integration publishes bad data

Migration-specific

Record volume and dedupe rules
Historical conversations/calls import?
Data quality remediation owner

Select integration count band on the estimator.

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