Getting Started with the SaaS Configurator

Modified on: Tue, 26 May, 2026 at 6:10 AM

TABLE OF CONTENTS


The SaaS Configurator is HighLevel's built-in tool for packaging, pricing, and selling your platform access as a recurring subscription service. Instead of billing clients manually, you create SaaS plans, generate payment links, and let HighLevel handle sub-account creation and onboarding automatically — turning your agency into a scalable SaaS business.


1.  SaaS V1 vs V2 at a Glance

HighLevel supports two billing architectures. You do not have to choose one permanently — they can run side by side. 

See SaaS V1 vs V2 — What's the Difference? for a full architectural comparison.



SaaS V1
SaaS V2
System of recordStripeHighLevel (Agency Sub-Account)
Payment providersStripe onlyStripe, NMI, Square, Authorize.net, Adyen, Mercado Pago, and more
Products managed inStripeHighLevel
Best forStable Stripe setups; agencies needing prorations and coupon deflectionsNon-Stripe payment providers; deeper CRM and automation integration
Not yet in V2Prorations, coupon deflections, self-serve reactivation, payment method updates


Note: SaaS V1 and V2 are two different architectures, not sequential upgrades. V1 remains actively maintained and battle-tested. Choose based on your payment provider and feature needs.





2.  Before You Begin

Complete this checklist before starting setup:

☐  You have the Agency Admin role in HighLevel.

☐  For V1: A Stripe account you can connect via OAuth.

☐  For V2: An existing Agency Sub-Account (a dedicated internal sub-account you own) with at least one supported payment provider enabled under Payments → Integrations.



3.  Connecting Your Payment Provider

3a.  SaaS V1 — Connect Stripe

  1. Go to Agency View → Settings → Stripe.
  2. Click Connect with Stripe and complete the OAuth flow.
  3. Return to Agency View → SaaS Configurator. The Pricing tab is now active and ready for plan creation.



3b.  SaaS V2 — Select Your Agency Sub-Account

  1. Go to Agency View → SaaS Configurator → Configure tab.
  2. Click Select Sub-Accounts.
  3. Choose your Agency Sub-Account from the dropdown and click Add Sub-Account.
  4. Confirm the sub-account has a payment provider configured under Payments → Integrations inside that sub-account.



What is an Agency Sub-Account?
It is an internal sub-account you own and use for operations — separate from your customers' sub-accounts. HighLevel uses it as the billing system of record for all V2 subscriptions.



4.  Creating SaaS Plans

4a.  Create a Plan Category (Required Before First Plan)

Categories group plans into upgrade paths, so customers can move between plans in the same category (e.g., Starter → Pro → Enterprise).

  1. In SaaS Configurator > Advanced settings, click Add new category.
  2. Enter a category name and select a currency.
  3. Click Save.


Tip: If planning to sell to multiple geographies (different currencies), it is recommended to create a separate category for each one, so that the clients can upgrade/downgrade to other plans that have the same currency.




You can create multiple categories for different product lines or currencies. Plans in the same category share an upgrade path.

Important notes:
1. Plans within the same category must use the same currency.
2. Moving a sub-account from one plan to another within the same category requires disabling and re-enabling SaaS. This will result in the loss of wallet data.
3. SaaS plans can technically be moved from one category to another, but this is not recommended because it may impact all associated sub-accounts.


4b.  Create a SaaS Plan

  1. In SaaS Configurator, click + Add your plan.
  2. Select the location (Agency Sub-Account) where the plan will be created. For V1, this step uses your connected Stripe account.
  3. Complete the 9-step plan creation wizard:
    Step
    What to configure
    1. Plan DetailsName, description
    2. CategoryAssign to an upgrade-path category
    3. PricingMonthly price, annual price
    4. Features & SnapshotEnable product features; attach a Snapshot to auto-configure new sub-accounts on purchase
    5. Add-onsOptional paid add-ons customers can self-select
    6. Marketplace AppsThird-party integrations bundled with the plan
    7. Trial & CreditsTrial period (days), complimentary credits: issue on signup, or after trial ends
    8. Usage BillingPer-unit overage charges (e.g., per SMS, per email)
  4. Click Save Plan.





Limits: Agencies can create up to 99 SaaS plans. Do not delete SaaS plans directly inside Stripe — always manage them through SaaS Configurator.



5.  Selling SaaS

5a.  Sell SaaS Through a HighLevel Funnel (Recommended)

For a branded sales experience with a full sales page, you can embed your SaaS plan in a funnel.


For V1 (Stripe-based):

  1. Switch to your selling sub-account.
  2. Go to Payments → Products → Import from Stripe.
  3. Search for your SaaS product and import it. See Import Stripe Products into SaaS Configurator (V1) for detailed steps.
  4. Go to Sites → Funnels, create a new funnel, and add a 1-Step Order Form or 2-Step Order Form using the imported product.


Note: If you update a V1 plan in the SaaS Configurator, you must re-import the product from Stripe into your agency sub-account and update it on the funnel as well.


For V2 (HighLevel-native):

  1. Switch to your Agency Sub-Account.
  2. Go to Payments → Products and open your SaaS product (created during plan setup).
  3. Go to Sites → Funnels, create a funnel, and add an Order Form using the product.




The quickest way to sell a plan is a direct payment link you can share anywhere.

  1. In SaaS Configurator → Plans & pricing, locate your plan card.
  2. Click Copy sale link.
  3. Share the link via email, a proposal, social media, or embed it in a button on any webpage.


When a prospect clicks the link, they are taken directly to a checkout page for that plan.





6.  Onboarding Customers

6a.  New Customer via SaaS Checkout — What Happens Automatically

Once a customer completes checkout, HighLevel handles the rest automatically:

  1. Payment confirmed — HighLevel receives the payment event and begins sub-account creation.
  2. Sub-account created — A new sub-account is provisioned and linked to the customer.
  3. Snapshot applied — If you attached a Snapshot to the plan, it is automatically applied to configure the sub-account (pipelines, calendars, workflows, etc.).
  4. Onboarding email sent — The customer receives an email with their login URL and a link to set up their password.
  5. Subscription active — The sub-account appears in Agency View → Sub-Accounts with status Active (or Trialing if a trial period was set).

Sub-account not created? Common causes: 
• The product was not configured as a SaaS price in the plan wizard 
• Payment was processed in Stripe test mode (not live mode) 
• Customer paid via PayPal (not supported for SaaS)


6b.  Manually Adding SaaS to an Existing Sub-Account

Use this flow when a client already has a sub-account and you want to put them on a SaaS subscription (for example, upgrading a legacy client or processing a sale outside of checkout).

  1. Go to Agency View → Sub-Accounts and open the target sub-account.
  2. Click Manage Client, then open the SaaS tab.
  3. Click Add a SaaS Subscription.
  4. Choose the payment processor (in case multiple of them are setup).
  5. Choose an existing customer profile or create a new one.
  6. Select the plan you want to assign.
  7. (Optional) Click Create a Special Price to set a custom amount, currency, and billing interval for this client without changing the public plan pricing.
  8. Complete payment:
    1. If the selected customer profile already has a payment method attached, then the payment will automatically be attempted immediately after selecting the plan.
    2. If the selected customer profile does not have a payment method attached, then their account will be put on hold and they will see a paywall the next time they login to their account. They can add a card from there to attempt payment.
  9. The sub-account is immediately linked to the subscription after successful payment.



Special Prices are useful for promotional pricing, enterprise agreements, or grandfathered rates. The custom price applies only to this sub-account and does not affect the public plan.



7.  Running V1 and V2 in Parallel

You do not need to choose one architecture exclusively. V1 and V2 plans coexist in the same SaaS Configurator dashboard without conflict.


How it works:

  • Both V1 and V2 plans appear on the Plans and pricing tab in SaaS Configurator.
  • V2 plans are identified by a “V2” badge, and the name of the associated agency sub-account above the plan card.



When to run both:

  • You are migrating from V1 to V2. Keep existing V1 subscriptions running while onboarding new customers through V2.
  • You have clients on Stripe who need V1 features (prorations, coupons) and new clients who need a non-Stripe payment provider.


Managing payment failures across both systems:


Where failures appear
How to resolve
V1Stripe dashboardRetry payment in Stripe or contact the client to update their card
V2Agency Sub-Account → Payments moduleRetry or update payment method in the Payments module



Article
What it covers
SaaS V1 vs V2 — What's the Difference?
Full architectural comparison; which version to choose
SaaS Mode Full Setup Guide & FAQ (V1)
Deep dive into V1 setup, Special Prices, and troubleshooting
Guide to SaaS Plan Creation, Sales & Customer Onboarding (V2)
Deep dive into V2 plan creation and the Payments module
Import Stripe Products into SaaS Configurator (V1)
Migrate existing Stripe products to HighLevel; link existing subscriptions
Configure Automatic Tax Collection for SaaS Subscriptions
V1/Stripe only — enable jurisdiction-based tax collection via Stripe Tax














Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article