Pipelines are included on every plan, including Starter at $97/month. There’s no per-pipeline cost, which is also why accounts end up with eleven of them and use two.

What is a GoHighLevel pipeline, precisely?

A pipeline is a set of ordered stages containing opportunities. Each opportunity is a contact moving toward a defined outcome, with an optional monetary value. Alongside pipelines sit smart lists — saved filters over contacts — which most people use badly because they conflate the two.

Rule of thumb: if a stage requires someone to decide something, it belongs in the pipeline. If it’s just a label, it belongs in a tag.

Step 1: Design stages around buyer actions

Bad stages: “New”, “Contacted”, “Interested”, “Warm”, “Hot”. Nobody agrees on what “warm” means, so nobody moves cards.

Better stages, each tied to something that demonstrably happened:

Six stages is the ceiling for a small team. Every stage past that is a place leads go to be forgotten.

Step 2: Put a value on every opportunity

An opportunity without a value makes the pipeline a to-do list. Set a default value per pipeline — average deal size — and let users override it. GHL does the weighted totals for you.

This is what lets you say “$84k in proposal stage” instead of “17 cards in proposal”. The forecast won’t be precise, but it converts a qualitative board into a number you can discuss. Set the value at creation with an automation action rather than asking people to type it.

Step 3: Automate stage entry, don’t automate stage exit

Let actions move cards forward. Form submitted → add to New lead. Appointment booked → move to Appointment set. Invoice paid → move to Won.

Don’t automate the negative moves. If an automation demotes a card because a lead hasn’t replied in 5 days, reps stop trusting the board and start editing cards manually. Negative movement should be a notification, not an action.

Step 4: Add the stuck-deal workflow

The single highest-value automation in GHL: trigger on Opportunity Stage Changed, wait a fixed number of days per stage, then check whether the stage is still the same. If yes, notify the owner and tag the contact a stale tag for that stage and apply a specific day threshold for each stage: 2 days for Contacted, 5 for Engaged, 3 for Proposal.

Keep the message actionable. “Card X has sat in Proposal for 5 days” gets ignored without a next step. Add the link to the record.

Step 5: Clean up once a quarter

Delete pipelines that haven’t had a card move in 60 days. Archive stages nobody uses. Merge duplicate pipelines that were built for the same offer by two different people.

This sounds like housekeeping, but a bloated pipeline view is the reason reps stop opening GHL. Untouched boards train people to ignore the whole CRM.

Does the pipeline integrate with conversations?

Yes, and this is GHL’s main advantage over a standalone CRM. Conversations in the Inbox show the contact’s pipeline stage, and you can move a card from inside the conversation sidebar. That eliminates the classic failure where the sales call goes well and nobody updates the CRM, because the update is one click from where the call ended.

When is a pipeline the wrong tool?

For a single-step business — enquiries that turn into a booked call or nothing — a pipeline adds ceremony. A tag plus a smart list gets you the same visibility faster. Pipelines pay off once there are three or more decisions between first contact and payment, or once more than one person touches the lead.

Also skip pipelines if nobody checks the dashboard. A pipeline that’s read weekly is a report; one that’s read daily is a system.

Quick Summary

• Six stages maximum, each keyed to an observable buyer action.
• Give every opportunity a value so the board produces a forecast.
• Automate entry into stages; make exits manual with notifications.
• A stuck-deal workflow per stage is the most valuable automation in GHL.
• Delete pipelines that haven’t moved a card in 60 days.

Agency plans start at $297/month and add sub-accounts and white-labeling. If you’re building for one business, Starter is enough.

What does a GoHighLevel funnel actually consist of?

A funnel is an ordered set of pages sharing a domain and a tracking setup. Each step is built in the drag-and-drop page builder, and each can host forms, calendars, surveys and payments. Anything a visitor submits creates or updates a CRM contact.

That last part is the reason to use GHL instead of a standalone page builder. The funnel and the CRM are the same system, so a form submission is instantly a contact with a pipeline stage.

Step 1: Attach a custom domain before you build anything

Go Settings > Domains > Add Domain. Enter a subdomain like go.yourbrand.com, then add the CNAME record it shows you at your registrar. Propagation takes anywhere from 10 minutes to a few hours.

Do this first, because pages created on the temporary msgsndr.com domain don’t carry over cleanly. Editing a funnel’s domain after launch means re-verifying forms and reconnecting calendars — an hour of avoidable work.

If you’re stuck: check whether the domain has an existing A record. GHL needs a clean CNAME, and a leftover record from another host silently blocks verification.

Step 2: Build step one as a single offer, not a menu

Create Sites > Funnels > New Funnel, choose the two-step template, and name it after the offer. The landing page should make one promise, show proof, and ask for one action.

Keep the form to three fields: name, email, phone. Each extra field costs conversion, and GHL will enrich the contact record later through form fills and tracking. Phone number is worth the friction if you follow up by SMS — otherwise drop it.

Use plain, specific copy. “Book a 20-minute call to review your ad account” converts; “Get started today” doesn’t.

Step 3: Connect the calendar as step two

Step two should be a calendar, not a thank-you page. In the funnel builder, add the Calendar element and attach a GHL calendar with round-robin or a single user, 30-minute slots, and a 4-hour minimum notice.

Make sure the calendar’s confirmation settings send both email and SMS if you collected a phone number. GHL’s default is email only, and the SMS confirmation measurably reduces no-shows for local service businesses.

Step 4: Add the one automation that matters

Go Automation > Workflows > Create Workflow, trigger on Form Submitted for this specific form, then add:

• Wait 5 minutes, send SMS: “Got your request — pick a time here: [link]”
• Wait 24 hours, if no appointment booked, send email with the same link
• Wait 72 hours, if still nothing, move the contact to a “nurture” pipeline stage

The conditional check on “appointment booked” is what separates this from a broadcast sequence. Most GHL accounts built in a hurry send the booking link three times to people who already booked.

Step 5: Test the whole path, including on a phone

Submit the form yourself from a mobile device. Check: does the contact appear in Contacts within a minute, does the SMS arrive, does the booking update the contact’s tag, and does the calendar invite land in your inbox?

Test the calendar on a phone specifically. Timezone handling is the most common failure — a booking showing 2pm in the app and 7pm in the invite means the calendar’s timezone isn’t set to the business location.

What should you skip in week one?

Almost everything else. Funnel A/B testing needs volume you don’t have yet. Membership areas and courses are a separate build. Snapshots from the marketplace are tempting but often bring in dozens of workflows that conflict with yours.

Build the funnel, watch the automate, and leave the rest until you have 50 leads in the system. Then you’ll know which of the extras you actually need.

Is GoHighLevel overkill for a single funnel?

Yes, if that’s all you’ll ever build. You can host a landing page for $0-20/month and connect a calendar for another $0-15. GHL earns its $97 when you need funnels plus CRM plus SMS plus pipelines in one place, or when you’re running several client accounts from one login.

Quick Summary

• Starter is $97/month with unlimited funnels, calendars and 100k contacts.
• Set up the custom domain first; page URLs don’t migrate cleanly later.
• Keep the landing form to three fields and make step two a calendar.
• One workflow: SMS in 5 minutes, conditional follow-ups at 24 and 72 hours.
• Test the booking on a phone — timezone bugs are the most common failure.