One crate or a pack: how many snapshots an agency actually needs

Every agency that buys one snapshot eventually asks whether it should have bought several. The answer is usually no, and then one day it is suddenly yes.

The question people ask themselves is “how many niches do I serve”. That is the wrong count. It includes the dentist you took on as a favour in 2025 and the one restaurant you will never repeat. The count that decides this is how many niches you sell to repeatedly, which is almost always a smaller number and occasionally is one.

Every snapshot you own is a thing you maintain

A snapshot is not a file you buy once and forget. Owning one has a standing cost, and owning six has six of them.

Three costs, specifically. First, currency: GoHighLevel changes, and every snapshot you hold is a set of workflows that may reference a trigger type or an action that has moved. Second, custom values: each snapshot has its own list, and the list is the thing that makes a deployment fit a client. Six snapshots means six checklists to keep accurate and six ways for a new team member to miss a field. Third, support surface: when a client says “the reminder did not send”, the first question is which crate they are on, and the answer changes the diagnosis.

None of that is an argument against owning several. It is an argument against owning several before you need them, which is the actual mistake.

The rule

Buy one crate. Keep buying nothing until you have closed three clients in a second vertical.

Three is not arbitrary. One client in a new vertical is an accident. Two is a coincidence, and you can serve both by renaming services inside the crate you already own. Three is a pattern, and at three the renaming has stopped being editing and started being a rebuild you do every time. That is the moment a second crate pays for itself, and not before.

Until then, the crate you have plus twenty minutes of custom values covers more ground than agencies expect. The nine components are the same nine everywhere. A cleaning company crate and a house painting company crate differ in wording, timing and the completion moment, not in machinery, which is why one will carry the other for a client or two before the seams show.

When a pack genuinely wins

There is one shape of agency where buying breadth up front is the right call rather than the greedy one, and it is specific.

An agency whose prospects all come from one aisle. Everything you sell is trades, or everything you sell is clinics, or everything you sell is brokers and firms. Not “local business”, which is not a category, but a genuine operational family.

That works because an aisle is grouped by shape rather than by industry label. The businesses on the home and trade aisle all run on speed to lead with a recall interval behind it: answer first, chase the quote for three weeks, come back on a schedule. The businesses on the health and wellness aisle run on booked time, protected slots and a recall the practice controls rather than the customer. Those are different machines, but within each one, the wording transfers, your sales pitch transfers, and your install runbook transfers.

If your pipeline is aisle-shaped, buying the aisle removes the “we do not have a crate for that” conversation permanently, and every install after the first is faster because your team already knows the shape.

If your pipeline is not aisle-shaped, a pack is a wide shelf of things you will not deploy, and you should buy one crate at a time as the third client appears.

The three ways the depot sells this

The shelf offers the same stock three ways, and the names describe the scope rather than the discount.

A single crate is one snapshot, priced by depth, yours to deploy into unlimited sub-accounts you own or manage. An aisle pack is every crate currently on one aisle at a flat per-crate rate, plus anything added to that aisle over the following twelve months. The full depot pack is every crate on every shelf, plus a year of new stock as it lands.

All three carry the same delivery and the same support terms: share links within 1 to 2 business days of purchase confirmation, and 12 hours of dedicated installation support to be used within 14 days. Nothing here is displayed or discounted below $850 a crate, packs included, which is why the packs buy you breadth and a fit-out call rather than a heavy discount. The figures are on the pricing page and there is no point restating them here, because they are the least interesting part of the decision.

The discipline that stops a multi-crate agency losing track

An agency with six snapshots and no conventions has six snapshots and no idea which sub-account is on which. Three habits prevent that, and they cost nothing if you adopt them before the fourth crate rather than after.

• A naming standard, written down. Sub-accounts named to a fixed pattern, something like client, vertical, and the crate SKU. The SKU matters more than it sounds: it survives a rename and it tells a support conversation which machinery is underneath in one glance.
• One snapshot per sub-account. Loading two crates into the same account produces duplicate custom fields, duplicate pipelines with near-identical stage names, and workflows that both claim the same trigger. Resist it even when the client “also does” the second thing.
• A version note per deployment. A single line recording which crate, which version, and the date it was loaded. Snapshot updates do not propagate to accounts that were built from an older version, so without that note you cannot answer “does this client have the fix” without opening the account.

The same discipline is what makes onboarding survive scale generally, and if you are building an internal account-setup routine to sit alongside the client crates, the pattern we described for a reusable agency onboarding snapshot is the piece that runs before any of this.

If the roll-out is larger than a few accounts, the multi-niche agency rollout service does the roster mapping, the naming standard and the batch fit as one job rather than as forty afternoons.

What happens at month thirteen

Worth knowing before you buy breadth, because it is the part of a pack that gets skimmed.

Twelve months of platform-change updates and new stock runs from purchase. After that, everything you already hold keeps working and stays yours to deploy into unlimited sub-accounts. What stops is the additions: new crates landing on the aisle, and refreshes issued when GoHighLevel moves something underneath.

For an agency with a live roster, that is the year in which you either build the internal habit of reading release notes yourself, or you decide the updates were the thing you were actually paying for. Both are reasonable. What is not reasonable is discovering the distinction in month fourteen when a workflow action gets deprecated across six client accounts at once.

The practical version: if you are buying an aisle, put a note in the calendar for month eleven. Not to renew reflexively, but to look at how many of the twelve months of refreshes you actually applied. If the answer is most of them, the pack was doing work. If the answer is none, you own files, and one crate at a time was always the right shape.

Who should never buy a pack

A single-location business. One crate, forever.

A dental practice needs the dental practice crate and nothing else on the shelf. Owning six snapshots you cannot deploy is not optionality, it is a subscription to reading release notes for machinery you do not run. The pack pricing exists for agencies and operators with a roster, and there is no version of the argument where it helps a single practice, shop or firm.

Buying the wrong scope is the same class of error as buying the wrong band, which we set out in what a snapshot actually costs.

The next decision

Count the verticals where you have closed three clients. Not served, closed, three.

If the number is one, buy one crate and revisit this in six months. If the number is two or three and they sit on the same aisle, look at that aisle whole. If they sit on different aisles, buy the two crates and skip the pack, because you are not aisle-shaped and a wide shelf will not fix that.

The aisle directory is laid out by operational shape for exactly this reason, and the counter will tell you which of the two you are if the answer is not obvious from your own client list.