Go High Level (GHL) Agency Setup: Complete Guide | GHLCRM.US

A successful GoHighLevel agency setup starts by separating your agency operations from client sub-accounts, defining permissions, standardizing CRM architecture, and testing every reusable system before onboarding clients.

The recommended structure is:

Agency Account

↓

Agency's Internal Sub-Account

↓

Client Sub-Accounts

↓

Users & Permissions

↓

CRM & Pipelines

↓

Calendars & Communication

↓

Workflows

↓

Snapshots

↓

Client-Specific Integrations

↓

Quality Assurance

↓

Client Launch

Agencies planning to repeat this process should also maintain a GoHighLevel Agency Setup Checklist so important configuration steps are not missed during client onboarding.

Start Your GoHighLevel 30-Day Free Trial →

Do not start by creating random client accounts.

Understand the hierarchy.

A typical HighLevel agency environment looks like:

Agency Account

├── Agency Internal Sub-Account

├── Client A Sub-Account

├── Client B Sub-Account

├── Client C Sub-Account

└── Additional Client Sub-Accounts

HighLevel treats sub-accounts as separate locations/workspaces.

Each client sub-account can contain its own:

Contacts

Conversations

Opportunities

Pipelines

Calendars

Workflows

Forms

Funnels

Websites

Phone Configuration

Email Configuration

Users

and supported integrations.

This separation is one of the foundations of scalable agency operations.

These two concepts should not be confused.

This is the top-level environment used to manage:

Sub-Accounts

Agency Users

Snapshots

SaaS Configuration

Agency Billing

White-Label Settings

and other agency-level functions.

An Agency Sub-Account is a regular HighLevel location designated as the agency's own internal business workspace.

HighLevel specifically distinguishes it from client sub-accounts. It can be used for the agency's own operations and, depending on the plan and configuration, can participate in SaaS, subscriptions, rebilling, and payment-provider configuration.

Conceptually:

Agency Account

= controls the HighLevel agency environment.

Agency Sub-Account

= runs your agency as a business.

Your agency's internal workspace can use HighLevel for:

Agency Leads

↓

Discovery Calls

↓

Proposals

↓

Client Onboarding

↓

Client Management

↓

Retention

This gives your team practical experience with the same system you deploy for clients.

It also gives you a controlled environment for building reusable assets.

The first major agency decision is plan selection.

HighLevel currently publishes three primary plans.

Current plan capabilities differ significantly.

Starter currently provides:

3 Sub-Accounts

Unlimited Contacts

Unlimited Users

Core HighLevel Features

and:

24/7 Support.

This can work for:

Solo Consultants

Very Small Agencies

Testing

or:

Businesses Managing Only a Few Locations

The main agency limitation is obvious:

3 sub-accounts.

If your agency expects to onboard many independent clients, this ceiling becomes restrictive.

Unlimited currently includes:

Everything in Starter

plus:

Unlimited Sub-Accounts

Basic API Access

and:

Eligible Phone & Email Rebilling Without Markup.

For a traditional service agency managing many client accounts, this is often the important structural upgrade.

Instead of:

3 Client Environments Maximum

you can build:

Agency

↓

Client 1

Client 2

Client 3

Client 4

Client 5

...

without the same sub-account ceiling.

Agency Pro currently includes the Unlimited plan plus capabilities such as:

SaaS Mode

Automated Sub-Account Creation

Phone & Email Rebilling With Markup

User/Agent Reporting

and:

Advanced API Access.

This distinction matters.

If the business model is:

Agency Manually Creates Client Account

↓

Agency Delivers Managed Service

Unlimited may be enough structurally.

If the business model is:

Customer Selects SaaS Plan

↓

Customer Pays

↓

Sub-Account Created Automatically

↓

Features Assigned

↓

Usage Rebilling / Markup

then Agency Pro is the appropriate architecture to evaluate.

Use this framework:

Consider:

Starter

Consider:

Unlimited

Consider:

Agency Pro

Do not buy Agency Pro simply because it is the highest plan.

Buy it when its additional architecture supports your revenue model.

Before onboarding clients, configure your own agency identity.

Review areas such as:

Agency Name

Company Information

Logo

Business Details

Authorized Users

Billing

Support Details

and applicable:

White-Label Configuration

Keep naming consistent.

If your agency brand is:

Example Growth

avoid environments containing random labels such as:

My GHL

Test Agency

CRM New

Professional naming reduces confusion as the team grows.

Create or designate the sub-account used for your agency's own operations.

HighLevel now formally distinguishes an Agency Sub-Account from ordinary client locations.

Use the internal workspace for:

Agency CRM

Agency Pipeline

Sales Calendars

Agency Forms

Lead Follow-Up

Onboarding

Internal Automations

and appropriate:

SaaS/Rebilling Configuration

depending on the plan.

Do not use a client's sub-account as your internal agency workspace.

A simple agency pipeline might be:

New Lead

↓

Contacted

↓

Discovery Booked

↓

Qualified

↓

Proposal

↓

Won

or:

Lost

Keep stages tied to meaningful business transitions.

Avoid creating fifteen stages merely because HighLevel allows it.

A prospective client submits a form.

HighLevel can:

Create Contact

↓

Create Opportunity

↓

Assign Salesperson

↓

Send Confirmation

↓

Notify Team

↓

Offer Discovery Calendar

↓

Update Pipeline

This lets your agency test HighLevel on its own sales process before selling similar systems to clients.

Build the calendars your own team needs.

Examples:

Discovery Call

Strategy Call

Client Onboarding

Technical Setup

Account Review

Configure:

Availability

Duration

Buffers

Assigned Users

Timezone

Notifications

and:

Booking Questions

Then test every calendar as an external visitor.

HighLevel distinguishes between agency-level access and sub-account-level access.

Agency team management allows administrators to assign users to appropriate accounts and control their access.

Do not make every employee an unrestricted agency administrator.

Instead, ask:

What does this person actually need to do?

Needs broad control over:

Agency Settings

Billing

Sub-Accounts

Users

SaaS

Snapshots

and strategic configuration.

May need:

Multiple Sub-Accounts

Workflows

Users

Reporting

Client Configuration

but not every financial setting.

May need:

Workflows

Forms

Funnels

Calendars

CRM Configuration

but may not need:

Agency Billing

May primarily need:

Contacts

Opportunities

Conversations

Calendars

Usually needs access only to the appropriate client sub-account and approved modules.

The goal is:

Minimum Access Required to Perform the Role.

HighLevel's current agency permission system can restrict:

Sub-Account Access

Modules

Settings

Billing Actions

Client Management

and other sensitive functions.

Use these controls.

A contractor hired to build workflows does not automatically need access to agency billing.

Every client should generally have a clearly defined sub-account.

Example:

Agency

├── Agency Internal

├── ABC Roofing

├── Smith Dental

├── Peak Fitness

└── Northside HVAC

This keeps:

Contacts

Calendars

Conversations

Workflows

and:

Client Users

separated appropriately.

Use consistent naming.

For example:

Brand Name — City

or:

Brand Name — Location

For multi-location clients:

Acme Dental — Austin

Acme Dental — Dallas

Acme Dental — Houston

Consistent naming becomes increasingly valuable when the agency manages dozens of locations.

Inside a sub-account, HighLevel currently supports two broad roles:

Admin

and:

User

with additional granular permissions.

Administrators can further control module access and settings such as Only Assigned Data.

This means:

Client Owner

does not need the same configuration as:

Sales Representative

May need:

Dashboard

Contacts

Opportunities

Conversations

Calendars

Reporting

May need:

Contacts

Pipelines

Conversations

Calendars

Reporting

May need:

Assigned Contacts

Assigned Opportunities

Conversations

Calendar

May need:

Conversations

Calendars

Contacts

but not:

Workflow Editing

Billing

or:

Advanced Integrations

Build permissions around jobs.

HighLevel's updated Feature Permissions system currently includes more than 80 controllable features for sub-accounts.

An agency can decide whether a client should see areas such as:

AI Agents

Calendars

Opportunities

Phone System

and other supported modules.

This is particularly useful when creating simplified client experiences.

More visible software does not necessarily create more perceived value.

It can create confusion.

If a client only needs:

Contacts

Conversations

Pipeline

Calendar

Reporting

then showing dozens of unrelated modules may make onboarding harder.

Configure the workspace around the service you actually provide.

Client-facing assets may require domains or subdomains.

Potential use cases include:

Funnels

Websites

Booking Pages

Tracking

Branded Login

and other supported assets.

Create a domain naming standard.

For example:

book.clientdomain.com

go.clientdomain.com

crm.agencydomain.com

The exact structure depends on the deployment.

Document DNS changes so the agency can troubleshoot them later.

Do not build every automation before verifying the sending architecture.

Determine:

What domain sends email?

Who is the sender?

Which service handles delivery?

Are DNS records correct?

Are replies monitored?

What is the unsubscribe process?

Then test:

Send

↓

Delivery

↓

Reply

↓

CRM

Do not assume configuration is correct merely because a workflow says “sent.”

Determine how the client will handle:

Phone Numbers

SMS

Inbound Calls

Outbound Calls

Call Routing

Voicemail

and:

Usage Billing

HighLevel's native phone architecture and supported integrations can create ongoing usage costs.

Document those costs before deciding what is included in your agency package.

Do not automatically copy your agency pipeline to every client.

A roofing company might use:

New Lead

↓

Contacted

↓

Inspection Booked

↓

Estimate Sent

↓

Won

A dental clinic may use a different administrative journey.

A B2B agency may use:

Lead

↓

Qualified

↓

Discovery

↓

Proposal

↓

Won

Pipeline architecture should reflect the client's actual process.

For every stage, ask:

Who owns this stage?

What moves a contact into it?

What moves a contact out?

Is movement manual or automated?

What happens if the lead stays here too long?

A pipeline without operating rules becomes a colorful board rather than a management system.

Build calendars around actual appointment types.

Examples:

Consultation

Estimate

Demo

Service Appointment

Sales Call

For each calendar configure:

Assigned Team

Availability

Duration

Buffers

Timezone

Form Questions

Confirmation

Reminder

and:

Rescheduling/Cancellation

Then run test bookings.

Only collect information needed for the process.

A lead form might need:

Name

Email

Phone

Service

Location

Avoid adding twenty fields merely because custom fields are available.

More friction can reduce form completion.

Create a data dictionary.

Example:

Standardize names.

Avoid:

Service

Service Type

Interested Service

Service Requested

all representing the same concept.

Poor data architecture creates poor automation.

Tags are useful but easy to abuse.

Create a naming convention.

For example:

SOURCE-Facebook

STATUS-Qualified

SERVICE-Roofing

AUTOMATION-Nurture

Avoid hundreds of undocumented tags.

Before creating a tag, ask:

Could this be a custom field instead?

Start with essential workflows.

Lead Created

↓

Create Opportunity

↓

Assign User

↓

Send Approved Response

↓

Notify Team

Appointment Booked

↓

Confirmation

↓

Reminder

No-Show

↓

Follow-Up

↓

Rescheduling

Opportunity Won

↓

Stop Sales Nurture

↓

Start Customer Process

Opportunity Lost

↓

Remove Active Sales Follow-Up

↓

Appropriate Long-Term Nurture

Start with core business transitions.

One of the most common agency mistakes is focusing only on triggers.

Every workflow should answer:

When should this automation stop?

Example:

Lead Follow-Up

should stop when:

Appointment Booked

or:

Opportunity Won

or:

Contact Opts Out

or another defined outcome occurs.

Otherwise:

Customer Converts

↓

Old Lead Automation Continues

That damages the customer experience.

When multiple workflows exist, map which ones can send:

SMS

Email

Voicemail

Internal Notifications

and:

AI Responses

A single lead might accidentally enter:

New Lead Workflow

Campaign Workflow

Appointment Workflow

Reactivation Workflow

without proper exclusions.

Use:

Conditions

Tags

Status

Workflow Removal

and appropriate:

Exit Logic

to prevent collisions.

Before creating a reusable snapshot, build one clean source environment.

Call it something clear such as:

MASTER — Home Services

or:

MASTER — Dental

or:

MASTER — Agency Client

Build the reusable configuration there.

HighLevel's current snapshot architecture works this way: you first configure a source sub-account and then create a snapshot from it.

A HighLevel Snapshot is a reusable configuration template.

Current snapshots can capture selected assets including:

Workflows

Funnels

Calendars

Forms

Campaigns

Custom Fields

and additional supported configuration.

This enables:

Master Sub-Account

↓

Snapshot

↓

Client A

Client B

Client C

instead of rebuilding everything manually.

Do not treat snapshots as:

Clone Every Piece of Client Data

They are primarily reusable configuration packages.

Their purpose is:

Standardization

and:

Deployment

not copying every live interaction or customer record.

Do not automatically select everything.

Ask:

Is this reusable?

Good snapshot candidates include standardized:

Workflows

Forms

Funnels

Calendars

Custom Fields

Templates

and other supported configuration.

Client-specific credentials or settings may require separate setup.

HighLevel currently allows Agency Admins to create a new sub-account directly from an existing snapshot.

The process can become:

Account Snapshots

↓

Select Snapshot

↓

Create New Account

↓

Enter Client Information

↓

Sub-Account Created With Snapshot

This can significantly reduce repetitive onboarding work.

HighLevel notes that when a snapshot is loaded into a new sub-account, included funnels and websites are copied as drafts.

They still require appropriate domain connection and publishing before becoming live.

Therefore:

Snapshot Applied

does not mean:

Client Fully Launched

A post-snapshot checklist remains necessary.

HighLevel also states that once a snapshot has been applied, it cannot simply be unloaded as one package.

Individual elements can be changed or removed manually.

This is another reason to test the master account before deploying it widely.

After applying a snapshot, verify:

Business Name

Logo

Company Information

Domains

Email

Phone

Calendars

Assigned Users

Custom Values

Forms

Workflows

Payment Provider

Integrations

Tracking

Client Permissions

Messaging

AI

Never assume a snapshot makes an account production-ready automatically.

A useful model is:

Reusable:

Workflows

Pipelines

Fields

Forms

Templates

Funnels

Unique:

Brand

Domain

Users

Phone

Email

Calendar Availability

Payment Provider

Credentials

Business Policies

This makes onboarding easier to maintain.

Not every agency needs SaaS Mode.

SaaS Mode is useful when the agency wants a model resembling:

Customer Chooses Plan

↓

Subscription

↓

Account Provisioning

↓

Features Assigned

↓

Recurring Software Revenue

HighLevel's current public pricing places SaaS Mode and automated sub-account creation on Agency Pro at $497/month.

Do not confuse this with Unlimited.

Designed for growing agencies.

Key structural capabilities include:

Unlimited Sub-Accounts

Basic API

Eligible Phone/Email Rebilling Without Markup.

Adds:

SaaS Mode

Automated Sub-Account Creation

Markup Rebilling

Advanced API Access

and current additional Pro capabilities.

Choose based on the business model.

If using Agency Pro SaaS Mode, decide what each plan includes.

For example:

CRM

Contacts

Pipeline

Calendar

Everything in Basic plus:

Workflows

Funnels

Reputation

Everything in Growth plus approved:

AI

Advanced Automation

Additional Features

This is only a planning example.

Your actual packages should reflect the services, features, costs, and client market you support.

HighLevel currently lets agencies control sub-account-level features through SaaS plans and client configuration.

A feature must be available at the sub-account level before an individual user can receive permission to access it.

Think of access as:

SaaS Plan / Sub-Account Features

↓

User Role

↓

Individual Permissions

This prevents a user permission from bypassing a disabled client feature.

HighLevel currently supports configurable user limits for SaaS V1 and V2 plans.

SaaS plans allow unlimited sub-account users by default unless an agency enables a specific User Limit.

This can help agencies create pricing such as:

Plan A → 3 Client Users

Plan B → 10 Client Users

Plan C → Larger Allowance

if that structure fits the offer.

Do not confuse:

Vendor Cost

with:

Client Charge

or:

Agency Markup

These are different numbers.

A useful model is:

Underlying Usage

↓

Agency Cost

↓

Client Rebill

↓

Optional Markup Where Supported

HighLevel's current plan structure distinguishes Unlimited's eligible phone/email rebilling without markup from Agency Pro's markup rebilling capability.

Account for usage when designing client packages.

HighLevel contains services that can create usage or additional product costs.

Depending on configuration, these may involve:

Phone

SMS

Email

AI

Premium Workflow Actions

Marketplace Applications

and other paid services.

Your agency pricing should define:

Included

vs:

Usage-Based

vs:

Client-Paid

vs:

Marked Up

before launch.

If the client accepts payments through HighLevel-supported features, connect the appropriate payment environment.

Then test:

Product / Invoice / Payment Link

↓

Payment

↓

CRM

↓

Workflow

↓

Receipt / Notification

Do not test payment infrastructure only after a real customer attempts to pay.

Clients need to understand outcomes.

Build reporting around:

Leads

Appointments

Opportunities

Pipeline Value

Conversions

Communication

and relevant:

Revenue

Do not overwhelm clients with every available metric.

Focus reporting on the questions they actually ask.

Your agency can use HighLevel to automate its own onboarding.

Example:

Opportunity Won

↓

Create Onboarding Task

↓

Send Welcome Information

↓

Collect Business Details

↓

Collect Required Access

↓

Schedule Kickoff

↓

Build Sub-Account

↓

QA

↓

Training

↓

Launch

This creates a repeatable operating process.

Before setup, collect information such as:

Legal/Business Name

Website

Business Address

Timezone

Primary Contact

Team Members

Services

Business Hours

Calendar Requirements

Domains

Communication Requirements

Pipeline Process

Integrations

and:

Brand Assets

Do not chase these details across twenty emails.

Standardize collection.

Clients may need to provide access to external systems.

Do not ask them to send sensitive credentials casually in ordinary messages.

Use an appropriate secure process for:

DNS

Payment Providers

Advertising Platforms

Email Infrastructure

and other systems.

Document:

Who requested access

Why

Who has it

and:

When it should be removed

Before client launch, test as:

Agency Admin

Client Admin

Client User

Lead

and where applicable:

Customer

Different roles reveal different problems.

An agency admin seeing a feature does not prove the client can see it.

Do not test features independently only.

Run:

Ad / Website

↓

Form

↓

Contact

↓

Opportunity

↓

Workflow

↓

SMS / Email

↓

Booking

↓

Reminder

↓

Pipeline Update

↓

Salesperson

This is end-to-end QA.

Also test:

Duplicate Lead

Existing Contact

Missing Phone

Missing Email

Appointment Cancelled

Appointment Rescheduled

No-Show

Opt-Out

Opportunity Won Early

User Unavailable

Integration Failure

A system that works only for the perfect lead is not production-ready.

Log in using test users.

Verify:

Can the salesperson see only what they should?

Can the client change workflows?

Can the client access billing?

Can a contractor see unrelated accounts?

Can users export data unnecessarily?

Are sensitive settings restricted?

HighLevel's agency and sub-account permission systems exist precisely for this type of control.

Check:

Desktop

Tablet

Mobile

Then verify:

Forms

Calendars

Buttons

Tracking

Redirects

Thank-You Pages

SSL

Domain

A beautiful funnel that cannot submit a lead is a failed funnel.

Send test messages to multiple providers where practical.

Check:

Delivery

Sender

Reply

Links

Formatting

Mobile Rendering

Unsubscribe

Do not assume a workflow's successful execution means the recipient saw the email.

Where configured, test:

Outbound SMS

Inbound Reply

Outbound Call

Inbound Call

Routing

Voicemail

Conversation Logging

Opt-Out

and applicable:

Workflow Behavior

Communication infrastructure is part of the customer experience.

Book appointments using different scenarios.

Check:

Available Slot

Unavailable Slot

Timezone

Confirmation

Reminder

Cancellation

Rescheduling

Assigned User

Workflow

Calendar errors can create real operational problems quickly.

Before marking the account live, verify:

Company Details

Users

Permissions

Domains

Phone

Email

Calendars

Forms

Pipelines

Workflows

Integrations

Payment Configuration

Tracking

Reporting

Client Training

QA Complete

A checklist is more reliable than memory.

Do not teach every HighLevel feature.

Teach the client's job.

A salesperson may need only:

Open Conversation

↓

Update Opportunity

↓

Book Appointment

↓

Add Notes

A manager may need:

Pipeline

↓

Reporting

↓

Team Performance

Client training should follow role responsibilities.

For each client, maintain documentation covering:

Account Purpose

Users

Pipelines

Calendars

Workflows

Integrations

Domains

Phone Numbers

Custom Fields

Tags

Snapshots

Billing Model

Important Exceptions

Documentation reduces dependence on the person who originally built the account.

Instead of:

Workflow 1

New Workflow

Copy of Test

use:

LEAD — New Inquiry

APPT — Confirmation

APPT — No Show

SALES — Long-Term Nurture

CLIENT — Onboarding

Naming standards make troubleshooting easier.

Apply the same principle to:

Forms

Calendars

Funnels

Pipelines

Custom Fields

Tags

Email Templates

Snapshots

A scalable agency should be understandable to someone other than the original builder.

Avoid editing critical live assets casually.

Where practical:

Duplicate

↓

Modify

↓

Test

↓

Approve

↓

Deploy

This is particularly important for:

Large Workflows

AI Agents

Payment Flows

Client Funnels

and:

Messaging

One accidental change can affect many contacts.

A master snapshot will evolve.

Use versioning.

For example:

Home Services v1.0

↓

v1.1

↓

v1.2

Document:

What Changed

Why

Who Approved It

Which Clients Need the Update

Do not push changes blindly.

A snapshot is a reusable configuration mechanism.

It should not be treated as a permanent live synchronization layer between your master account and every client account.

When the master architecture changes:

Review Change

↓

Determine Affected Clients

↓

Test

↓

Deploy Appropriate Update

This requires operational management.

Agencies usually focus heavily on onboarding and ignore offboarding.

Document what happens when a client leaves.

Review:

User Access

Domains

Phone Numbers

Data

Integrations

Payment Connections

Automation

SaaS Subscription

Agency Credentials

and:

Client-Owned Assets

The process should reflect your contract and applicable platform requirements.

Create an internal cost model.

For each client:

HighLevel Allocation

Phone

Email

SMS

AI

Premium Actions

Marketplace Apps

Labor

=

Approximate Cost to Serve

Then compare:

Client Revenue

−

Cost to Serve

=

Gross Contribution

A client can look profitable until usage and support are included.

Do not measure success by:

Number of Workflows

Measure:

Response Time

Booking Rate

Show Rate

Lead-to-Sale Conversion

Pipeline Velocity

Workflow Failure Rate

Cost per Appointment

and:

Revenue

Automation should improve a business transition.

Use:

Lead

→ Response

→ Qualification

→ Booking

→ Show

→ Sale

→ Retention

Find the weakest transition.

If:

Lead → Response = strong

but:

Booking → Show = weak

do not build another lead-response workflow.

Improve:

Booking → Show

This creates a more disciplined optimization process.

Several mistakes repeatedly create unnecessary complexity.

Use permissions instead.

Use structured data where appropriate.

Model real business processes.

Process first.

Automation second.

Every workflow needs stop conditions.

Standardize assets from the beginning.

Test complete journeys.

Client-specific configuration remains.

It does not under HighLevel's current public plan structure.

Model costs before setting client pricing.

For a new agency, use this sequence:

1. Choose Plan

↓

2. Configure Agency Account

↓

3. Build Internal Agency Sub-Account

↓

4. Configure Team & Permissions

↓

5. Build CRM Architecture

↓

6. Build Pipeline

↓

7. Build Calendars

↓

8. Build Forms

↓

9. Build Core Workflows

↓

10. Test

↓

11. Create Master Sub-Account

↓

12. Create Snapshot

↓

13. Create Client Sub-Account

↓

14. Apply Client-Specific Configuration

↓

15. Connect Domains / Email / Phone

↓

16. Configure Client Users

↓

17. Run End-to-End QA

↓

18. Train Client

↓

19. Launch

↓

20. Monitor & Optimize

This sequence reduces rework.

Explore GoHighLevel With a 30-Day Free Trial →

Start by choosing the appropriate plan, configure the top-level Agency Account and internal Agency Sub-Account, define team permissions, build a standardized master client environment, create reusable snapshots, and then customize and QA each client sub-account before launch.

An Agency Sub-Account is a normal HighLevel sub-account designated as the agency's own internal business workspace rather than a client's workspace. HighLevel says it can be used for agency operations and, on eligible plans/configurations, SaaS, subscriptions, rebilling, and payment-provider configuration.

HighLevel currently includes up to 3 sub-accounts with its $97/month Starter plan.

Yes. HighLevel's current Unlimited plan costs $297/month or $2,970/year and includes unlimited sub-accounts.

No. Under HighLevel's current public pricing structure, SaaS Mode is included with Agency Pro at $497/month, not the $297 Unlimited plan.

HighLevel currently lists Agency Pro at $497/month or $4,970/year.

Current advertised additions include SaaS Mode, automated sub-account creation, phone/email rebilling with markup, User/Agent Reporting, and Advanced API Access on top of the Unlimited plan.

A Snapshot is a reusable package of selected configuration assets captured from an existing source sub-account. It can contain supported items such as workflows, funnels, calendars, forms, campaigns, custom fields, and other configuration.

No. HighLevel specifically explains that you first configure a source sub-account and then create the snapshot from that account.

Yes. Agency Admins can create a new sub-account from an existing snapshot, allowing supported configuration to be loaded during account creation.

HighLevel currently allows one snapshot during the initial new-account creation process. Additional snapshots can be applied manually afterward.

No. HighLevel states that an applied snapshot cannot simply be unloaded as one package. Individual assets can instead be modified or removed.

Not necessarily. HighLevel states that funnels and websites copied into a new account through a snapshot are loaded as drafts and still require the appropriate domain connection and publishing.

Yes. HighLevel's current Feature Permissions system includes more than 80 controllable features that agencies can enable or disable at the sub-account level.

Yes. Sub-account users can be assigned Admin or User roles and further restricted using granular module permissions and options such as Only Assigned Data.

Yes. SaaS/sub-account feature permissions determine what is available to the overall sub-account, while individual user permissions can further restrict what a particular person can access. A user cannot access a feature disabled at the sub-account level.

Yes. HighLevel currently provides configurable User Limits for SaaS V1 and V2 plans. SaaS plans allow unlimited users by default unless the agency enables a user limit.

HighLevel currently supports converting eligible existing sub-accounts to SaaS Mode by linking or creating the appropriate payment customer and assigning a plan from the SaaS Configurator.

Test the full journey from lead capture through CRM creation, pipeline assignment, messaging, calendar booking, workflow behavior, user permissions, domains, integrations, payment flows where applicable, opt-outs, and reporting.

No. Traditional managed-service agencies may be well served by the Unlimited architecture. SaaS Mode is more relevant when the agency wants automated software subscriptions, account provisioning, feature packaging, and supported rebilling/markup functionality.

A strong GoHighLevel agency setup is not created by turning on every available feature.

It is created by building a repeatable operating system.

Start with:

Correct Plan

↓

Agency Account

↓

Internal Agency Workspace

↓

Team Permissions

↓

Master CRM Architecture

↓

Client Sub-Accounts

↓

Workflows

↓

Snapshots

↓

Client-Specific Configuration

↓

QA

↓

Training

↓

Launch

The plan decision matters.

Current HighLevel pricing separates the primary agency tiers clearly:

Starter — $97/month

→ 3 sub-accounts.

Unlimited — $297/month

→ unlimited sub-accounts, Basic API Access, and eligible phone/email rebilling without markup.

Agency Pro — $497/month

→ SaaS Mode, automated sub-account creation, markup rebilling, Advanced API Access, and additional Pro capabilities.

For many service agencies:

Unlimited

can provide the multi-client structure they need.

For agencies turning HighLevel into a software subscription:

Agency Pro

becomes substantially more important.

After selecting the architecture, standardize deployment.

Build:

One Strong Master Sub-Account

↓

Create Snapshot

↓

Deploy

↓

Customize

↓

QA

HighLevel's current snapshot system is specifically designed to help agencies reuse configuration and create consistent client environments faster.

But automation should never eliminate quality control.

Every new client still needs verification of:

Users

Permissions

Business Information

Domains

Email

Phone

Calendars

Forms

Pipelines

Workflows

Integrations

Payments

and:

Reporting

The scalable agency model is therefore not:

Automate Everything

It is:

Standardize What Repeats

Customize What Is Client-Specific

Test Everything That Matters

As the agency grows, this creates a cleaner operating model:

Standardized Setup

↓

Faster Onboarding

↓

Fewer Configuration Errors

↓

Easier Team Training

↓

Better Client Experience

↓

More Scalable Agency Operations

That is the real value of a well-designed HighLevel agency setup.

Start Your GoHighLevel 30-Day Free Trial →