Pipelines and stages
One pipeline per sales process. Stages match decisions your team actually makes (Inspection booked, Estimate sent, Signed), with values and lost reasons.
A GoHighLevel CRM implementation is the account itself, set up properly: pipelines, custom fields, tags, calendars, forms, phone and email, lead routing and the first set of follow-up workflows. The work is scoped from how your business sells, written up before we start, and tested before it goes live.
GoHighLevel CRM implementation is the done-for-you build of your sub-account: pipelines, custom fields and tags, forms, calendars, phone numbers with A2P registration, an authenticated email domain, lead routing, the first follow-up workflows and a dashboard. One location with one sales process takes 3 to 5 weeks and costs $500 to $4,000, quoted in writing after a free 30-minute call.
One pipeline per sales process. Stages match decisions your team actually makes (Inspection booked, Estimate sent, Signed), with values and lost reasons.
A short list of custom fields and a tag naming rule (source-, status-, service-) that the workflows and reports depend on.
Forms, surveys, the chat widget, missed-call text back, Facebook and Google lead forms, each writing a source and an owner to the contact.
The right calendar type for each appointment (round robin, service, class), buffers, Google or Outlook sync per user, confirmations and reminders.
LC Phone or ported numbers, A2P 10DLC brand and campaign registration, a dedicated sending domain with SPF, DKIM and DMARC.
Assignment rules, new-lead response, appointment reminders and no-show recovery, internal notifications. More workflows come under the automation service.
A dashboard for open opportunities, stage conversion, source performance and response time.
A pipeline copied from a snapshot built for a different business. Stages like "Hot" and "Warm" that nobody updates.
No rule for tags and fields, so there are three versions of "source" and the smart lists are useless.
Calendars connected to one person's Google account, no round robin, no buffers, reminders off.
A sending domain never authenticated and A2P registration never finished, so email lands in spam and texts fail quietly.
Nobody who can say what each workflow does.
Seeing two or more of these? On the free call we audit your account live and tell you which one to fix first.
Book the free audit call →Pick the one that suits you. Both are free, and neither commits you to anything.
A video call with our team, at a time you pick. We audit your account with you on screen.
Not ready to talk? Send your website or HighLevel setup and we record what we would fix first.
Screenshots from real accounts. Client names have been cropped out.



Workflows read and write the pipeline stage. Reports read the same stage. Keep that rule and the account stays understandable.
| Piece | The decision | Guide |
|---|---|---|
| Pipeline | One per sales process; stages as states | Pipeline setup |
| Fields and tags | Field, custom value or tag | Fields and tags |
| Routing | Round robin, weighted or by rule | Lead routing |
| Calendars | Service, round robin, class or collective | Calendar setup |
A GoHighLevel CRM implementation configures seven areas of the sub-account in a fixed order: pipelines, fields and tags, lead capture, calendars, phone and email, routing with the first workflows, and reporting. Each area has a decision behind it that we write down before we touch the menu.
| Area | Where it lives in GoHighLevel | The decision we make with you | Guide |
|---|---|---|---|
| Pipelines and stages | Opportunities > Pipelines | One pipeline per sales process; stages named as states the team can verify (Estimate sent, Signed), with lost reasons | Pipeline setup |
| Custom fields and tags | Settings > Custom Fields; tags under Contacts | Field for data you filter or report on, tag for a state that triggers a workflow, custom value for text that repeats in messages | Fields and tags |
| Lead capture | Sites > Forms, Surveys, Chat Widget; Settings > Integrations for Facebook and Google | Every entry point writes a source and an owner; no form submits without landing in a pipeline | Speed to lead |
| Calendars | Calendars > Calendar Settings; Settings > My Profile for each user's Google or Outlook sync | Round robin, service, class or collective per appointment type; buffers; which user's calendar is the source of truth | Calendar setup |
| Phone and email | Settings > Phone Numbers; Settings > Phone System (A2P); Settings > Email Services > Dedicated Domain | LC Phone or ported numbers; A2P brand and campaign filed on day one; a sending subdomain with SPF, DKIM and DMARC | A2P fixes |
| Routing and first workflows | Automation > Workflows | Assignment rule (round robin, weighted or by rule), new-lead response, reminders, no-show recovery, internal alerts | Lead routing |
| Reporting | Dashboard; Reporting | Open opportunities by stage, stage conversion, source performance, first-response time | Pipeline mistakes |
The order matters. Fields and tags come before forms because forms write to fields. Phone and email come before workflows because a workflow that sends from an unregistered number fails quietly. Reporting comes last because it only reads what the other six areas write.
The same seven areas are configured in every build; what changes is how many of each, how many people need routing, and how much testing repeats. This is why a solo build and a multi-location build sit at opposite ends of the price ladder.
| Item | Solo operator | One location, small team | Multi-location or agency with sub-accounts |
|---|---|---|---|
| Pipelines | 1 | 1 to 2 | 1 per location or a shared pipeline with a location field, decided in discovery |
| Users and routing | 1 user, no routing | 2 to 8 users, round robin or by service | Per-location teams, routing by location then by availability |
| Calendars | 1 to 2 | 3 to 6 (service, round robin, consult) | Per-location calendar sets, often a class or collective calendar |
| Phone and A2P | 1 number, 1 A2P campaign | 1 to 3 numbers, 1 campaign | Numbers per location; one brand, one or more campaigns, or one registration per sub-account |
| Workflows at launch | 4 to 6 | 6 to 12 | A tested set saved as a snapshot and loaded per sub-account |
| Testing passes | 1 | 1 full pass plus a role pass | One pass per location plus cross-location routing tests |
| Timeline | 3 weeks | 3 to 5 weeks | 6 to 10 weeks |
| Our fee | From $500 | $500 to $4,000 | Custom quote in writing |
Franchise and agency builds are described separately on the franchise page and the agency page; the snapshot-per-sub-account method is the same one we use for SaaS mode.
The fee covers design, configuration, testing, training and documentation inside your GoHighLevel sub-account. It does not cover the subscription, usage, copywriting at volume, or software outside HighLevel.
| Included | Not included (quoted separately or paid to HighLevel) |
|---|---|
| Discovery session and a written architecture document you approve | HighLevel subscription: $97, $297 or $497 a month at the time of writing (full cost guide) |
| Pipelines, fields, tags, forms, calendars, routing, first workflows, dashboard | SMS, email, phone and AI usage, billed by HighLevel through the wallet (usage costs) |
| A2P 10DLC brand and campaign filing, sending domain authentication | Carrier registration fees HighLevel passes through, and the days to weeks the carriers take to approve |
| Contact import with a field map and validation counts | Cleaning a badly exported list by hand beyond the agreed map (quoted separately as a fixed price) |
| Message copy for the first workflows, written with you | Long nurture sequences, funnels, websites and ad campaigns (separate scope) |
| Recorded training per role and a written account map | Ongoing changes after the 30-day review (a monthly support plan) |
| Native integrations: Stripe, Google and Outlook calendars, Facebook and Google lead forms | Custom API work and two-way syncs with other software (API and MCP) |
Most implementation projects start inside an account that already exists. These are the failures we find most often, what causes them, and the fix we apply. Each row links to the troubleshooting page that owns the problem.
| Symptom | Usual cause | Fix |
|---|---|---|
| Texts send from the app but never arrive | A2P brand or campaign not approved, or rejected for a website without a privacy policy | Refile with matching business details and consent language; see A2P registration rejected |
| Emails land in spam | Sending from the shared domain, or SPF, DKIM and DMARC never added | Dedicated sending subdomain, authenticated, warmed; see emails going to spam |
| New leads sit unowned for hours | No assignment step; forms create contacts but not opportunities | Assign-to-user action and create-opportunity action in the capture workflow; see lead routing |
| Bookings double up or land on the wrong person | Calendar synced to one Google account, no round robin, no buffers | Per-user sync, correct calendar type, buffers and availability; see calendar not syncing |
| Three versions of "source" in smart lists | No tag naming rule; fields added ad hoc by different people | Field and tag dictionary, bulk merge, workflow updated to write one source field |
| Workflows show Total enrolled but nothing happens | Workflow in Draft, trigger filter too narrow, or re-entry off | Read the Execution Log, fix the filter, publish; see workflows not triggering |
| Dashboard numbers nobody trusts | Stages used as to-do lists, opportunities without values, won deals never closed | Rename stages as states, require value on create, close-won workflow moves the stage |
The SVNP gym case study shows this kind of rebuild on a real account, with the numbers the client reported.
If you want this built. Bring your current account, or a description of how leads reach you, to a free 30-minute call. We audit the account for free, tell you what we would build first, and quote the scope in writing. Book the call.
Sources checked November 2, 2026: HighLevel help, "Import Contacts into HighLevel" (CSV only, Contacts > Import, file size limit stated as 50 MB) and "CSV File Format for Importing Objects" (header row must match existing fields, duplicate matching by contact ID, email or phone, 30 MB limit on that page); HighLevel pricing page (Starter $97, Unlimited $297, Founder $497 a month). Platform limits change; we re-check them at the start of every project.
Platform facts are checked against the HighLevel help center and HighLevel pricing.
Step one is free. The full ten-step method with deliverables is on the process page.
30 minutes, your questions and your account on screen, a written quote within 24 hours.
A working session: lead sources, who answers, what a sale is, which tools stay.
Pipelines, fields, tags, calendars and a workflow list, in a document you approve.
Configuration in your account, or in a staging sub-account first for risky changes.
Test contacts through each path: form, missed call, booking, cancellation, no-show.
Recorded walkthroughs per role and a written map of the account.
Response times, stage conversion and Execution Logs, then the first changes.
Every project gets one fixed-price quote in writing within 24 hours of the free call, so the price matches the work. These are the bands at the time of writing.
Multi-location and multi-pipeline builds are a custom quote. The price moves with the number of pipelines, lead sources and integrations, and whether an existing account needs cleaning first.
Real accounts, with the numbers the clients reported. We do not publish percentage promises.
GoHighLevel gym case study: five lead sources tagged at entry, a coach on every lead and a consult pipeline. 2,088 contacts, 65 opportunities (Oct 2026).
Read the case study →A GoHighLevel Jobber integration for a handyman business: review requests on paid jobs, missed call text back and a registered phone line. 353 runs by Oct 2026.
Read the case study →Source: the rollout plan described in this guide
Source: our process page
GoHighLevel lead routing with Assign to User: equal or weighted round robin, the only-unassigned toggle, dynamic user IDs,…
Read →GoHighLevel pipeline setup step by step: where to create it, naming stages, opportunity statuses, required lost reasons,…
Read →GoHighLevel custom fields hold data per contact, custom values are reusable placeholders, tags are labels. When to use each,…
Read →GoHighLevel calendar setup: service, round robin, class and collective calendars, availability, buffers, Google sync and the…
Read →Checked October 19, 2026, at the time of writing; HighLevel changes prices, features and policies.
Three to five weeks for one location with one sales process, including testing and training. Multi-location or multi-pipeline accounts take 6 to 10 weeks, mostly because discovery and testing repeat per location. The process page lists the ten steps and what you receive at each.
Basic setup and single-location implementation run $500 to $4,000, quoted in writing after a free 30-minute call that includes a free audit of any existing account. Multi-location work is a custom quote. The setup cost page breaks the range down, and the cost estimator gives a first figure from your own numbers.
Yes. The platform is self-serve, and the GoHighLevel setup guide walks through it in order. Most owners who hire us tried first: the account works, but routing, A2P registration, the sending domain or the pipeline design was skipped, and leads leak.
Yes, we audit it first, keep what works, rebuild what does not, and document the result. We do not reset an account unless the data model cannot be saved, and never without your approval. The free account health check shows the kind of items the audit lists.
Either way. You can hold your own subscription (Starter $97, Unlimited $297 or Founder $497 a month at the time of writing) and give us access, or we provision a sub-account under our agency with a written transfer path. Your contacts, numbers and data are yours in both cases. The plan comparison explains which plan fits.
A snapshot is a saved copy of another HighLevel sub-account's pipelines, workflows, forms and calendars. An implementation starts from your sales process, builds only what you need, tests it with test contacts and documents it. A snapshot can be a starting point inside an implementation, but on its own it is a template with someone else's assumptions in it.
By CSV through Contacts > Import, against a field map you sign off. We create the custom fields first so every column lands in the right place, and set the duplicate rule (email, phone or contact ID) before the file runs. HighLevel imports CSV only, so exports from other tools are cleaned first.
That is the aim. Each role gets recorded training on the parts of the account it uses, and you get a written map of pipelines, fields, tags and workflows. Support is optional afterwards through a monthly support plan, not required to keep the account running.
Access to your current account or CRM if you have one, a description of how leads reach you and what happens to them, your business details for A2P registration (legal name, EIN, website with a privacy policy) and someone who can approve the architecture document. Most delays come from slow approvals or access, not from the build.
Turn repetitive work into tested workflows: speed-to-lead, booking, nurture, reviews.
Read more →SaaS mode, plans, rebilling and snapshots for a branded software offer.
Read more →A branded HighLevel experience on your own domain, set up precisely.
Read more →Pick a time that suits you. We open your account with you, audit it live and send a written quote within 24 hours. If it is not a fit, we say so on the call.
Prefer not to talk yet? .
Free GoHighLevel strategy call
Pick a day
You are booked.
Before the call
Need a different time? Reschedule or cancel.
Free GoHighLevel strategy call
Pick a day
You are booked.
Before the call
Need a different time? Reschedule or cancel.
Free 30-minute call with a free account audit. Every price is a custom quote in writing.