SaaS Mode

Usage-Based SaaS Rebilling with Included Limits & Overage Pricing
Right now in SaaS Mode we can rebill things like emails, SMS, calls, and other usage with a simple multiplier. That’s great, but it doesn’t match how most SaaS plans are actually sold. Feature request: Add the ability to set included usage + overage pricing and optional caps for each rebillable item. Example: My SaaS plan includes: 10,000 emails / month 2,000 SMS / month After that: Emails rebill at my chosen multiplier (e.g. 1.3x cost) SMS rebill at my chosen multiplier (e.g. 1.5x cost) Optional: Set a hard or soft cap (e.g. stop sending at 25,000 emails OR notify + continue billing) Why this matters: Lets agencies sell real, modern SaaS plans (“includes X, then pay per use”) instead of only pure pass-through markup. Protects margins by charging for true heavy usage instead of eating the cost. Avoids underpricing “power users” while still letting normal users stay within plan limits. Works perfectly for: Emails SMS Calls / minutes AI usage Any other metered resource GHL supports Key controls needed: Per-resource included amount (per month / per billing cycle) Per-resource overage multiplier or per-unit price after the included amount Optional usage cap: Hard cap: stop usage Soft cap: warn + continue and bill Reporting so we can see: Included vs overage usage Overage revenue per sub-account This would make SaaS Mode far more flexible and would align GHL pricing with how agencies package and sell their own SaaS bundles.
0
·
Enhancement
Granular Feature Control & Smarter Permissions for SaaS Mode Plan Builder
As a white-label agency building custom SaaS plans for clients, the current SaaS Mode configuration is too limited and creates unnecessary complexity. Here's what we're dealing with: Problem 1: Not enough granularity in the Plan Builder Right now, the Features tab only lets you toggle broad top-level categories (e.g. "Funnels", "Websites", "Workflows"). But within each of those categories, there are many sub-features — and we have no control over which specific sub-features are included or excluded in a plan. This makes it impossible to build truly tailored packages for different client tiers. What I'd love to see: A hierarchical feature control system in the Plan Builder: Level 1: Main categories (as they exist today) Level 2: Sub-categories per main category that can be toggled independently Level 3 (bonus): Specific actions or views within sub-categories (e.g. "view only" vs "edit") This would allow agencies to build precise packages — for example, giving a client access to Funnels but only the basic builder, without A/B testing or advanced settings. Problem 2: Unintended side effects at the User Permissions level When configuring permissions at the individual user level, disabling one permission often unintentionally disables other features that the agency wants the client to see and use. These hidden dependencies are not documented or visible anywhere, making it very frustrating to configure correctly. What I'd love to see: A clear dependency map or warning system: "Turning this off will also affect X and Y" The ability to override individual dependencies, so disabling one thing doesn't silently break something else Better alignment between SaaS plan-level settings and user permission-level settings, so there are no unexpected conflicts The bigger picture: Right now, configuring SaaS plans requires working across two separate layers (plan builder + user permissions) that don't always talk to each other logically. A unified, simplified configuration flow — with full granular control — would make GoHighLevel significantly more powerful for serious white-label agencies.
0
·
Enhancement
Load More