Embedded Integration Tenant Provisioning (Onboarding)

Embedded Integration Tenant Provisioning (Onboarding)

1. 01

   Map every client system to a named owner and a data classification before a single connector is authorized

   List each source system (CRM, ERP, billing, marketing stack), the internal person accountable for it, and whether it holds PII, financial records, or regulated data. Connectors get approved against that map, not against whoever asks loudest.

2. 02

   Decide per client whether the integration layer is white-labeled or vendor-branded, and put the decision in the contract

   Full white-labeling (Albato, Locoia, Prismatic) lets an agency present the integration marketplace as its own product; partial or no white-labeling (Cyclr, Paragon, Workato) means the client sees the upstream vendor. That choice changes renewal leverage, so it belongs in the statement of work, not in a delivery Slack thread.

3. 03

   Stand up one tenant per client with isolated credentials and a separate environment for testing

   Multi-tenanted platforms (Cyclr, Prismatic, Paragon) support this natively. Never share a workspace across two client accounts, even when the same agency team runs both.

4. 04

   Connect read-only first and run a full sync cycle before granting any write scope

   A read pass surfaces field mismatches, duplicate records, and rate-limit ceilings while the blast radius is zero. Write access is granted only after the read sync reconciles to the client's system of record.

5. 05

   Classify each workflow by autonomy level and insert a human checkpoint on anything client-facing

   Goal-driven agents that touch outbound email, CRM stage changes, or customer messaging need an approval gate. A swarm of autonomous agents once pushed hundreds of malicious packages to a public registry and forced a four-day signup shutdown, which is the failure mode a checkpoint prevents.

6. 06

   Document the rollback path and the credential rotation schedule in the client's runbook

   Every connector gets an owner, a rotation interval, and a tested disable procedure. If the client's API key leaks, the runbook should let a junior operator sever the connection in under five minutes.

7. 07

   Set the retainer review checkpoint at day 30 with a written integration health summary

   Report connector uptime, failed runs, records synced, and hours saved against the manual baseline. This is the artifact that justifies the middleware line item at renewal.