What a GoHighLevel sub-account actually costs to run, line by line

“How much does a GoHighLevel sub-account cost?” has a misleading answer and a useful one.

The misleading answer is nothing extra — on the higher agency plans, sub-accounts are unlimited and adding one does not change your invoice from HighLevel. That is true and it is why the question gets asked so often. It is also the reason agencies routinely price client retainers at a number that loses money on account four.

The useful answer is that a sub-account has five cost lines, only one of which appears on the platform bill.

Line 1 — the platform plan

HighLevel sells agency plans in tiers. The entry tier caps you at a small number of sub-accounts. The middle tier lifts the cap and adds white-label branding. The top tier adds SaaS mode, rebilling and the automated provisioning that goes with it. Published figures at the time of writing sit at roughly $97, $297 and $497 a month respectively — but check HighLevel’s own pricing page before you quote anyone, because the tiers and their contents change.

What matters for costing is the shape rather than the number: the plan is a fixed cost, so its per-account share falls as you add accounts. At three accounts the plan is a meaningful line. At thirty it is a rounding error, and every other line below has become the real cost.

Line 2 — telephony

Every sub-account that makes or takes calls and sends SMS consumes:

• a monthly rental per phone number
• a per-minute rate on inbound and outbound calls
• a per-segment rate on SMS, where a long message is several segments
• carrier fees attached to registered messaging

This is metered, it varies by country and carrier, and it scales with how busy the client is. It is also the line that surprises agencies, because a successful automation increases it. An AI receptionist that answers every call and an outbound recovery sequence that actually chases no-shows both consume minutes by design.

If you resell at a markup you can make this line profitable rather than merely recoverable. That is what rebilling is for, and it is covered in SaaS mode and snapshots.

Line 3 — email sending

Metered per email, cheap per unit, and easy to underestimate on a reactivation campaign against a list of forty thousand. Add the cost of the sending domain itself and the time to authenticate it properly — SPF, DKIM and DMARC records that actually validate.

Line 4 — compliance and setup work that repeats per account

Some work cannot be shared across accounts no matter how good your snapshot is:

• messaging brand and campaign registration, per business
• domain and DNS configuration, per business
• payment processor connection, per business
• third-party integrations, per business, because credentials never travel in a snapshot

Call this the fixed credential cost. On our own builds it lands around 90 minutes of skilled time per account. Yours will differ; the point is that it does not shrink when you buy a better snapshot, because a snapshot carries structure and not credentials.

Line 5 — build time, and the one you can actually change

This is the largest line for most agencies and the only one that a kit changes.

Here is the arithmetic, with the assumptions printed so you can substitute your own:

Scenario A — building each account by hand. Assume 8 hours to design and build an account’s automation properly the first time: intake logic, follow-up sequences, reminder cadence, review requests, reactivation. Assume your loaded cost for that time is $60/hour. That is $480 of build cost per account, repeated every time.

Scenario B — loading a kit. Assume the automation arrives pre-built and configured for the vertical. You still pay the 90-minute credential cost, plus roughly 90 minutes to fill custom values and run a full test pass. Three hours at $60 is $180 per account, plus the one-time price of the kit.

On those assumptions the crossover is fast: a kit priced at $950 pays for itself somewhere around the third or fourth account, and every account after that is $300 of build cost you did not spend. Change the hourly rate, change the build estimate, and the crossover moves — but the structure does not, because Scenario A’s cost is per-account and the kit’s cost is once.

These are illustrative figures, not measured results. We have no basis for telling you what your build takes; you do.

What this means for what you charge

Two consequences fall straight out of the lines above.

Charge a setup fee that covers the fixed credential cost. It is real work, it happens once per client, and it does not disappear at volume. Agencies that fold it into the retainer are lending the client 90 minutes of skilled time at 0% interest.

Price the retainer against metered usage, not against the plan fee. A busy client with an AI receptionist answering forty calls a week costs materially more to run than a quiet one, and the platform bill will not tell you which is which unless you look. Either rebill usage with a markup or band your pricing by call volume.

Line 6 — the one nobody budgets: support

An account that is live generates questions. “Why did this contact get two texts?” “Can we move the reminder to two hours?” “The calendar is showing Tuesday wrong.” None of these are billable in most retainers and all of them are real.

Two things reduce this line, and neither is a discount:

• Naming and documentation. Half of all support time is spent working out what an asset does before you can change it. A named, documented account answers its own first question. This is the entire argument of our naming convention note.
• Identical accounts. If forty accounts are built from the same blueprint, a fix you work out once applies forty times. If they are forty bespoke builds, you diagnose forty times.

A cost comparison you can actually fill in

Cost line	Per account or shared?	Shrinks with volume?
Platform plan	Shared	Yes
Telephony	Per account, metered	No
Email sending	Per account, metered	No
Credential and compliance work	Per account	No
Automation build	Per account, unless blueprinted	Only with a kit
Ongoing support	Per account	Only with standardisation

Print that table, put your own numbers in the right-hand columns, and the pricing conversation with your client becomes a different conversation. Three of the six lines are genuinely fixed per account. Two of them are only per-account because of how you work.

Where “unlimited sub-accounts” actually helps

The unlimited-sub-account plans are excellent value with one specific condition attached: you can fill the accounts. An empty sub-account costs almost nothing and earns exactly nothing. The plan fee is only cheap per-account if the accounts exist and are live.

Which reframes the real constraint. It is not the licence. It is how fast you can take a signed client and produce a working, tested, compliant account. That is a throughput problem, and the two things that move it are a repeatable blueprint and a repeatable process:

• a blueprint — one of the 22 sub-account kits, each configured for its vertical
• a process — either your own onboarding system or bulk sub-account provisioning where we build the whole batch

The honest summary

• The plan fee is fixed and gets cheaper per account as you grow.
• Telephony and email are metered and grow with client success — rebill them.
• Compliance and credential work is per-account and does not shrink. Charge for it.
• Build time is per-account only if you keep rebuilding. That is the line a kit removes.

Every price we publish, for both kits and services, is a one-time figure with no subscription attached, precisely so it can be compared against the arithmetic above rather than buried in a monthly.