The free GHL Toolbox.

The setup-order checklist

GoHighLevel gives you a blank dashboard and roughly thirty things you could touch. The setup-order checklist cuts that down to eight steps in the right order: account basics, domain and email, calendar, payments, pipeline, workflow, offer, and onboarding. In that order, not another one.

The order matters inside GHL specifically because the platform's tools have dependencies. Your email automation won't work without a verified sending domain. Your calendar booking won't work without a connected payment integration if you're taking deposits. Your pipeline is meaningless without a working lead-capture path. The checklist wires these up in the sequence that makes each step valid before you move to the next.

What you avoid: building automations before you have a verified domain, setting up a payment integration before you have an offer to connect it to, configuring sub-accounts before your own agency account is solid. Each of those mistakes costs hours to unwind.

Deliverability checklist

Deliverability is where GHL users hit the hardest wall — and it hits after they've already built things, so it's demoralising. Emails going straight to spam, messages not arriving, campaigns that look like they sent but didn't land. The platform's email tools are capable, but they require DNS-level authentication to be trusted by receiving mail servers.

The deliverability checklist walks you through the full setup inside GHL: connecting your sending domain, configuring SPF records (which authorise GHL to send on your domain's behalf), setting up DKIM (which signs outgoing messages so they can't be spoofed), and getting your DMARC policy in place. It also covers how to verify your setup is working before you send a campaign — not after.

For AU/NZ users in particular: the checklist includes local regulatory notes. Australian SMS sender-ID rules changed in 2026, and NZ SMS capability through GHL is limited. These aren't edge cases — they're abandonment triggers if you hit them mid-campaign without knowing they're coming.

First-client launch starter

The most common place GHL users stall is right before their first client. The platform is configured — or at least it looks configured — but there's no kit for actually bringing someone on board. No intake form, no sub-account setup process, no billing connected to an offer, no handover documents. Just improvisation under pressure, which is when mistakes compound.

The first-client launch starter gives you the minimum viable onboarding kit inside GHL: an intake form that captures what you need, a sub-account setup that puts the client in the right place with the right permissions, billing connected to an offer they've agreed to, and basic handover documentation so the client understands what they're getting and how to reach you.

It's deliberately stripped down. One offer, one client type, one path. The goal isn't a perfect onboarding system — it's a working one you can use this week, that you can improve after your first client rather than before them.

One-clean-path workflow map

GHL's workflow builder is one of its most powerful features and one of its most common sources of paralysis. The tool is capable enough to build almost anything, which means new users frequently try to build too much before they've shipped anything. They get two-thirds through a complex workflow, hit a logic branch they haven't thought through, and abandon it.

The one-clean-path workflow map solves this by establishing a single revenue-relevant path before you build any workflow: lead comes in → nurture sequence runs → booking happens → follow-up fires → client onboards. One path, in GHL's workflow builder, working. Not every possible path. Just this one, tested end-to-end, generating actual appointments or responses from actual leads.

The map is a visual tool you complete before you open the workflow builder, not inside it. It forces the sequencing decisions — what triggers what, what happens if someone doesn't book, what the handoff to onboarding looks like — before you're deep in trigger logic and action steps. Build the map, then build the workflow. In that order.

Community access

The GHL community space is full of people selling things: snapshots, courses, done-for-you setups, coaching programs. That's fine — but it makes it hard to find people who are just building, comparing notes, and catching each other's mistakes. The GHL Incubator community exists to be that space.

No pitch threads. No upsell circus. No guru theatre. Just people working through the same setup sequence, sharing what they've found, and keeping each other honest about what's actually working versus what sounds like it should work. The value is specific: someone who hit the same deliverability wall last month can diagnose your setup in minutes. Someone who onboarded their first GHL client last week can tell you what they wished they'd had ready.

The community is included in the free Toolbox because the tools are more useful with a peer group around them. You're not building in isolation. You're building alongside people who are on the same path and can catch the thing you're about to get wrong before you get it wrong.

An account you actually own, set up in the right order

Your agency account, not a borrowed sub-account from someone else's setup. Your domain, verified and authenticated. Your sending reputation, established before you send a campaign. The setup-order checklist and deliverability checklist exist to get you to this state before you touch anything else.

Email that lands, before you send a campaign

SPF, DKIM, and DMARC in place. A test inbox run proving your messages arrive. A warm-up approach that builds sending reputation before volume. The deliverability checklist exists because this is where most new GHL users hit a wall they can't see coming — and the fix is simpler than the problem looks.

A first client you can onboard without improvising

An intake form that works. A sub-account set up correctly. Billing connected to an offer. Handover documentation ready to send. The first-client launch starter is the kit you hand yourself before you say yes to someone — so the onboarding is a process, not a panic.

One workflow built right, before you build the next one

A single lead-to-client path in GHL's workflow builder, tested end-to-end, producing actual appointments or responses. Not a complex multi-branch automation — just the one clean path that makes revenue possible. Built from a map you drew first, not discovered mid-build.