4–12 weeks for a bounded scope; integration can extend this
Planning estimate, not a delivery promiseProcess owner · Developers/integration team · IT operations · Security/privacy · User champions
Integrate through supported interfaces
Use ERP, CRM, Microsoft 365 or email APIs with least-privilege service identities. Separate environments and keep secrets out of source control. Validate structured output before writing to systems.
Prepare the operating model
Define ownership, incident response, audit logs, deletion, vendor-change review and spending limits. Test unavailable providers, malformed output and recovery.
Introduce the change with users
Update the workflow and review responsibilities. Train on real tasks with safe examples. Roll out gradually, communicate limitations and keep a documented fallback.
What you leave with
- Integrated service and access matrix
- Operations and incident runbook
- User training and handover record
Common mistakes
- Giving the model unrestricted write access
- No named operational owner
- Replacing the workflow without training or rollback