Client Account Intake and Workspace Provisioning (Onboarding)

Client Account Intake and Workspace Provisioning (Onboarding)

1. 01

   Inventory every channel the client owns before any workspace is created

   List each profile handle, page ID, ad account, and Google Business Profile location, then flag duplicates or legacy handles the client forgot about. Channel coverage claims vary widely across platforms, so confirm the actual list against the client's own audit rather than a vendor's supported-network list.

2. 02

   Map approval authority to named humans, not job titles

   Record who drafts, who approves, and who has final sign-off on regulated or executive-voice content. Approval routing is the feature agencies most often assume is configured when it is not.

3. 03

   Decide white-label posture per client before provisioning

   Some clients want the agency's brand on reports and some want the platform's; full white-label is available on services like Sendible and ContentStudio, while others such as Agorapulse and Sked Social do not offer it. Settle this at intake so reporting templates are not rebuilt mid-retainer.

4. 04

   Set permission tiers that match the delivery team's real roles

   Separate strategist, creator, community manager, and client-viewer access, and test each tier with a live login. Permissions that look correct in settings frequently break when a client is invited as a reviewer.

5. 05

   Baseline the analytics before the first post goes live

   Export 90 days of historical performance per channel so post-launch reporting has a comparison point. Analytics reliability differs by network and by platform, so note which metrics the client already trusts and which you will source elsewhere.

6. 06

   Run a two-week throughput test on a representative client set

   Time the coordination loop (brief to draft to approval to publish) across three to five accounts before quoting a per-account retainer. Revision load, not seat price, is what erodes margin.

7. 07

   Document the escalation path for platform outages and API breaks

   Name who contacts the client, who contacts the vendor, and what the fallback publishing route is. A scheduling failure during a product launch is a retention event, not an inconvenience.