Consider a change when missed commitments, unclear ownership, unstable releases, weak communication, inaccessible code or accounts, repeated surprise costs, or reporting without useful decisions become a pattern rather than an isolated event. First document the problem and give the agency a fair opportunity to correct it. If trust or capability cannot be restored, plan the transition around access, code, data, integrations, subscriptions, open work, credentials, documentation, and immediate operational risk.
How Inficial approaches it
Fix the operating problem or plan a controlled transition
Not every disagreement requires a new agency. Start with specific examples, expected standards, owners, and a time-bound recovery plan. A clear reset can be safer than changing teams during a critical trading period.
If the relationship must end, do not begin with credential removal. Inventory access and dependencies first, secure current code and design files, document production workflows, and agree who owns active incidents and releases during handover.
Agency transition checklist
- Store, domain, analytics, tag manager, app, and infrastructure access
- Current theme, repositories, deployment process, and environment variables
- Design files, documentation, decision logs, and open backlog
- App contracts, licences, billing owners, and integration credentials
- Known defects, active incidents, release freezes, and support coverage
- Credential rotation and access removal after handover is verified
