Make GHL Enterprise Ready
D
Daniel Ndaya
GHL IS NOT enterprise-ready, and enterprise is where the big money is at. If GHL becomes enterprise-ready, it would hit $10-100 billion EASY...Enterprise companies have more money to spend and will allocate more funds to software that can scale with their growth. We, as agency owners, crave to sign enterprise clients to GHL, but we can't, because GHL is not enterprise-ready. It lacks sooooo many BASIC features that HubSpot and Salesforce have that would make it enterprise-ready. Simple features such as the ability to create roles and teams...are ABSENT; all we have are permissions for individuals...It could change, but that is just an example
Log In
A
Anthony Reyes
Here’s a concise, actionable list of enterprise features we need:
RBAC (Role-Based Access Control)
Support custom roles at both agency (global) and subaccount levels.
Provide role templates/defaults and bulk permission editing.
Allow setting and cloning defaults across accounts.
Today’s four roles (Agency Admin/User, Subaccount Admin/User) are too limited and managed individually, which makes onboarding large teams (e.g., 50 users) take over an hour.
Global feature visibility & cleaner UI
Let agencies toggle features globally (e.g., hide WordPress at the agency level, not just per subaccount).
If a user lacks access to a menu/feature, hide it by default (or at least gray it out) to prevent “no permissions” popups.
Provide granular controls so we can hide ~40% of the app for clients who don’t need it.
This reduces confusion—for example, when we include managed WordPress in our base package but also show a separate $999/month WordPress upsell.
Native, flexible onboarding
Ship an easy way to set any webpage as the launchpad/home for each subaccount, out of the box.
Add first-class automation triggers and in-app ribbon/broadcast messages to guide users during onboarding.
Launchpad v2 has been in beta for two quarters; a simpler, “just works” approach would give agencies maximum flexibility with minimal platform overhead.
SaaS Pro plan and billing flexibility
Rework SaaS Configurator (v2) into a robust v3. Current limitations block enterprise deals.
Support coupons/discounts, custom pricing, and true tiered pricing based on user count or other dynamic data.
Enable per-seat billing that scales automatically—add/remove users and charges adjust without manually switching plans.
This aligns with how most CRMs/SaaS platforms handle usage-based pricing and is critical for scalability.
These changes would materially improve enterprise readiness, reduce onboarding friction, and make the platform more professional and scalable for larger clients.
R
Ryan Jenkins
Anthony Reyes hey guys, putting all this into one feature request isn't productive.
Product managers and developers need things broken out into individual "user stories" which they can evaluate and build independently.
I recommend submitting different user stories for each of the features requested above so they can be voted on individually.
While you're at it... make sure the requests have necessary details in them.
A few examples:
"Make GHL Enterprise Ready" isn't actionable or clearly defined. It's too broad.
"Rework SaaS Configurator v2 into a robust v3. Current limitations block enterprise deals." What does that mean? You haven't described WHAT specific limitations you're thinking of or HOW they're blocking deals.
"SaaS Pro plan and billing flexibility." What are you hoping to accomplish that the current system doesn't let you do?
I say this with love. I don't think you're wrong that all this stuff is needed, but this ticket needs to be broken out into a dozen smaller tickets.