GoHighLevel (GHL) Implementer + Trainer (Part-Time) – Build Backend After Demo Acceptance

Overview
We run live demos for businesses. Once a prospect accepts the demo, we need the GoHighLevel backend set up end?to?end for launch.

You will implement pipelines, workflows, numbers, booking, tagging, and automations so the system is operationally functional (tested end?to?end).
You will also train a junior (George) 2× per week for 1 hour each session via Loom/Zoom.

This is part?time to start.

What “operationally functional” means (Definition of Done)

A build is complete only when:

1) GHL backend is built

Pipeline stages created (example: New ? Responded ? Booked ? Confirmed ? Showed ? No-show ? Rescheduled ? Closed Won/Lost)

Tags and attribution set up cleanly

Calendar / booking configured + tested

2) Messaging + numbers work

Phone number(s) connected and assigned correctly

Reply handling works reliably:

YES / Interested

RESCHEDULE

STOP / DNC (must immediately stop all messages)

3) Reminders & confirmations work

Confirmation message after booking

Reminder(s) (e.g., 24h before)

Basic no-show recovery flow

4) End-to-end QA is proven

You must test a contact through:

message ? reply ? booking ? confirmation ? reminder ? STOP logic
and confirm it works.

Training requirement (George)

You will provide:

2 × 1-hour training sessions per week (recorded)

A Loom walkthrough for each build so George can replicate it

Training sessions format:

Session 1: You build + explain

Session 2: George builds + you review/correct live
(Goal: George becomes self-sufficient.)

Deliverables (how you’ll be paid)

We prefer:

Fixed price per build/deliverable (clear scope, clear outcome)
Plus:

Hourly pay for the 2 × weekly training sessions

You can propose your preferred structure when applying.

Requirements

Strong hands-on GHL experience (pipelines, workflows, calendars, numbers, tags)

Clean SOP / documentation habits (Loom + notes)

Comfortable training a junior

Reliable communication

How to apply (IMPORTANT)

Start your message with: PIPELINE
Then send:

2–3 examples of GHL systems you’ve built (briefly describe what they did)

Your GHL experience length (months/years)

Your preferred pay structure (per deliverable + training hourly, or alternative)

Confirm you can do a paid sandbox test task