GoHighLevel SaaS: Features, Setup & Practical Guide

GoHighLevel SaaS Mode lets agencies package HighLevel features into their own recurring software plans, apply white-label branding, automate customer account creation, manage subscriptions, configure feature access, and rebill supported usage from one SaaS management system. Instead of selling only marketing services, agencies can use Go High Level to create subscription packages that give clients access to selected CRM, automation, communication, website, funnel, calendar, reputation, and other platform features.

The core of GHL SaaS Mode is the SaaS Configurator. HighLevel describes it as the built-in system for packaging platform access into recurring SaaS subscription plans. Agencies can configure pricing, product features, snapshots, add-ons, trials, credits, and usage billing while controlling how customers purchase and access their sub-accounts.

HighLevel currently supports two different SaaS billing architectures: SaaS V1, which remains Stripe-based, and SaaS V2, which uses an Agency Sub-Account as the billing system of record. They are separate architectures rather than two names for the same billing setup, so agencies should understand which model they are configuring before creating plans.

For an agency, the practical model can look like Customer Chooses Plan → Subscription Created → Sub-Account Provisioned → Snapshot Applied → Features Enabled → Customer Uses Branded Platform → Recurring Billing and Usage Management.

For a dedicated resource covering the white-label business model, see our complete guide to GoHighLevel SaaS Mode.

Test HighLevel's CRM, automation, account structure, branding, and SaaS capabilities before building your customer packages. HighLevel currently operates official promotional pages offering an extended 30-day trial, including promotional access to SaaS Pro on selected offers.

Start Your GoHighLevel 30-Day Free Trial →

GoHighLevel SaaS Mode is HighLevel's system for agencies that want to package and resell software access to client sub-accounts under a recurring subscription model. The agency defines what clients receive, how the plans are priced, how accounts are provisioned, and which supported usage costs are rebilled.

This differs from simply creating a normal HighLevel sub-account for a service client. With SaaS Mode, the agency can formalize the software offer into plans and automate more of the subscription lifecycle.

HighLevel's current SaaS Configurator supports monthly and annual pricing, feature selection, snapshots, add-ons, Marketplace apps, trials and credits, and usage billing. At least one product feature must be selected before a SaaS plan can be saved.

For agencies already selling CRM implementation, automation, websites, funnels, appointment systems, or reputation management, SaaS Mode can provide a recurring software layer alongside those services.

Go High Level SaaS works by connecting a subscription plan with a customer sub-account, feature configuration, billing architecture, and automated provisioning process.

The agency first determines what it wants to sell. It can then create related pricing plans inside the SaaS Configurator, define the included features, optionally associate a snapshot, configure usage rules, and provide customers with a purchase path.

When the customer purchases a plan through a supported setup, HighLevel can provision the relevant account and establish access according to the SaaS plan configuration.

A simplified customer journey is:

Pricing Page → Select SaaS Plan → Checkout → Subscription → Client Sub-Account → Snapshot/Features → Onboarding → Ongoing Billing

This makes the SaaS Configurator more than a pricing-table builder. It controls important parts of how the agency packages and delivers the software product.

GoHighLevel SaaS Mode and traditional agency services solve different business needs and can also be combined. A traditional service model normally charges clients for work performed by the agency, while a SaaS model charges recurring access to a configured software environment.

For example, an agency may manually build campaigns, manage advertising, write content, or optimize funnels for a monthly service fee. A SaaS customer may instead receive access to a branded CRM, pipeline, automation system, calendars, and templates that the customer uses directly.

The models do not have to be mutually exclusive. Agencies can offer software-only tiers, software plus onboarding, or higher plans combining software with managed services.

The important distinction is that SaaS Mode does not automatically make the business passive. Customers may still need onboarding, support, configuration, training, migration, and strategic assistance.

The GHL SaaS Configurator is the central interface for creating and managing recurring SaaS plans inside HighLevel. It controls how plans are grouped, priced, configured, sold, and connected to client account access.

HighLevel's September 2026 documentation describes the Configurator as the tool agencies use to define pricing, features, snapshots, add-ons, usage billing, trials, credits, and other plan settings.

Each plan should have clear customer-facing information so buyers can understand what they are purchasing.

A plan may include its name, recurring price, billing frequency, included features, optional add-ons, account configuration, and usage rules.

The plan should correspond to an actual customer segment rather than simply offering three arbitrary price points.

Plan categories group related SaaS plans and help define upgrade and downgrade paths. HighLevel states that plans within the same category should use the same currency, while businesses selling in different currencies should use separate categories.

For example, an agency could create one category containing Starter, Growth, and Pro plans.

If another product line serves a fundamentally different market or currency, it may belong in another category.

HighLevel also allows agencies to control plan hierarchy within categories. The order helps determine which plans represent upgrades or downgrades for customers.

This makes it possible to create a logical progression instead of forcing customers to cancel one product and buy an unrelated subscription when they need more functionality.

GoHighLevel SaaS V1 and SaaS V2 are separate billing architectures, so agencies should understand the difference before building their pricing model.

HighLevel's current documentation states that SaaS V1 remains Stripe-based. SaaS V2 instead uses an Agency Sub-Account as the billing system of record with a supported payment provider configured there.

SaaS V1 uses Stripe at the agency level as the subscription system of record.

The agency connects Stripe, creates SaaS plans, and can sell those products using supported checkout flows. HighLevel also supports importing relevant Stripe products for V1 configurations.

This architecture remains relevant for agencies already operating Stripe-based SaaS subscriptions.

SaaS V2 uses an Agency Sub-Account for billing rather than making Stripe at the agency level the central subscription record.

HighLevel instructs agencies using V2 to configure a supported payment provider under Payments → Integrations in the designated Agency Sub-Account before building the corresponding plans.

The choice affects how products, subscriptions, and billing records are maintained, so it should be made before a large SaaS catalog is created.

Setting up GoHighLevel SaaS Mode requires deciding on the billing architecture, preparing branding and payments, creating plan categories, building SaaS plans, defining features, and testing the complete customer purchase and onboarding journey.

Do not start by creating random plans and deciding the business model later. First define who the software is for and what problem each plan solves.

HighLevel currently identifies Agency Pro as the plan that includes SaaS Mode and enhanced rebilling functionality. Its support documentation lists the Pro plan at $497/month and describes SaaS Mode as one of its key features.

Before beginning setup, make sure the appropriate Agency Admin permissions and billing configuration are available.

For SaaS V1, HighLevel requires access to a Stripe account. For SaaS V2, the billing Agency Sub-Account needs a supported payment provider under Payments integrations.

Decide what the customer is actually buying.

A generic package called "CRM Software" may be harder to position than a product built around a specific use case such as lead management for contractors, appointment automation for clinics, or follow-up software for real estate teams.

Define the target user, main problem, included features, level of onboarding, support model, and any usage-based charges before setting prices.

The software configuration should reflect the promised customer outcome.

Inside the SaaS Configurator, create the category that will contain related plans.

HighLevel's current process uses SaaS Configurator → Advanced Settings → Add New Category, where the agency names the category and assigns its currency.

Keep related plans together so upgrades and downgrades remain logical.

Select Add Your Plan inside SaaS Configurator and configure the relevant billing architecture or payment processor.

HighLevel's current plan editor supports plan information, category, monthly or annual pricing, product features, snapshots, add-ons, Marketplace apps, trials, credits, and usage billing.

Do not create feature differences merely to make the pricing table longer. Each higher tier should solve a meaningful additional need.

The Configurator controls which product features belong in the customer's plan. HighLevel currently requires at least one feature before the plan can be completed.

An entry plan might focus on essential CRM and appointment functionality, while a higher plan could include more advanced automation or other premium capabilities.

Exactly which features belong in each tier depends on the niche and value proposition.

Snapshots can help agencies deploy preconfigured account assets instead of giving every new customer a completely empty system.

An industry-specific snapshot might contain pipelines, workflows, forms, funnels, calendars, templates, or other supported configuration designed for a particular use case.

This can shorten the time between purchase and the customer's first useful experience.

Snapshots should still be tested carefully because a setup that works for one niche may not suit another.

HighLevel's current SaaS Configurator includes settings for plan trials, complimentary credits, and optional add-ons.

Use these features as part of a deliberate pricing strategy rather than enabling everything automatically.

An optional add-on should represent an identifiable enhancement a customer can understand and choose.

Some HighLevel services generate variable costs based on actual client usage. Rebilling allows agencies to pass supported costs to the relevant sub-account instead of absorbing every usage charge.

HighLevel currently distinguishes between rebilling at cost and rebilling with an agency markup. Its support documentation states that rebilling with markup is available on Agency Pro and forms part of SaaS Mode.

The agency should clearly understand what usage it is paying for, what the client is charged, and where markup is applied.

A SaaS plan still needs a purchase path.

HighLevel currently supports direct SaaS checkout links as well as funnel-based selling patterns, depending on the SaaS architecture. For SaaS V1, plans can be imported into an appropriate selling sub-account and used in supported funnel order forms.

The pricing and checkout experience should explain what the subscription includes and what happens immediately after purchase.

Before sending paid traffic or onboarding real customers, test the experience from purchase through account access.

Verify plan pricing, payment processing, account provisioning, feature access, snapshots, branding, onboarding emails, usage settings, and cancellation or plan-change behavior.

A SaaS business depends on repeatability, so an onboarding error that affects one test customer could otherwise affect every new subscriber.

White labeling lets agencies present the HighLevel software experience using their own brand identity rather than relying only on HighLevel's default customer-facing branding.

This can include elements such as the brand name, logo, white-label domain, themes, and other supported identity settings.

The objective is consistency. Customers should understand which company is selling and supporting their software environment.

A white-label domain can provide customers with a branded login destination.

For example, instead of directing customers to an unrelated platform domain, the agency can configure an address associated with its own software brand where supported.

Domain and DNS configuration should be completed carefully because login access depends on it.

The platform experience should use consistent branding across the major customer touchpoints.

HighLevel's current branding capabilities include elements such as logos, brand names, themes, email information, domains, privacy and terms URLs, and certain custom styling options.

Branding should improve clarity rather than disguise the responsibilities between the agency and its customers.

GHL SaaS Multi-Brands is a newer HighLevel feature designed to let agencies operate more than one branded SaaS identity from a single agency account.

As of August 2026, HighLevel documented Multi-Brands as supporting up to two independent brands, each with its own branding, domain, and white-label configuration. HighLevel described the feature as being in Private Beta at that time, with broader beta availability planned.

This can be useful when an agency wants to operate distinct products for different industries or customer segments without maintaining completely separate agency accounts.

HighLevel allows brands to be associated with SaaS plan categories. When a sub-account purchases a plan from a category mapped to a brand, that branding can be applied automatically.

For example, an agency might operate one SaaS brand for real estate and another for home services.

Each could have a different name, logo, domain, and customer presentation while remaining managed from one broader agency environment.

Because this feature has been evolving through beta, agencies should verify current availability in their own account before building a launch plan around it.

Test the account structure, CRM, automation, snapshots, branding, and billing workflows before packaging HighLevel into your own customer plans.

Claim Your GoHighLevel 30-Day Free Trial →

GoHighLevel SaaS pricing should be based on customer value, included functionality, support requirements, and usage costs rather than copying another agency's pricing table.

There is no universal Starter, Professional, and Enterprise price that is automatically correct for every business.

An agency selling software to solo consultants may have a very different willingness-to-pay environment from one selling a highly configured platform to multi-location companies.

Start by calculating both fixed and variable costs.

Your fixed platform subscription is only one expense. Other costs may include communication usage, AI consumption, premium workflow executions, domain services, support, onboarding labor, payment processing, third-party apps, and client-specific services.

An entry tier should deliver a complete enough experience for the intended customer to accomplish a meaningful task.

Avoid intentionally making the lowest plan unusable simply to force an upgrade.

Instead, define a narrower customer use case. The entry plan may target businesses that need core lead management and appointment functionality without advanced add-ons.

The middle tier can serve customers with more complex workflows or larger usage requirements.

This might introduce additional automation, marketing functionality, reporting, or other capabilities relevant to the target niche.

The difference should be easy to explain without requiring customers to read a long technical feature table.

Premium plans can combine broader software access with higher-touch onboarding, implementation, custom configuration, or support.

This is where agencies need to distinguish software revenue from service revenue internally. Adding unlimited custom work to a software subscription can make margins difficult to manage.

Define clear boundaries around what is included.

GoHighLevel SaaS rebilling lets agencies pass eligible usage-based platform costs to client sub-accounts, and Agency Pro can apply markup to supported rebilled services.

HighLevel explains that the agency is generally charged through its Agency Wallet first for relevant usage. When rebilling is enabled, the sub-account is subsequently charged for the usage it generated.

This is important because a software subscription can have variable operating costs.

If a customer uses significantly more communication or AI resources than another customer, a single flat fee may not always reflect the agency's underlying cost structure.

Rebilling at cost passes supported usage charges to the sub-account without adding a profit margin.

HighLevel currently states that rebilling without markup is available on Unlimited and Agency Pro for supported services, although individual products can have their own requirements.

Agency Pro can apply markup to supported rebilling as part of SaaS Mode.

For example, when a supported usage service generates an underlying cost, the agency can configure the SaaS arrangement so the client pays a higher amount, with the difference contributing to agency revenue.

Actual pricing should remain transparent enough that customers understand what they are purchasing and how variable usage is charged.

HighLevel also supports domain purchase and rebilling functionality.

Its current documentation states that domain purchasing can be made available to sub-accounts and that eligible $497 SaaS agencies can add markup to domain purchase costs.

This can reduce friction for customers who need a domain as part of their website or funnel setup because they may not need to manage the purchase entirely outside the platform.

Domain availability, renewal, ownership expectations, and billing terms should still be communicated clearly.

HighLevel also provides rebilling controls for eligible Premium Workflow Features.

For SaaS agencies on the qualifying plan, supported premium execution costs can be passed to clients with a configured markup.

This matters for agencies whose software packages depend heavily on automation because workflow execution can become a variable cost as client activity grows.

Do not assume every platform feature follows the same rebilling rules. Review HighLevel's current documentation for each paid feature before determining customer pricing.

GoHighLevel's SaaS Configurator now supports selecting specific AI Employee tiers when AI Employee is included inside a SaaS plan.

HighLevel documented an updated tier selector in July 2026, allowing agencies to choose between available AI Employee tiers such as Growth or Unlimited rather than using a simple on/off toggle.

This illustrates why SaaS plan configuration should be reviewed regularly. HighLevel continues adding new product tiers and billing options, and an old SaaS package may not reflect the current platform.

Agencies should decide whether AI functionality belongs inside the base subscription, a premium tier, or an optional add-on according to customer demand and cost structure.

GoHighLevel snapshots can reduce the amount of configuration required after a new SaaS customer subscribes by providing a prebuilt account starting point.

A niche SaaS offer becomes more useful when the customer receives an environment designed around their business rather than an empty CRM.

For example, a home-services snapshot could include a lead pipeline, contact fields, appointment workflows, estimate follow-up, review requests, and basic forms.

A different niche may require a completely different account configuration.

The snapshot should support the product promise. Loading hundreds of unused assets into every new account may make the software harder to understand instead of more valuable.

Go High Level SaaS becomes easier to scale when repeatable onboarding tasks are standardized instead of relying on manual setup for every subscriber.

HighLevel's Configurator is designed to support automated provisioning after successful SaaS checkout, including sub-account creation and configured plan access.

The agency should then decide what customers need after account creation.

A useful onboarding journey might include account credentials, a short getting-started sequence, configuration instructions, video tutorials, an onboarding call where appropriate, and clear support channels.

Avoid overwhelming new customers with every feature on day one.

Help them reach the first useful outcome quickly, then introduce more advanced capabilities later.

Selling a GHL SaaS plan requires more than publishing a feature list because buyers usually care about the business problem the software solves rather than the underlying HighLevel configuration.

A niche-focused offer can make the value proposition easier to understand.

Instead of selling "CRM + workflows + calendar + reputation management," an agency could describe the practical outcome those components create for the intended customer.

The software still needs accurate feature information, but positioning should translate technical capabilities into a useful business process.

HighLevel supports direct SaaS checkout links as one sales route.

These can be useful when the customer has already seen the offer and simply needs a straightforward subscription checkout.

HighLevel also supports selling SaaS through funnel-based approaches. For SaaS V1, its current guide describes importing the Stripe SaaS product into a selling sub-account and placing the relevant product on a supported order form.

A funnel gives the agency more room to explain the offer, compare plans, answer objections, and present checkout as part of a complete sales journey.

Customers' requirements can change, so plan architecture should account for upgrades and downgrades from the beginning.

HighLevel's SaaS Configurator supports categories and plan levels that determine compatible plan changes. Agencies can also reorganize certain existing plan category and level settings without deleting live plans.

For example, a customer may begin on a basic plan and upgrade once they need additional features.

A logical hierarchy makes that transition easier to manage than maintaining unrelated subscription products with no defined relationship.

Test plan changes before promoting them to customers because billing, access, and subscription synchronization need to remain consistent.

Agencies do not necessarily need to build the SaaS business only around completely new customers.

Existing clients may already use HighLevel sub-accounts as part of a managed service arrangement. HighLevel includes processes for converting existing sub-accounts into SaaS subscriptions, and its current SaaS documentation also supports linking eligible existing Stripe subscriptions in V1 configurations.

The commercial transition should still be handled carefully.

An existing client paying for managed services should understand how the new software subscription changes their billing, support, access, or responsibilities.

Do not simply change the account structure without aligning the customer agreement and onboarding experience.

Go High Level SaaS is particularly suited to niche positioning because agencies can combine feature selection, snapshots, branding, and onboarding around one type of customer.

A generic CRM can require extensive explanation. A configured system designed around a specific industry can communicate its use case more clearly.

An agency serving dental practices might prioritize appointment booking, lead follow-up, missed-call processes, reputation management, and patient inquiry pipelines.

A real-estate-focused SaaS package might emphasize lead routing, pipelines, appointment scheduling, follow-up automation, and listing-related workflows.

The underlying platform may be similar, but the customer experience, snapshot, training, and positioning can differ substantially.

HighLevel also provides SaaS Configurator API endpoints for advanced agencies and developers that need programmatic control over parts of the SaaS operation.

HighLevel describes its SaaS Configurator Public API as supporting tasks such as querying plans, managing subscriptions, and enabling SaaS Mode for multiple sub-accounts.

Potential use cases include custom dashboards, provisioning systems, integration with external business applications, subscription automation, and larger account migrations.

The API is an advanced capability rather than something every new SaaS agency needs immediately.

A smaller SaaS business may be better served by getting its plans, onboarding, positioning, and customer support process working reliably before investing in custom development.

HighLevel also offers a White-Label Desktop App capability that can provide customers with a more branded desktop experience across supported desktop operating systems.

The current customizer can configure items such as app name, icon, theme, login title, subtitle, and other visual assets before the app is submitted for building.

This is separate from the core question of whether the SaaS offer itself provides value.

An app icon and branded login screen may improve presentation, but they cannot compensate for weak onboarding or an unclear product.

The most common GoHighLevel SaaS Mode mistakes come from weak positioning, poorly planned pricing, unclear usage costs, overcomplicated plans, and insufficient onboarding.

One mistake is creating the plans before defining the customer. Feature selection becomes much harder when the agency does not know which problem the product is supposed to solve.

Another is copying another SaaS agency's price points without understanding its support costs, niche, customer acquisition model, and usage expenses.

Agencies should also avoid assuming that every customer will understand HighLevel immediately after receiving login access. A technically working account is not the same thing as successful onboarding.

Rebilling deserves close attention. Communication, AI, premium workflows, domains, and other paid services can have separate rules. Failing to understand variable costs can create unexpected expenses.

Finally, avoid claiming that SaaS revenue is automatically high-margin or passive. Customer acquisition, support, onboarding, churn, payment fees, variable usage, and staff costs all affect the actual economics.

Optimizing a GHL SaaS business means improving the product, onboarding, pricing, customer usage, and retention process rather than simply adding more HighLevel features.

Start by examining activation. Can new customers reach a useful result soon after subscribing? If not, improve the snapshot and onboarding flow before adding more features.

Review which features customers actually use. A complicated plan may look valuable on a pricing table while making the product harder to understand.

Monitor variable costs so pricing remains sustainable as usage increases.

Review support requests. Repeated questions often reveal unclear onboarding or a product configuration that can be simplified.

Plan upgrades should follow genuine customer growth. Higher tiers work better when they unlock capabilities customers actually need rather than artificial restrictions.

Finally, review the product whenever HighLevel changes its SaaS capabilities. The 2026 Configurator now includes evolving features such as SaaS V2, Multi-Brands, updated AI Employee tier selection, and expanded SaaS management tools.

GoHighLevel SaaS Mode lets agencies package HighLevel software capabilities into recurring plans for client sub-accounts, including configurable features, pricing, snapshots, add-ons, usage billing, and automated provisioning.

The SaaS Configurator is HighLevel's built-in management system for creating and managing SaaS plans. Agencies can configure categories, prices, product features, snapshots, trials, credits, add-ons, Marketplace apps, and usage billing.

HighLevel currently identifies the Agency Pro $497 plan as the plan that includes SaaS Mode and advanced rebilling functionality.

SaaS V1 uses Stripe as the billing system of record, while SaaS V2 uses a designated Agency Sub-Account with a supported payment provider. HighLevel treats them as separate billing architectures.

Yes. HighLevel's SaaS Configurator supports automated provisioning of customer sub-accounts after successful SaaS checkout according to the applicable configuration.

Yes. Snapshots can be associated with SaaS plans so new customer accounts can receive predefined configuration rather than beginning entirely empty.

Yes. HighLevel supports rebilling for eligible usage. Its current pricing and billing documentation distinguishes rebilling at cost from rebilling with markup, with markup available through the Agency Pro SaaS model for supported services.

Yes. HighLevel's SaaS plan configuration supports monthly and annual subscription pricing.

Yes. The current SaaS Configurator supports optional add-ons and eligible Marketplace applications as part of SaaS plan configuration.

HighLevel documented SaaS Multi-Brands in 2026, allowing up to two independent brand identities within one SaaS account. The feature was still being rolled out through beta stages when HighLevel published its August 2026 documentation, so current account availability should be checked before relying on it.

Yes. HighLevel offers public SaaS Configurator endpoints for advanced use cases such as plan querying, subscription management, SaaS enablement, provisioning automation, and custom integrations.

Yes. HighLevel currently maintains official promotional landing pages offering an extended 30-day free trial. HighLevel also has promotional offers specifically advertising a 30-day trial of SaaS Pro for eligible new customers.

GoHighLevel SaaS Mode gives agencies the infrastructure to package HighLevel functionality into recurring software plans, apply white-label branding, configure customer access, automate sub-account provisioning, manage subscriptions, and rebill supported usage. The SaaS Configurator provides the central system for controlling pricing, plan categories, features, snapshots, add-ons, trials, credits, and usage rules.

The strongest SaaS offer starts with a clearly defined customer rather than a large feature list. Decide which problem the software solves, configure a useful starting environment, establish understandable pricing, and make onboarding easy enough for customers to reach value quickly.

For Go High Level SaaS, recurring revenue does not remove the need for customer support, acquisition, account management, or careful cost control. Agencies still need to understand variable usage, payment processing, support requirements, churn, and the operational work behind the subscription.

As the business grows, GHL SaaS Mode can support more advanced models through upgrade paths, rebilling, niche snapshots, Multi-Brands, AI plan options, APIs, and white-label experiences. The advantage comes from using those capabilities to create a repeatable software product—not simply enabling every available feature.

Explore HighLevel's CRM and automation platform, test account configuration and branding, and evaluate how the SaaS model could fit your agency before building customer plans.

Start Your GoHighLevel 30-Day Free Trial →