GHL snapshot licensing and what you may resell

There is a sentence that ends more snapshot purchases badly than any other: "unlimited use". It sounds like permission for everything. It is almost always permission for exactly one thing, and the thing it is not permission for is the one people go on to do.

The two rights, and why they are not the same

Installing is the right to load a build into sub-accounts you own or manage, for your own clients, as many times as you like. This is what a normal snapshot licence grants and it is the right that matters for almost every agency.

Redistributing is the right to hand the build itself to somebody outside your agency — another agency, a marketplace listing, a bundle you sell. It is a different right, it is priced differently everywhere it exists, and it is almost never included by default.

Why the distinction is enforced now

It used to be a paperwork problem. It is increasingly a technical one: marketplace tooling can lock the assets inside a shared snapshot so a buyer cannot repackage and re-list them, and a build that arrives through a protected share link is not a build you can freely re-export as your own product.

That protection is good for anyone selling snapshots and occasionally surprising for anyone buying one, because it can also constrain legitimate customisation. Ask before you buy whether the delivery is a protected link or an open import — the answer changes what you can do afterwards.

Five clauses to get in writing

1. Install scope. Unlimited sub-accounts inside your own agency, with no per-client fee and no seat count.
2. Rebranding rights. Explicit permission to modify, rebrand and re-export as your own snapshot — this is the clause that makes it a product rather than a rental.
3. Term. Whether the licence is perpetual for what you received, and what happens to your existing installs if you stop paying anything ongoing.
4. Updates. Whether you receive revisions when the platform changes underneath the build, and for how long.
5. Redistribution. Explicitly excluded is fine and normal. Silently ambiguous is not — ambiguity always resolves in the seller’s favour later.

What your client is licensed to do

This is the second question, and it is the one that arrives eighteen months later when a client leaves. If you install a system into a sub-account you own, and the client subsequently wants to take their account elsewhere, what leaves with them?

Decide it before you sign them, put it in your own service agreement, and be straightforward about it. A reasonable position is that the client owns their data — contacts, conversations, their domain, their number — and licenses the system for as long as they are with you. An unreasonable position is not having thought about it, which is how a departure becomes a dispute.

Where this touches your client’s customers

It sounds like a purely commercial matter, but it has an operational edge. If your right to run the build depends on a link that could be withdrawn, then the machinery answering your client’s phones, sending their reminders and collecting their reviews sits on somebody else’s permission.

The whole point of owning a rebranded, re-exported snapshot in your own agency is that nothing between you and your client’s customers depends on a third party staying in business or staying friendly.

How we do it, for reference

Every snapshot in the white-label snapshot catalogue is sold once, with unlimited installs inside your own GoHighLevel agency, explicit permission to rebrand and re-export as your own snapshot, and twelve months of version updates. Redistribution to other agencies is not included, which is the normal and correct exclusion. The licensing answers on the FAQ state it plainly, and the full terms carry the wording.

Where the ambiguity usually bites

Three scenarios account for most of the disputes, and all three are avoidable with one question asked before purchase.

The agency that grew

A licence granted to one agency, used across a second agency the same owner later founded, or across a partner’s account after a merger. Read whether the licence is granted to a legal entity, to a platform account, or to you. Entity-scoped licences do not travel, and finding out during due diligence is an expensive moment.

The client who wants to leave with it

A client asks to take their sub-account, including the system, to another agency. Whether you may hand it over usually depends on whether you re-exported the build as your own — a modified, re-exported system is yours to license onward, while a protected share link is not. Decide the answer before it is asked, and write it into your own service agreement rather than improvising it during a departure.

The bundle that seemed harmless

An agency includes a purchased build inside a course, a template pack or a community perk. That is redistribution regardless of whether money changed hands for that specific item, and it is the clearest breach of a standard licence there is. Free does not mean permitted.

Your own paperwork

The licence you buy governs what you may do with the build. What your client may do is governed by a document you write, and most agencies do not have one. Three clauses cover almost everything.

1. Ownership of data. The client owns their contacts, conversations, domain and phone number, without argument, and can have them on request.
2. Licence to the system. The client may use the system for as long as they are a client. It does not transfer with them, and that is stated at the start rather than at the end.
3. What happens at termination. Say exactly what is exported, what is disabled, and over what period. A defined offboarding is a retention feature, not a risk — clients relax about staying when leaving is not a threat.

None of this is legal advice, and a licence written for one jurisdiction can behave differently in another. What it is, is a list of the questions worth asking before money moves — because every one of these disputes is cheap to prevent in an email and expensive to resolve once a client is involved.

The short version

Unlimited installs and resale rights are different purchases. Buy the first, confirm you may re-export what you modify, and do not assume the second unless somebody has written it down and charged you for it.