AUTONOMIZED AGENCY ROLLOUT CHECKLIST
Version: 2026-09-07

START WITH ONE CLIENT
1. Record the agency's authority and the customer's agreed scope.
2. Identify the exact business, client key, time zone and authorized users.
3. Inventory records, custom fields, workflows, calendars, sites, funnels, courses, payment connections and phone numbers. Mark each: move / reconnect / retain / unsupported / later.
4. Agree the retail service, your written partner terms, usage schedule, budget behavior, support contact and activation date before billing.
5. Export only authorized data and keep an original backup. Inventory CSVs from the website are planning files, not production imports.
6. Match fields and deduplicate by stable source IDs inside the intended tenant. Never merge different clients.
7. Keep outbound actions disabled. Reconnect accounts using the customer's authorization; never copy passwords or API keys into intake notes.
8. Reconcile source and destination counts, exclusions and relationships. Show exceptions; do not silently discard records.
9. Verify the intended users can access only their client business. Confirm the agency is the paying customer of record and the client cannot be charged a second direct platform subscription.
10. Demonstrate one agreed workflow, including a failed action, a retry and a disconnected dependency. Confirm the real result rather than a success message alone.
11. Obtain client acceptance, choose a cutover window and retain a rollback path. Start service/billing only under the accepted terms.

REPEAT IN GROUPS OF 5, THEN 10, THEN UP TO 25
Reuse the validated template. Each client still receives its own identity, permissions, connection checks, usage budget, reconciliation report and acceptance record. Pause the affected batch for a tenant-isolation, billing, missing-record or unconfirmed-action failure.

REVIEW
Day 1: access, records, service failures and unexpected charges.
Day 3: actual workflow results and support time.
Day 7: customer acceptance, exceptions and measured delivery cost.
Day 14: adoption, ongoing value, usage and whether the next group is justified.

Before promising a full replacement, demonstrate every required workflow. Keep essential existing systems running until their replacement passes acceptance.