GoHighLevel SaaS Mode: How to Set It Up and Price It

GoHighLevel SaaS Mode lets an agency resell the platform as its own branded software product, with new client sub-accounts provisioned automatically when someone signs up and pays through a connected Stripe checkout. It requires the Agency Pro plan at $497/mo, and it’s a different technical setup from simply reselling sub-accounts manually on the cheaper Unlimited plan. The part most setup guides skip is the full cost stack behind the number that actually matters: after the $497 platform fee, Stripe’s processing cut, and usage-based rebilling costs come out, how many paying clients does it take before SaaS Mode is actually profitable, not just generating revenue?

What SaaS Mode actually is

SaaS Mode is a feature set bundled into GoHighLevel’s Agency Pro tier that automates client onboarding and billing for agencies reselling the platform under their own brand. Per GoHighLevel’s official pricing page, Agency Pro ($497/mo) adds “SaaS Mode, Automated Sub-Account Creation, Rebill Phone & Email with Markup, User/Agent Reporting, Advanced API Access” on top of everything included in the lower tiers.^[1] That same upgrade is also the one that unlocks the full GoHighLevel white label experience: a custom login domain, a rebranded mobile app, and a client-facing portal that never shows the GoHighLevel name anywhere a customer can see it.

That’s a meaningful jump from how most agencies start. The Unlimited plan ($297/mo) already gives unlimited sub-accounts and lets an agency rebill phone and email usage to clients, but only at cost, with no markup allowed, and every sub-account has to be created and configured by hand. SaaS Mode changes both of those constraints: a client can buy a plan through a Stripe-connected checkout, and GoHighLevel automatically spins up their sub-account from a pre-built template, no manual provisioning required. The agency can also apply a markup to usage-based rebilling instead of passing it through at cost.

Mechanically, the flow looks like this: a customer buys through a Stripe-connected checkout page, funnel, or the SaaS Configurator’s own plan page. GoHighLevel provisions a new sub-account from a Snapshot you’ve built in advance. From there, the Stripe-to-HighLevel sync handles the ongoing billing lifecycle, upgrades, downgrades, cancellations, and dunning, without the agency manually touching each client’s billing record.

For the deeper mechanics of how a provisioned sub-account and its cloned snapshot actually behave once a client is live, including how permissions, pipelines, and automations inherit from the parent template, see aibrevo’s guide to GoHighLevel sub-accounts.

What each plan tier unlocks

The chart below shows why Agency Pro is the tier that matters for this decision, not a marginal upgrade from Unlimited.

SaaS V1 vs SaaS V2: which one are you actually setting up?

The technical setup differs depending on which version of SaaS Mode your agency runs, and per HighLevel’s SaaS Mode FAQs, the platform doesn’t let you run both at once.^[2] SaaS V1 connects a single Stripe account at the agency level: every client sub-account bills through that one Stripe connection, and it’s the simpler setup for an agency that’s fine standardizing on Stripe as its only payment processor. SaaS V2 supports four processors, Stripe, NMI, Authorize.net, and Square, configured individually per sub-account, which matters if you’re onboarding clients who already have a preferred processor or need one of those alternatives for compliance or regional reasons.

Most new agencies should default to V1 unless they have a specific reason to need multi-processor support. V2’s per-sub-account configuration adds real setup overhead, since payment processing has to be connected and tested separately for each client rather than once at the agency level. The tradeoff usually shows up first with clients in regulated or higher-risk categories, think certain financial services, supplement, or CBD niches, where a client’s existing merchant account with NMI or Authorize.net may already be approved for that category and switching them to a fresh Stripe account could mean re-underwriting from scratch. V2 also matters for agencies onboarding clients outside the US who need Square’s or Authorize.net’s regional support rather than Stripe’s.

If you’re not sure which version an existing GoHighLevel account is already running, that’s worth confirming with HighLevel support before building out pricing tiers, since migrating between versions later isn’t a simple settings toggle. In practice, a V1-to-V2 migration means reconnecting payment processing for every existing sub-account individually rather than flipping one agency-level switch, and any client billed through the old connection has to be handled carefully so an active subscription doesn’t silently break mid-cycle. That’s worth deciding deliberately before the first paying client signs up, rather than revisiting the choice once ten sub-accounts already exist.

Step-by-step: setting up SaaS Mode

1. Upgrade to Agency Pro. SaaS Mode isn’t available on Starter or Unlimited, so this is the first and non-negotiable step, at $497/mo or $4,970/yr (roughly two months free on the annual plan).

2. Connect Stripe in live mode. From the agency account, go to Settings → Payments → “Connect to Your Stripe Account” and authorize the connection through Stripe’s OAuth flow. Per HighLevel’s support documentation on connecting Stripe, this has to be done in live mode, not test mode, before real client checkouts can process.^[3] Have your Stripe account already fully verified, business details, bank account, and tax information filed, before starting this step; a Stripe account still pending verification will let you authorize the OAuth connection but won’t process real charges, which is a confusing failure mode to hit for the first time during a client’s actual signup.

3. Build a white-label domain and branding. Point a subdomain (something like app.youragency.com) at GoHighLevel and upload your logo and brand colors so clients interacting with the platform never see the GoHighLevel name. This is what makes the “resell it as your own software” pitch actually hold up. Set up the custom domain’s DNS records (typically a CNAME) ahead of time, since propagation can take anywhere from a few minutes to 24-48 hours, and testing branding on a domain that hasn’t finished propagating is a common source of “it’s not working” confusion during setup.

4. Build and test a Snapshot. The Snapshot is the template — pipelines, automations, funnels — that gets cloned into every new client sub-account automatically. A generic or untested Snapshot is one of the more common ways a new client’s first experience goes badly, since whatever’s broken in the template gets replicated into every account it’s cloned into. Build the Snapshot inside a dedicated test sub-account first, run every automation and pipeline stage through at least one full cycle there, and only then push it live as the template new signups actually receive. Skipping that dry run means the first person to discover a broken trigger is a paying client, not you.

5. Configure pricing tiers in the SaaS Configurator. Set plan names, monthly and annual price points, and which Snapshot or feature set each tier provisions. This is also where the pricing decisions in the next section get implemented. Decide up front whether each tier maps to a different Snapshot (different automations and pipeline depth per tier) or the same Snapshot with feature gating, since that decision shapes how much ongoing maintenance you take on as tiers evolve independently.

6. Set usage-based rebilling markup. Inside Agency Pro’s rebilling settings, set the markup you’ll apply to SMS, email, and call-minute costs. GHL consultants commonly cite an illustrative multiplier range of roughly 1.05x to 2x, though this figure comes from practitioner setup guides, not an official GoHighLevel recommendation, and the right multiplier depends heavily on your niche and competitive positioning. This is also the step most new agencies rush or skip entirely, and it’s the one that quietly erodes margin fastest once a heavy-texting client signs up, since a client sending thousands of SMS campaigns a month costs meaningfully more to serve than the “average” client the flat resale price was modeled against.

7. Test a full sample checkout end-to-end. Run a complete signup through Stripe test mode, then again in live mode, before sending real traffic to a checkout page. Confirm three things specifically: the new sub-account actually provisions from the correct Snapshot, the branded confirmation and receipt emails go out under your domain and not GoHighLevel’s, and a test cancellation correctly stops billing rather than leaving a phantom subscription active. Practitioner estimates put hands-on setup time around 2-4 hours for an agency with an existing Snapshot, with a full launch achievable within 5-7 business days, though this is an unverified planning estimate, not a GoHighLevel SLA.

Agencies that would rather have the Snapshot, branding, and SaaS Configurator build done for them instead of self-built can see what that looks like on aibrevo’s GoHighLevel implementation services page.

The full cost stack behind “profit”

This is where most SaaS Mode pricing guides stop short. It’s common to see a claim like “two clients at $297/mo covers your platform cost,” but that statement ignores two cost layers that eat into it before you’ve actually broken even: Stripe’s processing fee and usage-based rebilling costs.

Stripe charges its standard rate of 2.9% + $0.30 per successful US card transaction, published on Stripe’s own pricing page and subject to change, so it’s worth confirming the current rate before finalizing your pricing model.^[4] On top of that, GoHighLevel applies a flat 5% markup on carrier fees at the location level for SMS and MMS, regardless of whether an agency has set its own rebilling markup, a detail specified in HighLevel’s SMS/MMS cost-calculation documentation.^[5] The underlying SMS costs themselves come from Twilio’s pricing, since GoHighLevel’s phone infrastructure runs on Twilio, plus a carrier fee that varies by number type. For the full, current per-unit rate table across SMS, voice, and email, aibrevo’s GoHighLevel pricing 2026 guide breaks down every metered Agency Wallet charge sourced directly from HighLevel’s own support docs.

Here’s what that looks like laid out as a full cost stack for an illustrative 10-client scenario, not a verified case study:

The illustrative usage figure of roughly $30/client accounts for a light-to-moderate mix of SMS, email, and call minutes with markup applied; a client running heavy SMS campaigns could push that number meaningfully higher, which is exactly the underpricing risk consultants flag most often. The core lesson holds regardless of the exact multiplier: Stripe’s fee is a small, predictable percentage, but usage costs scale with how your clients actually use the platform, and a flat resale price with no usage modeling is where margin erosion tends to happen unnoticed.

Break-even math at illustrative resale price points

The question every agency actually wants answered is some version of “how many clients before this pays for itself?” The honest answer is that it depends on your resale price, and the number moves once Stripe fees and usage costs are subtracted, not just the $497 fixed platform fee. The chart below models three illustrative resale price points against the $497 fixed cost only, before usage and Stripe fees, to show why “2 clients covers it” claims vary so much across competing guides.

Once Stripe’s fee and a realistic usage-cost buffer get added in, the real break-even point at a $297/mo resale price is closer to 3 clients than 2, and at $197/mo, closer to 4 than 3. That one-client shift matters more than it looks like on paper, because it’s the difference between a new agency feeling profitable after its second signed client versus needing a third or fourth before the math actually works. Any guide claiming a precise universal break-even number without showing Stripe fees and usage costs in the calculation is skipping exactly the part that determines whether the number is real.

Resale pricing: what GHL consultants commonly recommend

There’s no independently verifiable source, forum thread, or published agency financial data that confirms specific resale prices in the market; the ranges below are what GHL consultants commonly recommend in setup guides, not a figure from agency P&L statements.

A starter resale tier is commonly recommended around $97-$147/mo, a growth tier around $197-$247/mo, and a pro tier around $297-$497/mo. Vertical or high-value niches, legal, dental, and roofing come up most often in practitioner guides, are sometimes priced significantly higher, in the $1,000-$2,500/mo range, reflecting both the value of the niche and typically heavier feature bundling (managed services on top of pure software access).

The pattern across these sources on what actually moves price within a tier is fairly consistent: expected usage volume for SMS, email, and call minutes; how competitive the specific niche is; whether the agency is bundling managed services (campaign management, content, ad spend oversight) versus reselling access to the software alone; and how much headroom the price needs to leave for covering the platform fee at low client counts. None of these figures should be treated as a guaranteed price point for any specific niche or market. They’re a useful starting range to model against your own usage-cost math, not a number to copy directly into a pricing page.

The gap between a pure-software resale price and a managed-service price is usually the biggest single lever in this list, bigger than the niche itself. A dental practice paying $297/mo for bare platform access and a dental practice paying $1,500/mo for the same platform plus a managed campaign calendar, content writing, and ad spend oversight — those aren’t really the same product, even though both invoices say “GoHighLevel” on them. Agencies that blur that distinction, pricing a managed-service tier like a software tier, tend to either underprice the labor involved or overprice a client who genuinely only wanted software access, and either mismatch shows up later as churn. aibrevo’s own GoHighLevel implementation cost breakdown covers what a build actually costs on the delivery side, which is a useful sanity check before setting a resale price that assumes your own margin is bigger than it is.

Common mistakes that break the math

Underpricing relative to usage costs. A flat resale price with no per-client volume modeling for SMS, email, and call minutes is the single most cited mistake in practitioner guides. A client running an aggressive text-message nurture campaign can cost meaningfully more to serve than a client using the platform lightly, and a single flat price doesn’t account for that difference. The real fix is knowing roughly where the usage ceiling sits for your flat price before a heavy user quietly turns a profitable account into a break-even one, and building a documented overage policy for the outlier clients who blow past it.

No buffer for Stripe fees and the carrier-fee markup. Pricing that treats the full resale price as available margin, without subtracting Stripe’s 2.9% + $0.30 and GoHighLevel’s 5% carrier-fee pass-through, overstates real profitability from day one. Both fees are small on a single transaction, but they compound the same way at 10 clients as they do at 100 — an agency that never built them into the original pricing model is running on a margin number that was wrong from the first invoice.

Ignoring churn. Treating every signed client as permanent recurring revenue against the fixed $497 cost is a planning error. A client who signs up and cancels within two months never contributed meaningfully to covering that fixed cost, and an agency that hasn’t modeled a realistic churn rate is likely to overestimate how quickly SaaS Mode becomes reliably profitable. A simple gut check worth running before launch: if a third of new signups cancel inside 60 days, does the remaining two-thirds still cover the platform fee and usage costs at your planned client count? If the answer is no, the pricing model was never actually profitable, it just looked that way before the first cancellation happened.

Weak or absent onboarding. SaaS Mode automates sub-account creation, not client activation. Consultants consistently point to poor onboarding, not underpricing alone, as the reason early-stage SaaS Mode agencies see high first-month cancellation rates. A client who signs up and never actually uses the platform is a churn risk regardless of how well the pricing itself is modeled. A structured first-week sequence, a welcome call, a pre-built checklist for connecting their calendar and phone number, a first campaign already loaded from the Snapshot, closes most of that gap, and it costs far less than replacing a churned client with a new one acquired through paid ads or outbound sales.

Skipping the live-mode test checkout. Launching without a full Stripe test-mode-then-live-mode checkout run is a preventable way to end up with broken billing right at launch, exactly when a bad first impression costs the most. It’s a five-minute check that catches a disproportionate share of launch-day problems, from a misconfigured webhook to a Snapshot that fails to clone correctly, before a real client ever sees the failure.

Who else builds SaaS Mode setups

aibrevo covers SaaS Mode as part of broader GoHighLevel implementation work, but it isn’t the only shop building these. Agencies focused on a specific vertical or on the automation layer specifically are often better served by a specialist: Autoesta’s GoHighLevel practice works on SaaS Mode and reseller builds as a dedicated focus area, while HighLevel Automation Team specializes in the workflow-and-automation side of a rollout, useful if the Snapshot itself is the hard part rather than the platform setup covered in this guide. Worth a look if your priority is deep automation build-out rather than the initial SaaS Configurator and Stripe connection work.

Frequently asked questions about SaaS Mode setup and pricing

Common questions agencies ask before and during setup are answered in the FAQ block above, covering plan requirements, V1 versus V2, break-even math, and pricing benchmarks.

Getting SaaS Mode built right the first time

SaaS Mode’s cost structure is genuinely simple once it’s fully laid out: one fixed platform fee, one processing fee on transactions, and a variable usage cost that scales with how your clients actually use the tools you’re reselling. The part that trips agencies up isn’t the arithmetic, it’s skipping two of those three costs when modeling whether a resale price actually works, and underestimating how much churn and onboarding quality matter compared to the price point itself. Model the full stack before setting prices, not after the first invoice arrives, and the break-even conversation with yourself becomes a lot more honest.

---

Sources

1. GoHighLevel official pricing page: gohighlevel.com/pricing (2026)
2. HighLevel Support Portal, SaaS Mode FAQs (V1 vs V2 distinction): help.gohighlevel.com
3. HighLevel Support Portal, Stripe sub-account connection steps: help.gohighlevel.com
4. Stripe pricing: stripe.com/pricing, verify current rate at time of reading
5. HighLevel Support Portal, SMS/MMS cost calculation methodology: help.gohighlevel.com