
How to Set Up SaaS Mode in GoHighLevel: A Step-by-Step 2026 Guide
If you're trying to set up SaaS Mode in GoHighLevel and the documentation feels like it's hiding the parts that actually matter, you're not imagining it. The product covers eighty percent of the marketing pitch and roughly forty percent of the operational reality. This guide fills in the other sixty — the configuration choices, billing decisions, and onboarding flows that decide whether your agency lands at $5K MRR or $50K MRR on the same product surface.
It's written for agency owners who have either bought the SaaS plan and stalled on activation, or are evaluating whether SaaS Mode is the right next move. Aussie English throughout. No "you can sell GoHighLevel to anyone" hype — we run SaaS Mode setups for clients every week, and the parts you don't see in tutorials are where the money is made.
What SaaS Mode actually is in 2026
SaaS Mode is the GoHighLevel feature set that lets an agency on the $497 Pro Plan resell GoHighLevel sub-accounts to its own end-clients, under its own brand, on its own pricing — while GoHighLevel sits invisibly underneath as the platform.
In practical terms it gives you four capabilities:
- Sub-account provisioning — create a new GoHighLevel sub-account inside your agency, branded as yours, in under two minutes.
- Bring-your-own-Stripe billing — your end-client pays your agency directly, on your Stripe, on your plans, and you optionally rebill the underlying GHL costs (SMS, email, AI minutes) at a markup.
- Snapshot deployment — push a pre-built CRM/funnel/automation template into a sub-account on first login, so the client experiences a working product instead of a blank box.
- Custom domain + branding — your sub-accounts run on
app.your-agency.com, your colours, your logo. The end-client never sees the words "GoHighLevel".
If you only set up three of these four, you have a white-labelled service, not a SaaS. That distinction matters because it changes margin, churn, and how you can talk about the offer.
Why agencies set up SaaS Mode (and why some shouldn't)
The case for SaaS Mode is real and it's three things:
- Recurring revenue. A $97/month sub-account at 80% gross margin compounds. Twenty clients = $1,940 MRR clear. A hundred = $9,700.
- Lower customer acquisition payback. Implementation services close in 1–2 calls; SaaS subscriptions close at the end of a trial or workshop with no further sales effort.
- Optionality. You can run done-for-you and done-with-you offers on the same platform you're already paying for.
The case against is also real:
- Support load. Every sub-account is a customer who can submit tickets. Without an SOP'd support layer, your founder time gets eaten alive by password resets.
- Stripe and tax exposure. When your agency becomes the merchant of record for the SaaS subscription, you take on chargeback risk, GST, and (in Australia) potentially digital-services-tax obligations on overseas customers.
- Activation challenge. A trial sub-account with no snapshot installed and no onboarding is a churn machine. We see agencies launch SaaS Mode, get 30 trial sign-ups, and convert 1.
Set up SaaS Mode only if you have (a) the snapshot to deploy on day one, (b) a support process, and (c) a credible plan for activation in the first 14 days.
What you need before you start (checklist)
Before you touch the toggle, have these ready:
- A GoHighLevel $497 Pro Plan subscription active for at least 7 days (Stripe propagation is annoying).
- A Stripe account in your agency's name (not a personal account; not a third party's).
- A dedicated subdomain for the white-label app (e.g.
app.your-agency.com) with DNS access. - A snapshot that represents your product offering — funnels, pipelines, calendars, workflows, email templates.
- A support email (
[email protected]) and ideally an inbound channel (chat widget or shared inbox). - A pricing model — at minimum two tiers, with clear feature differentiation and reseller-margin maths done.
- A logo at 600×60 px for navigation and 400×400 px square for app icon use.
The number-one cause of stalled SaaS Mode rollouts is starting the technical work before the pricing and snapshot decisions are made. Make those decisions first.
Step-by-step setup
Step 1 — Enable SaaS Mode at the agency level
Inside your agency-level GoHighLevel dashboard go to Settings → SaaS Configurator. Toggle SaaS Mode on. Confirm your Pro Plan status is healthy.
If the toggle is greyed out, the cause is almost always: Pro Plan is paid but hasn't propagated, OR your agency owner role is not the one logged in. Use the account owner login, not a team member's.
Step 2 — Connect your Stripe account
Still in SaaS Configurator: Connect Stripe. This OAuth flow connects your agency Stripe to GoHighLevel so that subscription payments from your end-clients land in your Stripe directly.
Critical detail: this is not the same Stripe connection used by individual sub-accounts for their own payments. SaaS Mode uses one master Stripe at the agency level for SaaS subscription billing.
Step 3 — Build your plan tiers
In SaaS Configurator → Plans, create at least two and ideally three plans. A workable starter structure for an Australian or US-focused agency in 2026:
- Starter — $97/month — 1 user seat, 1 calendar, basic email & SMS (with rebill caps), no AI agents.
- Growth — $197/month — 5 user seats, 3 calendars, includes a small AI agent allowance, branded email IP option, priority support.
- Pro — $497/month — unlimited seats, unlimited calendars, full AI agent suite, white-labelled mobile app branding, weekly office hours.
For each plan, set the Stripe price IDs (monthly + optional annual), the included features (toggle them in the plan editor), and the optional rebill margin on SMS, email, AI minutes, premium triggers, and integration costs.
The rebill margin is the silent profit driver. Standard agency practice in 2026 is 1.5–2.5× the wholesale GHL cost of SMS and AI minutes. We see agencies leave 15% of revenue on the floor by not setting these.
Step 4 — Configure white-label branding
Inside SaaS Configurator → Whitelabel: upload your 600×60 logo (for navigation) and your 400×400 favicon, set primary and accent colours that match your brand, set your support email and the help URL (point this at your own docs or chat widget, not the default), and configure the custom domain for the app. The custom domain requires a CNAME at your DNS provider pointing your chosen subdomain to GoHighLevel's whitelabel endpoint. Propagation is usually 30 minutes but can take up to 24 hours.
Test the white-labelled app login flow from an incognito window before declaring it live.
Step 5 — Build and assign the activation snapshot
In your agency-level Snapshots tab, build a snapshot that contains the working product your end-clients will see on day one. A useful baseline:
- 3 pre-built funnels (lead magnet, booking funnel, upsell page).
- 2 calendars (discovery call, follow-up).
- 1 sales pipeline with 6 stages and field templates.
- 4–6 workflows wired to the snapshot's forms and calendars.
- 10 email templates and 5 SMS templates.
- A dashboard with default widgets relevant to the client's industry.
Inside SaaS Configurator → Snapshots, set this snapshot as the default for new sub-accounts. Now, every trial that signs up gets a working product instead of an empty box. This single decision typically lifts day-14 activation rates from 10% to 50%+.
Step 6 — Build the trial / sign-up funnel
Build a public funnel inside your agency that captures the prospect's name, email, business name, and intended use case; takes their card via Stripe (or routes to a free trial); and triggers the SaaS Mode "Create Sub-Account" workflow action — this auto-provisions a sub-account on the chosen plan, deploys the snapshot, sends the login email, and starts the onboarding sequence.
The "Create Sub-Account" workflow action is the linchpin of self-serve SaaS Mode. If it's missing from your action list, your account is provisioning new sub-accounts manually — which works for the first ten clients and breaks at twenty.
Step 7 — Build the onboarding sequence
This is the part that most agencies skip. A 14-day onboarding sequence that drives activation across the snapshot's key features:
- Day 0 (immediate): Welcome email + login + 90-second product tour video (your own, not GoHighLevel's).
- Day 1: "Set up your first calendar" walkthrough.
- Day 2: "Import your first 25 contacts" walkthrough.
- Day 4: "Send your first email broadcast" prompt + template.
- Day 7: Check-in email from a real human + offer of a 15-min activation call.
- Day 10: Case study email — a real client using your product.
- Day 12: "What you've achieved so far" stats email pulled via webhook.
- Day 13: Trial-ending reminder + upgrade CTA.
- Day 14: Conversion email or graceful downgrade.
The activation call on day 7 is the single highest-leverage touch we've measured — it lifts trial-to-paid conversion by 1.8–2.3× in the agencies we've measured.
Step 8 — Wire up support
Even if it's just you and a VA, decide and document: where the support email lands, who answers in the first hour, the first day, the first three days, the response-time promise you're publicly making, and where customers self-serve (Loom library, help docs, AI chat). Without this, your SaaS Mode will eat your founder's calendar inside the first 50 sub-accounts.
Step 9 — Test the full end-to-end flow
Before you launch publicly, run this test: sign up via your public funnel, paying with a real card; confirm the sub-account is created and the snapshot deploys correctly; confirm the white-label login URL works in incognito; confirm onboarding emails arrive on schedule; confirm the rebill margin is applying to SMS/email actions inside the sub-account; confirm cancellation flow works (cancel from inside the sub-account; confirm sub-account suspends; confirm refund proration logic). Then refund the test charge.
Step 10 — Soft launch to a private list
Don't open the doors to the world on day one. Soft-launch to 10–20 known contacts, watch the cohort for 14 days, fix the friction points they surface, then open public sign-up.
Implementation examples — three real configurations
Agency A — Property-services niche. Pricing: $147/$297. Snapshot includes 5 property-specific funnels and a CRM pipeline tuned for buyer enquiries. Soft-launched to existing service clients as a self-serve "do it with us" tier. Hit $14,000 MRR in 90 days with 70 active sub-accounts.
Agency B — Coaching niche. Pricing: $97/$297/$697. Snapshot includes a course shell, membership area, and Stripe-connected checkout. Pro tier includes white-glove migration from Kajabi (which we run as a migration project on their behalf). 22 sub-accounts in 60 days, average plan price $312 — strong margin profile.
Agency C — Trades. Pricing: flat $197 with an annual discount. Snapshot includes a quote-request funnel, jobs pipeline, automated review-request workflow, and SMS-first communication. Found that trades customers churn fastest on email-heavy onboarding, so rebuilt the entire 14-day sequence as SMS + voice notes. Activation went from 18% to 41%.
Common mistakes — what costs SaaS Mode agencies real money
Mistake 1 — No snapshot on day one. Trial sub-accounts open onto a blank product. Activation lands below 10%. The fix: build a working snapshot before opening sign-up.
Mistake 2 — Forgetting the rebill margin. SMS, AI minutes, and email overages get billed at wholesale. Standard 2× markup leaves typically 12–18% of revenue uncaptured per active sub-account.
Mistake 3 — Custom domain not configured. End-clients see "app.gohighlevel.com" in the URL bar. They Google it. They learn the product is reseller-able. Trust dies.
Mistake 4 — Onboarding emails fired from a no-reply address. Replies to onboarding emails contain the most valuable activation signal you have — bin them, lose the signal.
Mistake 5 — No cancellation flow. Customers cancel through Stripe directly. You discover the cancellation 14 days later when the next invoice fails. By then they've moved.
Decision framework — is SaaS Mode right for you?
Use this scorecard. If you score under 7, fix the gaps first. Ask yourself: Are you on the GoHighLevel Pro Plan? Have you sold the product or service this SaaS Mode will package, at least 5 times manually? Do you have a snapshot ready that represents working product? Do you have a support coverage plan for hours 0–24, 1–7 days, and 7+ days? Do you have at least one real activation case study you can show prospects? Do you have a custom domain ready for the white-labelled app? Have you decided pricing and run the rebill margin maths? Have you written the 14-day onboarding sequence? Have you tested the full sign-up → cancel flow with real Stripe charges?
7+ out of 9 means launch. Below means you'll churn out money on customer acquisition without the activation rate to keep them. The same disciplined launch logic underpins our workflow builds too — momentum without observability is just expensive guessing.
Alternatives to SaaS Mode
If SaaS Mode looks like more than you want to operate, three viable alternatives:
- Done-for-you services on the agency Pro Plan — no end-client billing, no support escalation, no rebill complexity. Lower ceiling, higher per-client revenue. Pairs well with our implementation services.
- Reseller of GHL sub-accounts without white-label — keep GoHighLevel branding visible, charge a setup fee + management retainer. Simpler, less defensible.
- Industry-niched snapshot product sold as a one-off plus monthly support. Same snapshot, no SaaS plumbing. We've seen $200K/year businesses built this way without ever flipping the SaaS Mode toggle.
Frequently asked questions
How much does SaaS Mode cost in addition to the GHL Pro Plan?
Nothing extra in plan fees. You're paying $497/month for the Pro Plan and SaaS Mode is included. Your costs come from underlying usage (SMS, AI minutes, email beyond plan) which you rebill to end-clients at margin.
How long does setup take?
A diligent solo agency owner takes 3–6 weeks from decision to public launch, mostly because of snapshot build and onboarding-sequence writing. We typically deliver SaaS Mode for an agency in 14–21 calendar days, snapshot included.
Can I migrate existing service clients into SaaS Mode?
Yes, and you should. Existing service clients have proven they value the product. Offer a self-serve tier at a lower price than your DFY service; many will downgrade themselves, freeing your team's hours for higher-value work.
Does SaaS Mode include the GoHighLevel mobile app branding?
Yes — you can submit your own iOS and Android app for white-labelled deployment via GoHighLevel's mobile app program. Submission takes 4–8 weeks once your branding is finalised.
Can end-clients buy additional sub-accounts under their own?
No — sub-accounts under a SaaS Mode agency are flat, not hierarchical. If your end-client needs multiple locations (a multi-site business), you provision them as separate sub-accounts under your agency.
What happens to my sub-accounts if I cancel my Pro Plan?
They are suspended after a grace period. This is a real reason to put your Pro Plan billing on annual — it eliminates accidental card-failure churn cascades.
Can I run SaaS Mode in multiple geographies?
Yes, but you need to make a Stripe decision per region (Stripe AU, Stripe US, etc.) and a tax / GST treatment per region. Most agencies pick one Stripe account for international receivables and a separate one for AU to keep GST clean.
Is SaaS Mode profitable from sub-account #1?
The 1st sub-account makes back about 20% of your Pro Plan fee at $97 pricing. Break-even on the $497 base typically lands at 6–10 paying sub-accounts depending on rebill mix. After that, every sub-account is high-margin recurring revenue.
If you want SaaS Mode set up correctly the first time — snapshot included, onboarding written, rebill margins live, and a real launch plan — that's exactly what we build for agencies. Look at our pricing or take the implementation off your plate with a strategy call.
