GoHighLevel SaaS mode pricing setup is where your agency stops selling hours and starts selling software—but it's also the configuration area with the most expensive mistakes. Get a rebilling margin wrong and you lose money on every SMS your customers send; wire a plan to the wrong snapshot and paying signups land in empty accounts. This walkthrough covers how to structure your pricing, configure it in the SaaS configurator, set up Stripe and rebilling correctly, and test the whole machine before launch.
What SaaS mode actually does
SaaS mode (available on the $497 agency pro plan) turns your GoHighLevel agency into a self-serve software business. You define subscription plans; prospects sign up and pay through Stripe; GoHighLevel automatically creates their sub-account from your snapshot, activates the features their plan includes, and rebills them for usage—SMS, email, phone calls, and AI—at rates you set with your margin built in.
The pricing setup has three layers that must agree with each other: the subscription price (what the plan costs monthly), the feature set (what the plan unlocks), and the rebilling rates (what usage costs on top). Most broken SaaS launches trace back to one of these layers being configured out of sync with the others.
Structuring your plans before touching the configurator
Decide your tiers on paper first. The pattern that works for most agencies is three plans: an entry tier with core CRM and one or two channels, a mid tier adding automations and calendars (this is the plan you'll drive most signups to), and a premium tier with everything plus higher limits or priority support.
Anchor your prices to the value delivered, not to GoHighLevel's cost. Common real-world ranges run $97–$197 for entry, $197–$397 for mid, and $397–$997 for premium tiers. Remember your platform cost is fixed at $497/month regardless of customer count—your margin structure improves with every signup, and usage rebilling adds a second revenue stream on top.
Step-by-step pricing configuration
With the structure decided, here's the configuration sequence in the SaaS configurator:
- Connect Stripe first: Settings → SaaS Configurator requires a live Stripe account connection before plans can sell—use your real account, not test mode, when you launch.
- Create your plans: name, monthly (and optional annual) price, and a clear description—these appear on your pricing page exactly as written.
- Map features per plan: toggle which GoHighLevel features each tier unlocks, matching the tier design you did on paper.
- Set trial terms: choose trial length (7 and 14 days are the common choices) and whether a card is required upfront—card-required trials convert lower but produce far better-qualified signups.
- Configure rebilling: enable rebilling for SMS, email, phone, and AI usage, and set your markup multiplier—2x to 3x on wholesale rates is typical and keeps you profitable on usage.
- Attach the provisioning snapshot: choose which snapshot loads into new sub-accounts per plan, so every signup lands in a complete, working account.
- Set up your pricing page: use the generated signup links on your marketing site's pricing page, one per plan.
- Configure failed-payment and cancellation behavior: decide grace periods and what happens to accounts on cancellation, so involuntary churn is handled by rules, not surprises.
Rebilling margins: the layer that quietly decides your profit
Rebilling is where SaaS mode either compounds your revenue or silently leaks it. GoHighLevel charges you wholesale rates for SMS (via Twilio), email (via LC Email/Mailgun), phone minutes, and AI features. With rebilling on, your customers' usage is charged to their card at your rates—so your markup multiplier is pure margin on every message a customer sends, forever.
Two rules keep this healthy. First, never leave rebilling off on a usage-heavy feature 'temporarily'—an agency absorbing SMS costs for fifty active customers can lose hundreds of dollars a month without noticing. Second, keep markups defensible: 2–3x wholesale reads as normal SaaS usage pricing; 10x invites customers to check what Twilio costs and feel cheated. Review your rates against wholesale changes a couple of times a year.
Test the full journey before you launch
Before driving any traffic, run a real test purchase through every plan: sign up on your pricing page, pay with a real card (refund yourself after), and verify the whole chain—payment lands in Stripe, the sub-account is created, the right snapshot loads, plan features match what you sold, the welcome email arrives on your branding, and usage rebilling charges correctly.
Then test the exits: cancel a subscription and confirm the account behaves as configured, and simulate a failed payment if you can. Every one of these paths will eventually happen with a real customer; the only question is whether you find the bugs or they do.
Getting help with SaaS mode setup
SaaS mode touches pricing strategy, Stripe, snapshots, and provisioning in one tightly-coupled system, and it has to work end to end before the first customer arrives. If you'd rather launch on a tested setup than debug one live, my SaaS mode setup service configures the entire stack—plans, rebilling, snapshot provisioning, and full journey testing—and pairs naturally with white label setup and a solid snapshot build.
Frequently asked questions
What plan do I need for SaaS mode?
SaaS mode requires the $497/month Agency Pro plan. The $297 plan includes white labeling but not the SaaS configurator.
What's a normal rebilling markup?
Most agencies set 2x–3x on wholesale SMS, email, phone, and AI rates. That's profitable without being so high that customers question the pricing.
Can I change pricing after launch?
Yes—new prices apply to new signups. Existing subscriptions stay on their original terms unless you migrate them, so it pays to get the structure close to right before launch.