GoHighLevel Account Manager — Run Our Documented System Across US Locations — Ramp to Full-Time on a Written Plan

READ THIS FIRST — one question d ---------- whether to apply

If we give you a written spec and a live GoHighLevel account, could you find every single place they differ? The tag named lead_new that should be lead-new, the hardcoded phone number where a custom value belongs, the wait step someone quietly changed? And does that sound satisfying rather than tedious? If yes, this seat was built for you. If you'd rather be architecting funnels from a blank page, this isn't your role. Our system is already designed, built, and documented.

The honest deal on hours and pay
We start small on purpose: 10 hours/week for roughly the first month while you learn our system from its written specs and checklists. Real documentation, not tribal knowledge. Then hours grow with proof, on a plan we put in writing in your offer:

~Month 2: 20 hrs/week — once you own the weekly health checks and have launched your first location
~Month 2–3: full-time, 40 hrs/week — once you own the task board and we're no longer double-checking your work
~Month 6-10: we will review based on how we scale with your help.

If you need full-time income on day one, we respect that — please don't apply. If you have room for a 10-hour ramp with a written path to a stable long-term full-time seat, keep reading.

Who we are:
We run marketing automation for a multi-location US franchise brand. GoHighLevel, Zapier, and Google Scripts are the backbone. We've built a GHL snapshot — workflows, pipelines, custom fields, custom values, Zapier connectors — now rolling out location by location, and every part of it is specced in writing. You'll be trained on high-trust systems; NDA required. We use AI tools (Claude, ChatGPT) daily and suspect you will too.

The job: Keep the system true, and constantly make it better

Five things, in the order you'll spend time on them:

INSTALL — stand up each new location from our onboarding checklist: A2P registration, Domain registration, fields, tags, custom values, Zapier connector config, email forwarding — then run our written verification test suite before anything goes live.
CONFIGURE — keep per-location settings current as customers' details change: custom values, calendars, phone setup. The recurring core of the week.
MAINTAIN — weekly health pass over every live location: workflows firing, integrations connected, messages actually sending. You catch the silent failure before we do. Own the task board, keep the docs matching what's built, and send a short written status every Friday: what shipped, what's monitored, what drifted, what's proposed.
DOCUMENT — all changes per account that is being requested so we know what modifications we made from our standard spec and can best help the customer were things inevitably break.
REPAIR — customers break things. When a workflow stops behaving, you compare the account against the spec, restore it, prove it with a dummy contact, and write up what happened. This skill is the reason the seat exists.

And through all of it: we expect your judgment, not just your hands. You'll be inside this system every day and you'll see what we can't — gaps, fragile patterns, spaghetti worth restructuring, GHL features we should be using. Bring those as short written recommendations / optimizations; the good ones get built into the product, and you get a sandbox where experimenting never needs permission (only shipping to live does). Knowing what to change matters — knowing what to leave alone matters just as much.

The standard

"Done" means tested with a dummy contact and verified — not "I built it"
The spec is the truth. When the account and the docs disagree, you flag it — you never silently "fix" either side
Naming discipline IS the product — clean names, structured workflows, no spaghetti left behind you
You monitor what you ship

You must have:

Real hands-on GoHighLevel experience: you've built and maintained workflows and pipelines in real sub-accounts and can explain what a custom value is without Googling. You do NOT need to be an agency-level architect; you DO need to be past the course-graduate stage
The detective trait: precise, thorough, genuinely enjoys finding the difference between what's written and what's real
Organized, reliable, deadline-keeping habits — half this role is managing the work, not just doing it
Strong written English — documentation and written status updates are half the job
Good spoken English — video check-ins with us multiple times a week at first, and then less frequently as you get comfortable. Will have video calls with customers too.
Basic Zapier familiarity (our connectors are pre-written; you configure and test)

Nice to have: Loom habit · ClickUp or similar · Markdown · experience working alongside AI tools (we run on Claude daily)

How to apply — follow exactly. This is the first test.
Your application must be you, not AI (and yes, I understand the irony as we had AI assist in writing this post). Exactly two things:

A link to a NEW short unscripted video (Loom or phone, 2–3 minutes, talking — not reading): (a) 20 seconds on who you are and your hobbies outside of GHL/automation. (b) walk us through one real GHL workflow or pipeline YOU built — screen-share the account (client data blurred) or screenshots. If it worked perfectly the first time you built it, pick a differnt work flow. Tell us what it does and what BROKE when you deployed it, and then tell us how you fixed it.
A photo of YOU holding a handwritten sign — paper, your own handwriting, your face clearly visible. Big at the top: "I Love GHL". Underneath, smaller:
today's date and your name
the hours (Philippine time) you could work during the 10-hr ramp, and whether you could go full-time at month 2–3. and your salary demands (keep it hourly) for this position.

Rules: AI-written or AI-voiced applications are deleted, no exceptions. At the interview you'll re-answer part of your video live, so a faked application only wastes your own time. Applications missing either part are deleted unread. This takes 15 minutes if you actually know GHL.

When you'll hear back — we put this in writing too: we plan to collect applications through 11:30 PM, Friday, August 28 (Central Standard time), review everything over the weekend, and reply to EVERY applicant by close of business Monday, August 31 — invitation or not, you will hear from us. Applications after Friday go to a second batch we only open if the first doesn't produce a hire.

If you're the person who reads the checklist twice, catches the misnamed tag before anyone else notices, and quietly keeps the whole machine honest — this seat pays you to be exactly that, and it grows with you.