GoHighLevel snapshots: what we actually install (and what a snapshot is not)

A file is not speed-to-lead

People search “GoHighLevel snapshots” for two reasons. They want a faster install than clicking every setting by hand. Or they bought a snapshot and it did not catch a single lead. Both are real. A snapshot is a file of structure. It is not speed-to-lead. Speed-to-lead is what happens after the structure is named for your close, connected to your forms, and watched when a field gets renamed.

The Shaz Method is not a snapshot marketplace. Setup ($250 once) is a snapshot of the catch, tuned to how you close, in the GHL account you own. We would rather inherit a mature install than dump a file on top of one. We will not pretend a from-scratch CRM is the product. Longer positioning: snapshots vs a custom CRM.

What a snapshot actually contains

In GHL, a snapshot can carry pipelines, stages, funnels, forms, surveys, calendars, workflows, email/SMS templates, custom fields, tags, folders, trigger links, membership products, and a pile of smaller objects. What it cannot carry is your offer, your voice, your phone number reputation, your Google/Meta ad accounts, or the human who will pick up a booked conversation.

What we put in the Shaz Method snapshot is the catch: pipeline stages with owners and SLAs, forms and calendars on the same contact, core speed-to-lead and a nurture skeleton with stop rules, tagging so source stays attached. Not 80 unused funnels named after someone else’s coaching offer. Not a membership area you will never launch. Not a 27-email ladder for a business that closes on the phone.

If your close is a site visit, the snapshot’s calendar and pipeline say site visit. If your close is a stay, they say dates and deposit. If your close is a membership, they say interested → conversation → member. Generic “New Lead / Contacted / Closed” is how cards go to die. See pipelines.

Snapshot vs template vs “we’ll just copy the account”

A snapshot is the right tool when you want a repeatable foundation you can load into a sub-account and then tune. Copying an entire account by hand is how mistakes hide. Building from a blank sub-account every time is how you forget the stop rule.

A public “agency snapshot” from a stranger is a different product. You inherit their field names, their assumed sales motion, their email tone, and often their broken test workflows. Then you spend a month deleting. We load ours only as a starting line, then we name things for you. If you already have structure, the diagnostic says whether we snapshot-load or edit in place.

We do not use snapshots as a hostage mechanism. Work happens in your sub-account (or agency account). If we stop, you keep the contacts, workflows, funnels, and numbers. Setup is priced at $250 because the foundation should survive a breakup.

What we tune after the file loads

Numbers and sending domains: SMS registration, email from-name, quiet hours, opt-in language for your country. A snapshot cannot finish compliance for you.

Calendars: real availability, buffers, round-robin or single owner, confirmation copy, no-show recovery. A loaded calendar with nobody’s hours is a pretty 404. See GHL calendars.

Workflows: enrollment sources pointed at your actual forms and lead sources, not at demo forms left in the snapshot. Test submit until a contact shows a full thread. See automations and workflows.

Tags and custom fields: source, offer, location, listing, campaign. Enough to answer “where did this booked call come from?” without four tabs. Not 200 tags named after moods. CRM setup is the hygiene pass.

Users and routing: who gets the ping at 9:41pm. If that is nobody, we say so on the diagnostic. Lead routing is the map.

When not to load a snapshot

You already have a living GHL account with years of contacts, custom fields, and workflows that mostly work. Loading a second snapshot on top is how you get duplicate pipelines and two “new lead” stages. In that case we diagnose, then we edit. The $250 may become a lighter pass. That is a feature. We do not rebuild for sport.

Your leak is positioning, not catch. A snapshot will not fix an offer nobody wants. I will say that on the 20-minute diagnostic, not after a month of $697.

You want a black-box login where “the agency owns GHL.” Wrong product. You own the account. Platform fees stay with GoHighLevel.

Versioning, rot, and why operate still matters

A snapshot is a moment in time. Forms change. GHL ships features. Carriers change SMS rules. The snapshot you loaded in March will not notice that your thank-you page stopped writing a contact in August. That is why monthly operate exists on Core and Growth.

We do not “re-snapshot” your live account every month for fun. We health-check workflows, reporting, and the catch SLA. If a new offer needs a new pipeline, we add it with the same tagging conventions so source still survives. If a workflow should die, we kill it. Dead workflows are not assets. They are landmines.

Core ($397/mo) operates GHL, organic social, and email/SMS. Growth ($697/mo) adds ads into the same pipe plus extras including missed-call text-back. Neither retainer is a new snapshot subscription. The snapshot was the starting line. Operate is the sport.

How snapshot install sits on the ladder

Setup is the snapshot plus first install: account structure, pipeline, calendars, core speed-to-lead, tagging, baseline capture path, handoff notes. Core keeps it running. Growth buys attention into the same contact ID.

Onboarding is the week after you pay Setup: access, numbers, test submits, first catch. The diagnostic before that is free of retainer commitment on purpose. Apply is four steps. Email shaz@shazmethod.com if you already know you need the file loaded and tuned, not a tour of GHL features.

• You own the sub-account — the snapshot is loaded into your house
• We tune stages, copy, calendars, and enrollment to your close
• We test the catch with real (test) contacts before calling it done
• We do not leave demo funnels and “New Workflow 12” behind
• If you already have a mature install, we say so instead of loading twice

What usually comes along for the ride (and what we strip)

GHL snapshots can include membership products, trigger links, surveys, pipelines you will never use, and demo calendars named after the vendor’s coaching offer. We strip demo funnels, unused pipelines, and “New Workflow 12.” We keep objects that serve catch, convert, retain for your close. If you wanted the membership campus, we would say so on the diagnostic and name it in the snapshot on purpose — not as leftover furniture.

Custom values, from-names, and phone fields often arrive blank or pointed at the last client. That is expected. Setup week is replacing those with your identity. A snapshot that still says “Hi {{first_name}} from Demo Agency” on Friday is not installed. It is copied.

We also watch for duplicate objects after a load: two “New Lead” pipelines, two SMS workflows that both fire on form submit. Duplicate catch workflows are how people get three first texts. The test contact is how we see it. If you loaded a marketplace snapshot last year, the diagnostic includes a hunt for those duplicates before we add ours.

Snapshot shopping vs an install

The marketplace instinct is understandable. GHL is a large product. A file feels like progress. Progress is a contact at 9:41pm getting a useful reply and a next step. If a $29 snapshot got you that, keep it and hire operate. If it got you 40 unused assets and a still-silent after-hours inbox, you did not buy a system. You bought a zip of someone else’s assumptions.

Our job is the system. The snapshot is a delivery format. Read GoHighLevel systems for the runtime argument, and the method for the five functions we run after the file lands.

FAQ