Pipeline Training

Pipeline training is the onboarding segment where you teach the client how to manage their deals and leads through visual pipeline stages inside GHL. This covers creating opportunities, moving them through stages, understanding what automations fire at each stage, and using the pipeline as a daily management tool. Not every client build includes pipeline management, but for those that do, this training determines whether they actually use it or let leads pile up unmanaged.

Why This Matters

A pipeline without training is just a pretty board with cards on it. The client will look at it once, not understand why deals are in certain stages, and never touch it again. Meanwhile, leads sit in the “New” column for weeks because nobody moved them forward. Automations that were designed to trigger at specific stages never fire because the client does not know they need to drag the card.

Trained clients treat their pipeline as a daily dashboard. They open it in the morning, see which deals need attention, move cards forward, and close more business as a result. The visual nature of pipelines works incredibly well for business owners who think spatially. Seeing 15 cards in “Proposal Sent” and only 2 in “Closed Won” tells an immediate story about where the bottleneck is.

Agencies that skip pipeline training see a consistent pattern: the pipeline stays in whatever state it was at handoff, automation triggers stop firing because cards are not moving, and the client eventually asks “what is this pipeline thing for?” three months later during a support call. That is three months of missed opportunity management.

How to Think About It

Start with the big picture before diving into mechanics. Explain what each stage means in the context of the client’s specific business. A roofing contractor’s pipeline stages are different from a med spa’s pipeline stages. The stages should have been designed during the build phase to match how the client actually moves a lead from first contact to closed deal.

Then walk through the daily workflow. New lead comes in and appears as a card. The client reviews the lead, reaches out, and moves the card to the next stage. At each stage, explain what happens: does an automation send a follow-up email? Does a task get created? Does a notification go to a team member? The client needs to understand that moving a card is not just organizational. It triggers real actions in their system.

Keep the training focused on what the client does manually versus what the system does automatically. Some stage transitions are manual (the client drags the card). Some are automatic (a workflow moves the card when a form is submitted or an appointment is booked). Making this distinction clear prevents confusion about why cards sometimes move on their own.

Common Mistakes

Training on pipeline mechanics without connecting to the client’s actual sales process. Do not teach “here is how you drag a card.” Teach “when you finish the estimate and the customer says they want to move forward, you drag the card from Estimate Sent to Proposal Accepted, and the system automatically sends the contract.” The mechanics must be wrapped in business context.

Not explaining automation triggers at each stage. If you built workflows that fire when a card enters a specific stage, the client needs to know about them. Otherwise, they will be confused when emails go out or tasks appear. Walk through each stage and explain: “When a card moves here, this happens automatically.”

Overcomplicating the pipeline for the initial training. If you built a complex pipeline with eight stages and multiple automations, do not try to cover every detail in the onboarding call. Focus on the three or four stages the client will interact with most frequently. The edge cases and advanced stages can be covered in follow-up training or documentation.

Forgetting to show the opportunity detail view. Pipeline training is not just about the board view. Show the client how to click into an individual opportunity, see the full contact history, add notes, update values, and track the deal amount. The detail view is where the real management happens. The board view is just the navigation layer.

Not connecting pipeline to reporting. Show the client how to see basic pipeline metrics: total value by stage, conversion rates between stages, and average time in each stage. Even a quick overview of reporting makes the pipeline feel like a business intelligence tool rather than just a task board.

Tools Involved

Pipeline training centers on the Opportunities feature in GHL. The pipeline view, opportunity cards, stage management, and deal values all live here. If you have built workflows that trigger at specific pipeline stages, reference those during training so the client understands the automation layer. The Conversations tab connects to pipelines since the client will often move a deal forward after a conversation with the lead. On mobile, show the client how to view and manage their pipeline from the GHL app as covered in Mobile App Training.

Where This Fits

Sequence position 24, during the Live Onboarding Call. Pipeline training typically comes after the Conversations Deep Dive since the client needs to understand how communication flows before they can understand how deals progress through stages. This segment is only relevant if the client’s build includes pipeline management. If it does not, skip this and allocate the time to other training segments like the Build-Specific Walkthrough.

Common Questions

What if the client has never used a CRM pipeline before? Start with the analogy of a physical whiteboard with sticky notes in columns. Each column is a stage, each sticky note is a deal. You move the sticky note across the board as the deal progresses. Most business owners understand this immediately, even if they have never used digital pipeline software.

Should the client manage the pipeline daily or weekly? Daily is ideal. The pipeline should be part of the client’s morning routine: open the board, check for new leads, follow up on stale deals, move cards that progressed. A pipeline checked weekly accumulates stale data and missed follow-ups. Frame it as a five-minute daily habit, not a weekly planning session.

What if the client has multiple services that need separate pipelines? If you built multiple pipelines during the build phase, train on the primary one first. Get the client comfortable with the mechanics and daily workflow on one pipeline before introducing additional ones. Trying to train on three pipelines simultaneously creates confusion and reduces retention.