Sub-Account Provisioning

Sub-account provisioning is the automated creation and configuration of a client’s workspace the moment their agreement is signed. The SaaS Configurator handles everything: spinning up the sub-account, applying the right snapshot template, configuring default settings, and injecting the client’s branding. No human touches this process. It is the backbone of scalable onboarding, and it is what separates agencies that can handle 5 clients a month from agencies that can handle 50.

Why This Matters

Without automated provisioning, every new client means someone on your team manually creating a sub-account, selecting a template, applying settings, and hoping they remember every step. That works when you have three clients. It falls apart at fifteen. The manual process introduces errors, delays, and inconsistency. One client gets a fully configured account. The next one is missing half the automations because someone was rushing through setup on a Friday afternoon.

The business case is straightforward. Every minute your team spends on repetitive setup is a minute they are not spending on strategy, creative, or client communication. Provisioning automation reclaims hours per client. Multiply that by your monthly intake, and you are looking at a significant operational savings that compounds every single month.

There is also the client experience angle. When a client signs and their account is ready within minutes, it signals professionalism. They feel momentum. Compare that to waiting two days for someone to “get to it.” That early impression shapes the entire relationship. Fast provisioning tells the client they made the right choice.

How to Think About It

Think of sub-account provisioning as the factory floor of your agency. The agreement signature is the work order. The SaaS Configurator is the assembly line. The finished sub-account is the product rolling off the line, ready for customization. Your job is to design the assembly line once, test it thoroughly, and then let it run.

The key principle here is snapshot discipline. Your snapshot templates need to be living documents. Every time you improve a workflow, add a pipeline stage, or refine an automation in your master account, that improvement should flow into your snapshot. Stale snapshots mean new clients start with outdated configurations, and your team ends up doing manual fixes anyway.

Configuration should be layered. Start with a base snapshot that every client gets, then let the configurator apply package-specific additions on top. A starter package might get the basics. A premium package gets the full automation suite. This layered approach keeps your snapshots manageable and your provisioning logic clean.

Common Mistakes

Using a single monolithic snapshot for all packages. When every client gets the same everything, you end up with starter-tier clients sitting on enterprise-level automations they will never use. It clutters their workspace, confuses them during onboarding, and creates support tickets about features they did not pay for. Layer your snapshots by package.

Never updating snapshots after initial creation. The snapshot you built six months ago is already outdated. If you have improved your pipeline stages, added new email templates, or refined your workflow triggers since then, new clients are starting behind. Schedule monthly snapshot reviews. Treat them like product releases.

Skipping branding injection in the provisioning step. When a client logs in for the first time and sees your agency’s default branding instead of their own, it breaks the illusion of a custom-built system. The configurator should apply at minimum their logo, colors, and business name during provisioning. First impressions in the platform matter.

Not testing provisioning end-to-end after changes. You updated a snapshot, tweaked the configurator logic, and assumed it would work. Then a real client signs and the account is half-built. Always run a test provisioning cycle after any changes. Create a dummy agreement, let the system fire, and verify every setting landed correctly.

Treating provisioning as a one-time setup task. Provisioning is not “set it and forget it.” As your service offerings evolve, your provisioning logic must evolve with them. New packages, new integrations, new compliance requirements. All of these require updates to your provisioning pipeline.

Tools Involved

The core engine is the GHL SaaS Configurator, which handles account creation and snapshot application. Your snapshot templates define what each account looks like out of the box. Custom fields carry client-specific data into the new account. For API-level control over sub-account configuration, the Sub-Accounts endpoint gives you programmatic access to everything the configurator does and more.

Where This Fits

Sub-account provisioning fires at sequence position 7, immediately after the agreement is signed (SIG). It runs in parallel with the ClickUp Task, Google Drive Folder, and Team Notification. All four of these fire simultaneously on the agreement signature event. After provisioning completes, package-specific configurations and client-facing setup steps can begin. The sub-account must exist before any platform work happens, so this is a hard dependency for everything downstream.

Common Questions

What happens if provisioning fails midway? The system should be configured to alert your team immediately on failure. Build a fallback notification into your automation so someone is pinged if the sub-account does not appear within the expected timeframe. Most failures come from API rate limits or snapshot conflicts, both of which are fixable and retriable.

Can clients access their account before provisioning is complete? They should not. The welcome email with login credentials should only fire after provisioning is confirmed complete. Sending credentials to a half-built account creates confusion and support tickets. Sequence matters here.

How long does provisioning typically take? For most snapshot sizes, provisioning completes in under two minutes. Larger snapshots with extensive workflow libraries may take up to five. The key is that it is fast enough that the client never notices a delay between signing and receiving their welcome credentials.