GoHighLevel Pipeline Setup: Step-by-Step Guide (2026)

This GoHighLevel pipeline setup guide is for small businesses and agencies who have HighLevel running but still track deals in their heads, in a spreadsheet, or in a pipeline nobody trusts. A good pipeline is simple: a few clear stages that match how you really sell, every lead turned into an opportunity automatically, stage changes that trigger the next action, and a warning when a deal sits still too long. Below you'll find the plain-English terms, the exact clicks in HighLevel, the workflows to connect, and the mistakes I see most often when I'm asked to fix a messy pipeline.

TL;DR

• Plan before you click. Write down the real steps a lead goes through, from first contact to paid. Five to seven stages is plenty for most small businesses.
• Build it in Opportunities → Pipelines. In your sub-account, open Opportunities, select Pipelines, then Create new pipeline. Pipeline names must be unique in the sub-account, and stage names must be unique inside a pipeline.
• Don't add "Won" and "Lost" as normal stages. HighLevel tracks outcomes with four fixed statuses: Open, Won, Lost and Abandoned. In the updated Pipelines experience, HighLevel also says Won and Lost stages are created automatically.
• Let workflows create opportunities. Use a trigger like Form Submitted or Customer Booked Appointment, then the Create/Update Opportunity action so every new lead lands in the right stage without anyone typing it in.
• Use stage changes as triggers. The Pipeline Stage Changed trigger lets you send a task, a notification or an email the moment a deal moves.
• Catch deals that go quiet. The Stale Opportunities trigger fires when a deal has stayed in the same stage for a set number of days. It is not retroactive, so add it early.
• Record why you lose. Edit the Lost Reason options in Settings → Custom Fields so your lost deals teach you something.
• Keep it owned. One person owns the pipeline design. Everyone else follows it.

Key terms in plain English

HighLevel's own getting-started guide explains the structure as Contact → Opportunity → Pipeline → Stage. Here's what each part means in everyday language.

• Contact: a person in your CRM. One contact can have more than one opportunity, for example a first purchase and a later upsell.
• Opportunity: one potential deal with one contact. It has a name, a value, a stage, a status, an owner and a source. Think of it as a card on a board.
• Pipeline: the full sales or service process you want to track, shown as a board of columns. You can have more than one pipeline, such as "New Sales" and "Renewals".
• Stage: one column on that board. A stage is a step in your process, such as "New Lead", "Call Booked" or "Proposal Sent".
• Status: the outcome of the deal. HighLevel has four fixed statuses: Open (still being worked), Won (they bought), Lost (they said no or picked someone else) and Abandoned (nobody plans to follow up). HighLevel says these status types and names cannot be changed.
• Lost Reason: a field that records why a deal was lost. You can edit the list of reasons in custom fields.
• Opportunity value: the amount the deal is worth. This is what powers pipeline value in dashboards.
• Workflow: HighLevel's automation builder, found under Automation → Workflows. A workflow starts with a trigger and runs actions.
• Trigger: the event that starts a workflow, like a form submission, a booked appointment or a pipeline stage change.
• Action: a step a workflow takes, like creating an opportunity, sending an email, creating a task or notifying a team member.
• Stale opportunity: a deal that has sat in the same stage for too long with no change.

What is a GoHighLevel pipeline?

A GoHighLevel pipeline is a visual board inside the Opportunities section that shows every open deal as a card in a column, where each column is a step in your sales or service process. It tells you where each lead stands, what it's worth, and what should happen next, so nobody has to guess or keep it in memory.

HighLevel describes pipelines as a way to "organize and automate your sales or service workflows by visually tracking opportunities through defined stages". That last part matters. A pipeline is not only a picture. Once the stages are clear, you can hang automation off each one: a reminder when a lead books a call, a task when a proposal goes out, an alert when a deal hasn't moved in a week.

For a small business, the pipeline usually answers three questions every morning:

1. How many new leads came in, and has someone contacted them?
2. Which deals are close to closing, and what's blocking them?
3. Which deals have gone quiet and need a nudge or a decision?

If your current pipeline can't answer those in under a minute, it needs a rebuild, not more stages.

Why does pipeline setup matter for small businesses?

Pipeline setup matters because most small teams don't lose deals to competitors first. They lose them to silence: a lead nobody called back, a proposal nobody followed up, a "let me think about it" nobody chased. A clear pipeline with automation makes those gaps visible and gives each one an owner and a next step.

Here's what usually goes wrong without a proper setup:

• Leads stay as contacts. Someone fills in a form, the contact is created, but no opportunity is ever made. The lead never appears on the board, so nobody sees it.
• Stages are vague. "In progress" or "Follow up" could mean anything. Two people read the same board and see different things.
• Outcomes are hidden. Lost deals are deleted or left open forever, so reports are wrong and you can't see why you lose.
• Nobody notices stuck deals. A deal can sit in "Proposal Sent" for a month before anyone checks.
• Reporting is useless. Without values and statuses, the dashboard can't tell you what's in the pipeline or what you've won.

Speed matters here too. I wrote a full piece on why lead response time matters for small businesses. A pipeline that creates the opportunity and alerts the right person the moment a lead arrives is the simplest way to shorten that time.

Step 1: Plan your stages on paper first

Before you open HighLevel, write down how a lead really moves through your business today. Not how you wish it moved. How it actually moves.

Ask yourself:

• Where do leads come from? (Website form, Facebook lead ads, phone calls, referrals, booking link.)
• What is the first thing that should happen after a lead arrives?
• What has to happen before you can send a price or a proposal?
• What is the "yes" moment? A signed proposal, a paid invoice, a booked first session?
• What happens after the yes? Does onboarding belong in this pipeline or in a separate one?

HighLevel's getting-started guide gives its own checklist before you begin: what sales process you want to track, which stages a lead normally moves through, whether you'll add opportunities manually, by import or automatically, and which team members will manage them. It's a good list. Answer it before you build.

A simple rule for stages

Each stage should describe something that has happened, not something you hope will happen. "Call Booked" is a fact. "Interested" is a feeling. Facts are easier to automate and easier to report on.

Sample stage sets you can copy

These are examples to adapt, not rules. HighLevel itself notes that its sample stages are suggestions and should be customised for your business.

Service business (consulting, agency, coaching):

1. New Lead
2. Contacted
3. Call Booked
4. Call Done
5. Proposal Sent
6. Negotiation

Local service or appointment-based business:

1. New Enquiry
2. Contacted
3. Appointment Booked
4. Showed Up
5. Quote Given
6. Follow-up

Agency selling to other businesses:

1. New Lead
2. Qualified
3. Discovery Call Booked
4. Proposal Sent
5. Contract Sent

Notice that none of these lists include "Won" or "Lost". That's on purpose. We'll come to why in a moment.

How many stages should a pipeline have?

Most small businesses do well with five to seven open stages. Fewer than four and the board stops telling you anything useful. More than eight and people stop updating it, because every deal needs too many clicks. If you find yourself adding a stage for every small step, that step is probably a task, not a stage.

Step 2: Create the pipeline in HighLevel

Now open HighLevel. These steps follow HighLevel's own "Step-by-Step Guide: Creating Pipelines", which was updated in 2026 for the new Pipelines experience.

1. Go into the sub-account where you want the pipeline.
2. Click Opportunities in the left sidebar.
3. Select Pipelines from the top menu.
4. Click Create new pipeline in the top-right corner.
5. Enter a clear Pipeline Name, for example "New Sales".
6. Click Save.

Two rules to know:

• Pipeline names must be unique in the sub-account. You can't create two pipelines with the same name.
• Stage names must be unique inside each pipeline.

Add and order your stages

With the pipeline created, add the stages you planned in Step 1:

1. Enter a Stage Name.
2. Click Add stage to add the next one.
3. Repeat until your list is complete.
4. Use the up and down arrows to put stages in the right order.

Set stage colours

HighLevel now lets you colour each stage. Open the pipeline, go to the Stages tab and pick a colour for each one. You can choose no colour, a coloured dot or a background tint. The colours show in Kanban and list views and on opportunity cards.

A simple colour plan works best: cool colours for early stages, warm colours for stages close to a decision. Don't use colour to mean three different things.

Decide what shows in reports

Next to each stage you'll see funnel and pie chart icons. These control whether the pipeline and each stage appear in funnel and pie chart reports on your opportunity dashboards. Leave the main sales stages on. Turn off any "holding" stage you don't want to skew your funnel.

What about Won and Lost?

HighLevel's step-by-step guide says that Won and Lost stages are created automatically in the updated Pipelines experience, so you don't need to add them yourself. Separately, every opportunity has one of four statuses: Open, Won, Lost or Abandoned. Use those statuses to record outcomes. Don't build your own "Closed Won" or "Dead Lead" stages on top. If you do, you'll end up with deals that sit in a "Closed" stage while their status still says Open, and your reports will be wrong.

Step 3: Add your existing deals

You probably already have deals somewhere: a spreadsheet, another CRM, a notebook. HighLevel gives you three ways to get opportunities into a pipeline, and you can mix them.

Add one opportunity manually

1. Go to Opportunities.
2. Click Add opportunity.
3. Pick an existing contact or enter a new one.
4. Fill in the pipeline, stage, value and other details.
5. Click Create.

Import many opportunities from a CSV

1. Go to Opportunities and click Import.
2. Choose Opportunities and click Next.
3. Upload your file.
4. Map each column to the right opportunity field.
5. Check the preview and click Start Bulk Import.

Clean the file first. Remove duplicates, make sure every row has a contact email or phone, put stage names exactly as they appear in HighLevel, and fill in values where you know them. If you're coming from HubSpot, my HubSpot to GoHighLevel migration guide covers the export and mapping side in more detail.

Step 4: Create opportunities automatically with a workflow

This is the step that turns your pipeline from a board into a system. Instead of hoping someone remembers to create a card, a workflow does it the moment a lead arrives.

HighLevel's getting-started guide walks through a form example:

1. Go to Automation → Workflows.
2. Click + Create Workflow and choose Start from Scratch (or a template).
3. Click + Add New Trigger, choose Form Submitted, select your lead form and click Save Trigger.
4. Click + to add an action, choose Opportunity → Create/Update Opportunity.
5. Pick the pipeline and stage for new leads, set the status to Open and add a value if you know it.
6. Decide on Allow Opportunity to Move. Turn it on if you want the same opportunity to update when the contact comes back through the workflow later.
7. Click Save Action, then switch the workflow from Draft to Publish.

From then on, every new form submission lands in your chosen stage.

Other triggers that work well

HighLevel lists other common triggers you can pair with the same Create/Update Opportunity action:

HighLevel's note on this is worth repeating: the Create/Update Opportunity action stays the same. Only the trigger changes. Pick the trigger that matches when a lead should appear on your board.

Name opportunities so you can read the board

Set a naming pattern in the action, such as the contact's full name plus the service: "Sara Ahmed – Website Package". When the board is full, you'll read names, not IDs.

Set the source

If your action lets you set an opportunity source, use it. "Website form", "Facebook ad", "Referral". When you look back at won deals later, you'll know which channel is worth more of your time.

Step 5: Make stage changes do the work

Once opportunities flow in, the next job is to make each stage trigger the right next step. HighLevel's Pipeline Stage Changed trigger does this. According to HighLevel, it activates when an opportunity moves from one stage to another and can be filtered by pipeline, stage, assigned user and lead value.

How to set it up

1. Go to Automation → Workflows and create a new workflow.
2. Click + Add New Trigger and search for Pipeline Stage Changed.
3. Add filters: the pipeline and the stage the deal moves into.
4. Click Save Trigger.
5. Add your actions.
6. Publish, then test by moving a test opportunity into that stage by hand.

Actions that make sense per stage

HighLevel suggests actions like sending a notification to the assigned rep, updating opportunity details, creating a follow-up task, starting another workflow and sending an email to the contact. Here's how that looks on a service pipeline:

Should every stage trigger a message to the lead?

No. Internal actions (tasks, notifications, assignments) are almost always safe. Messages to the lead should only go out where they clearly help, like confirming a booked call. If every stage move sends an email, people get spammed every time someone tidies the board, and your email reputation suffers. My GoHighLevel email deliverability checklist explains why that matters.

Track outcomes with the status trigger

HighLevel also has an Opportunity Status Changed trigger, plus an Opportunity Created trigger. Use the status trigger for things that should happen on a win or a loss. For example, when status becomes Won, notify the person who handles onboarding. When status becomes Lost, add a tag so the contact can go into a long-term nurture list later, with their consent.

Step 6: Catch stale deals before they go cold

The Stale Opportunities trigger is the single most useful pipeline automation for small teams. HighLevel describes it as a trigger that activates when an opportunity has been in the same stage for a set period without progress or updates.

How to set it up

1. Go to Automation → Workflows and click + Create Workflow, then Start from scratch.
2. Click + Add new Trigger and choose Stale Opportunities.
3. Name the trigger, for example "Stale – Proposal Sent".
4. Click Add Filters and set Duration in Days, the pipeline and the stage.
5. Click Save Trigger, add actions and publish.

How many days count as stale?

HighLevel's own answer is that it depends on your sales cycle: two to three days may be enough for short cycles, while longer cycles might need seven to ten days. Start with the shorter end for early stages like "New Lead" and "Contacted", and give later stages like "Proposal Sent" more time.

What should the stale workflow do?

Keep it internal first:

• Create a task for the deal owner: "This deal hasn't moved in 5 days. Call, update or close it."
• Notify a manager if it's a high-value deal.
• Reassign it if the owner is away.

Two things to know

• It's not retroactive. HighLevel says the stale duration is only counted after the trigger is added. Deals that were already stuck before you set it up won't fire on day one. Review those by hand once.
• It resets. If the deal moves stage or is updated, the timer resets. If it goes stale again, the workflow can run again.

Step 7: Record why deals are lost

Lost deals are data. If you don't record why you lose, you'll keep losing for the same reasons.

HighLevel added a Lost Reason field you can manage in opportunity custom fields. To edit it:

1. Go to Settings → Custom Fields.
2. Find Lost Reason.
3. Click Bulk Actions → Edit.
4. Add, rename or delete reasons, then save.

HighLevel notes that renaming a reason updates it everywhere it's used, and lost reasons are included when you export opportunities.

Keep the list short and clear:

• Price too high
• Chose another provider
• No response
• Not a fit
• Timing, try later

To find lost deals later, go to Opportunities, open Advanced Filters, set Status to Lost and apply. HighLevel's FAQ walks through exactly that.

Step 8: Assign owners and keep the board clean

A pipeline nobody owns turns into a junk drawer. Two kinds of ownership matter:

• Deal owner: each opportunity should have an assigned user. That's who gets the tasks and alerts. If you use round-robin or rules to assign leads, my GoHighLevel Router setup guide covers lead routing in detail.
• Pipeline owner: one person decides the stages, the naming, and the automations. When someone wants a new stage, they ask that person. This stops the slow creep of extra columns.

A weekly 15-minute pipeline review

Once a week, the pipeline owner opens the board and checks:

1. Any opportunity without an owner? Assign it.
2. Any opportunity without a value? Add one, even a rough estimate.
3. Any deal open for longer than your normal sales cycle? Decide: push, pause or close as Lost or Abandoned.
4. Any stage with a pile-up? That's where your process is slow.
5. Any workflow errors? Check the workflow history for failed actions.

You'll also find HighLevel's audit logs useful. Its FAQ explains that clicking the opportunity ID on an opportunity card opens audit logs showing activity on that opportunity over the last 60 days. That's handy when someone asks, "Who moved this deal?"

How do I set up a pipeline in GoHighLevel?

To set up a pipeline in GoHighLevel, open your sub-account, click Opportunities, select Pipelines, then click Create new pipeline. Give it a unique name, add your stages in order, set stage colours and report visibility, and save. Then create a workflow that adds new leads to the first stage automatically using the Create/Update Opportunity action.

That covers the build. To make it useful, add three more things: a Pipeline Stage Changed workflow for your most important stages, a Stale Opportunities workflow for stages where deals tend to stall, and a short list of Lost Reasons. With those in place, your pipeline tells you what's happening and nudges your team when something stops.

What stages should a GoHighLevel pipeline have?

A GoHighLevel pipeline should have stages that match the real steps your leads go through, usually five to seven. A common pattern for service businesses is New Lead, Contacted, Call Booked, Call Done, Proposal Sent and Negotiation. Use statuses for outcomes (Won, Lost, Abandoned) instead of building separate closed stages for every result.

The best test is simple. Take your last ten deals. Could you place each one in exactly one stage without arguing about it? If yes, your stages are clear. If two people would put the same deal in different stages, merge or rename them until the answer is obvious.

What is the difference between a pipeline stage and an opportunity status?

A pipeline stage shows where a deal is in your process, like Call Booked or Proposal Sent. An opportunity status shows the deal's outcome: Open, Won, Lost or Abandoned. Stages are fully customisable per pipeline. Statuses are fixed by HighLevel and can't be renamed. Use stages for progress and statuses for results.

Mixing the two is the most common setup mistake. If you have a stage called "Lost" and a status called Lost, people will update one and forget the other, and your reports will disagree with your board.

How do I move opportunities automatically in GoHighLevel?

You move opportunities automatically in GoHighLevel with workflows. Choose a trigger such as Customer Booked Appointment, Form Submitted, Contact Tag or Payment Received, then add the Create/Update Opportunity action with the target pipeline and stage. Turn on Allow Opportunity to Move so an existing opportunity updates instead of staying where it was.

If an opportunity didn't move when you expected, HighLevel's FAQ points to the usual suspects: the workflow isn't published, the contact didn't meet the trigger conditions, the action isn't configured, the wrong pipeline or stage is selected, or Allow Opportunity to Move is off.

Should I use one pipeline or several?

Use one pipeline per distinct process, not per person or per lead source. A small business usually needs one sales pipeline, and maybe a second for onboarding or renewals if those follow different steps. Use filters, owners and sources to split the view. More pipelines mean more workflows to maintain and more places for deals to hide.

Good reasons for a second pipeline:

• Different steps. Selling a one-off project and renewing a monthly plan are different journeys.
• Different teams. Sales and onboarding are handled by different people with different goals.
• Different reporting. You want to see new sales value separately from renewal value.

Bad reasons for a second pipeline:

• One pipeline per salesperson. Use the assigned user filter instead.
• One pipeline per lead source. Use the opportunity source instead.
• "We tried a new layout." Rename or reorder stages instead of starting fresh.

Agency tips: setting up pipelines across sub-accounts

If you're an agency running HighLevel for clients, pipeline setup has a few extra rules.

• Build a standard pipeline once, then adapt. Most of your clients in one niche will share a similar process. Start from your standard version and change only what's different.
• Agree the stages with the client in plain words. Show them the stage list on one page before you build. If they can't explain a stage, they won't use it.
• Train the client on statuses. Show them how to mark a deal as Won, Lost or Abandoned, and why it matters.
• Document the automations. For each stage, write down what workflow it triggers. When something breaks months later, you'll thank yourself.
• Hand over ownership. Name one person on the client side as pipeline owner.

If you're weighing whether HighLevel is the right base for this in the first place, I compared GoHighLevel and Zapier for small businesses and broke down the real cost of GoHighLevel in 2026.

Connecting your pipeline to other tools

Not every lead starts inside HighLevel. Some come from tools like Typeform, Calendly, Stripe or a custom site. You have two main options:

1. Use HighLevel's own forms, calendars and payments where you can, so triggers like Form Submitted, Customer Booked Appointment and Payment Received work natively.
2. Use an integration tool like Zapier or n8n to push contacts and opportunities into HighLevel from other systems.

If you go with an integration tool, keep the rule simple: one tool creates the opportunity, and HighLevel workflows handle what happens after. Don't have Zapier and a HighLevel workflow both creating opportunities for the same lead, or you'll get duplicates. If your Zaps have grown messy over time, my Zapier audit checklist is a good place to start, and the n8n vs Zapier comparison helps if you're choosing between the two.

Common GoHighLevel pipeline setup mistakes

These are the problems I see most when someone asks me to look at their pipeline.

1. Too many stages

Twelve columns, half of them empty. Every extra stage is another click for your team and another place for a deal to get stuck. Merge until each stage means something.

2. Stages that describe feelings

"Warm", "Interested", "Maybe". Replace them with events: "Call Booked", "Proposal Sent".

3. No automatic opportunity creation

Contacts come in, but nothing creates the opportunity, so the board is always behind. Fix it with a Create/Update Opportunity action on every lead source.

4. Duplicate opportunities

Two workflows (or a workflow plus a Zap) both create a deal for the same lead. Pick one source of truth and use "create or update" logic.

5. Closed stages instead of statuses

"Closed Won" and "Dead" as regular stages, with status still Open. Use HighLevel's statuses for outcomes.

6. No values

Without values, the pipeline can't tell you what it's worth. Even a rough estimate is better than nothing.

7. No stale alerts

Deals sit for weeks unnoticed. Add a Stale Opportunities workflow to the stages where deals tend to stall.

8. Automations that spam leads

Every stage move fires a message to the contact. Keep most stage actions internal.

9. Nobody owns the design

Everyone adds stages and workflows when they feel like it. Name one owner.

A copy-ready GoHighLevel pipeline setup checklist

Work through this list in order. Tick each item only after you've tested it.

Plan

• Wrote down the real steps from first contact to paid
• Picked five to seven stages, each describing a fact
• Decided which outcomes use Won, Lost and Abandoned statuses
• Listed every lead source

Build

• Created the pipeline in Opportunities → Pipelines with a clear, unique name
• Added and ordered stages
• Set stage colours
• Set funnel and pie chart visibility for each stage

Fill

• Imported existing deals from CSV, with stages mapped correctly
• Added values and owners to every open deal

Automate

• Workflow creates an opportunity for every lead source (Create/Update Opportunity)
• Allow Opportunity to Move set the way you want
• Pipeline Stage Changed workflows for your key stages
• Opportunity Status Changed workflow for Won and Lost
• Stale Opportunities workflows with sensible day limits
• All workflows published and tested with a test contact

Report and maintain

• Lost Reason options edited in Settings → Custom Fields
• Pipeline owner named
• Weekly 15-minute review on the calendar

See a working example

If you want to see how a HighLevel setup like this looks in practice, I keep a few demos on my site. These are demos, built to show how the pieces fit together, not client results:

• GoHighLevel demo: a sample HighLevel setup
• AI automation demo: AI as a feature inside a business system, such as sorting or summarising incoming leads
• n8n reliability demo: how to keep integration workflows from failing silently

FAQ

Can I have more than one pipeline in GoHighLevel?

Yes. You can create several pipelines in a sub-account, each with its own stages. Each pipeline name must be unique. Most small businesses need one sales pipeline and, at most, a second one for onboarding or renewals.

Do I need to create Won and Lost stages in GoHighLevel?

No. HighLevel says Won and Lost stages are created automatically in the updated Pipelines experience. Outcomes are tracked with four fixed statuses: Open, Won, Lost and Abandoned.

Can I rename opportunity statuses in GoHighLevel?

No. HighLevel says the four status types and their names cannot be changed. You can rename stages and edit Lost Reason options, but not the statuses themselves.

What happens to deals when I delete a pipeline stage?

In the updated Pipelines experience, HighLevel asks you to choose a destination stage when you delete one. All opportunities in the deleted stage move to the stage you pick, so they aren't lost.

Why didn't my workflow create an opportunity?

Check that the workflow is published, that the contact met the trigger conditions, that the Create/Update Opportunity action is configured, and that the right pipeline and stage are selected. These are the checks HighLevel lists in its own FAQ.

Does the Stale Opportunities trigger work on old deals?

No. HighLevel says it isn't retroactive. The stale timer only starts counting after you add the trigger, so review deals that were already stuck by hand.

How many days before a deal counts as stale?

It depends on your sales cycle. HighLevel suggests two to three days for short cycles and seven to ten days for longer ones. Use shorter limits for early stages and longer ones for proposal stages.

Can I import deals from a spreadsheet?

Yes. Go to Opportunities, click Import, choose Opportunities, upload your CSV, map the columns and start the bulk import. Clean duplicates and match stage names before you upload.

Who moved this opportunity?

Open the opportunity and click its ID in the bottom left. HighLevel opens audit logs that show activity on that opportunity over the last 60 days.

Should Zapier or HighLevel create my opportunities?

Use HighLevel workflows where the lead starts in HighLevel (forms, calendars, payments). Use Zapier or n8n only for leads that start in other tools. Never let both create the same opportunity.

Want me to check your GoHighLevel pipeline?

If your pipeline feels messy, deals slip through, or nobody trusts the board, I can help. I set up and fix GoHighLevel, Zapier and n8n systems for small businesses and agencies, including pipelines, opportunity workflows, stale-deal alerts and the integrations that feed them.

Start here: DM me the word "audit" on LinkedIn, or visit yousufmesalm.com and get in touch. I'll look at how your pipeline and automations are set up and tell you what to fix first.

Packages on my services page:

• Starter, $399: delivered in 7 days
• Growth, $599: delivered in 14 days
• Full system, $899: delivered in 28 days

Care plans to keep everything running after launch, including monitoring and small fixes: $80, $130 or $200 per month.

Sources

• HighLevel: Step-by-Step Guide: Creating Pipelines
• HighLevel: Getting Started – Setup Pipelines and Opportunities
• HighLevel: Workflow Trigger – Pipeline Stage Changed
• HighLevel: Workflow Trigger – Stale Opportunities
• HighLevel: Automating Opportunities
• HighLevel: A Guide to Understanding Opportunities in HighLevel
• HighLevel: Editing Opportunity Status
• HighLevel: Opportunities – Frequently Asked Questions
• HighLevel Changelog: The "Lost Reason" field is now available in Opportunity Custom Fields Settings