GHL Automation and Workflow Specialist

READ THIS BEFORE APPLYING
One question d ---------- whether you should apply: can you take a written spec — every custom field, tag, custom value, and workflow, with exact names — and rebuild it in a fresh sub-account so precisely that a side-by-side audit finds ZERO differences, then document what you built well enough that a stranger could rebuild it from your doc alone? If that sounds tedious, do not apply. If that sounds satisfying, keep reading — this seat was built for you.

This is not a beginner VA role, and "I finished a GHL course" does not qualify you.

One note before you dive in: the bar here looks intense on purpose — not because the day-to-day is. We're a small, supportive team and this is a long-term seat; we'd rather set a high bar once and find our person than sort through a hundred generic applications. Quality over quantity — if that resonates, we'd love to meet you.

WHO WE ARE
We run marketing automation for a multi-location US franchise brand. GoHighLevel and Zapier are the backbone of everything we deliver. We've built a GHL snapshot (workflows, pipelines, custom fields, custom values, Zapier connectors) that we're rolling out location by location — you'll be trained on high-trust systems, NDA required.

THE ROLE — MAINTENANCE & DELIVERY
You own the snapshot — the build AND everything after it ships. This is a flat-salary role, not hourly, and that's deliberate: we pay for outcomes, so the better you are at GHL, the better this deal gets for you. An expert who delivers in 15 focused hours a week earns the same as someone who grinds 25 — we will never ask you to log hours, only to deliver.

DELIVERY (building forward):
- Build and maintain snapshot assets: workflows, tags, custom fields, pipelines, custom values — to a strict written naming convention
- Set up new sub-accounts from our onboarding checklist (fields, tags, custom values, Zapier connector configuration, email forwarding)
- Test every workflow with dummy contacts and record Loom walkthroughs

MAINTENANCE (keeping it true):
- Weekly health pass over every live location: workflows firing, integrations connected, messages actually sending — you catch the silent failure before we do
- Keep our markdown documentation in sync with what's built — drift found is drift flagged, same week
- A short written status every Friday: what shipped, what's monitored, what drifted, what's proposed. This is how we know the system is healthy without watching over your shoulder

INITIATIVE & INNOVATION (making it better):
- You are expected to find room for improvement — gaps in the snapshot, better workflow patterns, GHL features we're not using yet. Bring at least one concrete improvement proposal a month; we approve, you build
- You get real room to innovate: a sandbox account that is yours to prototype in — new automations, AI integrations, patterns you've wanted to try. Experimenting needs no permission; only shipping to the live snapshot does. Show us what you're playing with in the Friday status — the good ideas get built into the product
- We want an owner with ideas, not just a pair of hands. If a month goes by and you haven't suggested anything, something is wrong

THE STANDARD — READ CAREFULLY
- "Done" means tested with dummy contacts and verified on a Loom — not "I built it." We check our own work here
- Naming discipline IS the product. You notice when something is lead_new instead of lead-new — clean naming, structured workflows, no spaghetti. Disorganized builders create expensive chaos and don't last here
- The docs must match the build, always. When you find them drifting apart, you flag it — you never silently "fix" either side
- You monitor what you ship. If a workflow misfires after a change, you catch it before we do — not the other way around

YOU MUST HAVE
- 1+ years hands-on GoHighLevel experience — you can explain the difference between a snapshot, a sub-account, and a custom value without Googling
- Built or maintained GHL workflows and pipelines for a real business (agency experience a plus)
- Basic Zapier experience (you don't need to code; our connectors are pre-written — you configure IDs and test)
- Strong written English — half this job is documentation
- Excellent spoken English — you'll be on video calls with us 2–3x/week explaining what you built and why; your application video should show us you're comfortable talking through technical work out loud

NICE TO HAVE
- Loom/screen-recording habit; A2P/phone setup exposure; Markdown/GitHub
- Experience working alongside AI tools — we run on Claude daily, and our SOPs assume it

WHAT YOU GET
- A fully documented system to work from — written specs and SOPs, not guesswork; training provided
- $350 twice monthly ($700/month), flat — paid via Wise on the 15th and 30th; 13th-month pay; PH holidays respected; raise review at 6 months. Expect roughly 20 focused hrs/week of real work; we pay for delivery, not logged hours
- Flexible schedule, but 2 hrs overlap with US Central mornings (9pm–12mn PH) for check-ins 2–3x/week
- A clear path to FULL-TIME as our location roster grows (full-time conversion includes an HMO/health allowance), and a growth path into feature building and project management — we are building a product, not filling a seat
- A long-term seat, not a one-off gig

HOW TO APPLY — FOLLOW EXACTLY. THIS IS THE FIRST TEST.
We use AI tools daily in this business and you will too. But your application must be you, not AI — we need to hear how you actually think and talk about GHL. Typed essays are exactly what AI is good at faking, so we don't want typed essays. Your application is exactly two things:

1. A link to a short UNSCRIPTED VIDEO (Loom or phone recording, 3–4 minutes, talking — not reading a script), in two parts:
(a) 20 seconds on who you are and why this role specifically.
(b) GHL PROOF OF WORK: walk us through one real funnel, pipeline, or workflow YOU built — screen-share the actual account (client data blurred), or screenshots if you've lost access. It must be a real build: at least 8 actions including at least one wait and one if/else branch — no two-step "tag added ? send email" demos. Tell us what it does, why you built it that way, and what broke the first time you deployed it.

2. A photo of a HANDWRITTEN NOTE (on paper, in your handwriting) with:
- the words PURPLE SNAPSHOT
- today's date and your name
- the hours (Philippine time) you would typically work
- the words "$700/month works for me" — or the monthly salary you'd need instead

RULES: AI-written or AI-voiced applications are deleted, no exceptions. At the interview we will ask you to re-answer one of your video questions live, so a faked application only wastes your own time. Applications missing either part are deleted unread. If you actually know GHL, this takes 15 minutes.

If you're the person who double-checks everything and catches the misnamed tag before anyone else notices — this seat pays you to be exactly that.