GoHighLevel CRM Setup Guide for Marketing Agencies

Most GoHighLevel CRM setups are built for convenience rather than clarity. Stages are named whatever was easiest to type. Tags are applied inconsistently. Smart lists are empty. Custom fields are unused. The result is a CRM that technically stores contacts but provides no useful insight into where deals are or what actions to take next.

Here is how to build a GHL CRM that actually reflects your agency's sales and delivery process — and becomes a genuine tool for running your business rather than just a database of names and email addresses.

Start With a Process Map, Not the CRM

Before touching GHL, answer these questions on paper or a whiteboard:

• What is the first thing that happens when a new lead enters your world?
• What needs to happen for a lead to become a qualified prospect?
• What needs to happen for a prospect to become a paying client?
• What needs to happen after the sale to deliver and retain the client?

Your pipeline stages should map to the answers to these questions — not to generic CRM stages you copied from another business. A pipeline that reflects your actual process is one your team will actually use and that will generate meaningful data.

Designing Your Pipeline Stages

A well-designed agency sales pipeline typically has 5–8 stages. Here is a template structure to adapt:

1. New Lead — Contact has opted in but has not been contacted or qualified
2. Contacted — Initial contact made; waiting for response
3. Discovery Booked — Discovery call scheduled
4. Discovery Completed — Discovery call happened; assessing fit
5. Proposal Sent — Proposal delivered; awaiting decision
6. Negotiation — Active back-and-forth on terms
7. Won — Deal closed; client onboarding begins
8. Lost — Did not convert; note the reason in a custom field

The critical distinction is between "Proposal Sent" and "Negotiation" — two stages that many agencies collapse into one, losing visibility into where deals are actually stalling.

Building Your Tag Architecture

Tags serve three primary functions in GHL: triggering automations, filtering contacts into smart lists, and providing visual context on a contact record. A well-designed tag system uses a consistent naming convention:

• Source tags: SOURCE_Facebook, SOURCE_Google, SOURCE_Referral, SOURCE_Organic
• Status tags: STATUS_Active, STATUS_Inactive, STATUS_Churned
• Interest tags: INTEREST_Automation, INTEREST_Funnels, INTEREST_WhiteLabel
• Workflow tags: WF_NurtureActive, WF_OnboardingComplete, WF_ReviewRequested
• Qualifier tags: QUAL_Warm, QUAL_Hot, QUAL_Cold

The naming convention (PREFIX_Description) makes it immediately clear what a tag does and prevents the chaotic tag proliferation that most GHL accounts experience over time.

Smart Lists That Actually Get Used

Smart lists are dynamic filtered views of your contact database. They update automatically as contact data changes. Build these five smart lists as a starting foundation:

• Hot Leads Today: Contacts tagged QUAL_Hot + created in last 7 days + no booked call tag
• Awaiting Response: Pipeline stage: Contacted + last activity older than 3 days
• Proposals Outstanding: Pipeline stage: Proposal Sent + created more than 3 days ago
• New Clients (Onboarding): Tagged STATUS_Active + tagged New Client + created less than 30 days ago
• Re-engagement Candidates: Tagged STATUS_Active + last activity older than 60 days

Custom Fields for Data That Matters

Custom fields store contact-specific data that is not captured by GHL's default fields. For a marketing agency, useful custom fields include:

• Current monthly ad spend
• Primary marketing challenge
• Current CRM/platform they use
• Team size
• Industry vertical
• Lost reason (for closed-lost opportunities)
• Referral source name

The lost reason field is particularly valuable — tracking why deals are lost reveals patterns that inform your offer, pricing, and sales process over time.

Connecting Your CRM to Automations

The CRM becomes powerful when it connects to your automation system. Every pipeline stage change should be evaluated as a potential automation trigger: when a contact moves to "Discovery Booked," send a confirmation and add a calendar reminder; when they move to "Won," trigger the onboarding sequence; when they move to "Lost," trigger the re-engagement sequence for 90 days later.

This stage-triggered automation architecture means that your CRM updates themselves initiate the next right action — removing the need for anyone to manually remember to do the follow-up.