HighLevel Expert to Own Our Funnel, Sub-Accounts and Deliverability, 20 to 25 hrs/wk Ongoing

Read this whole post before applying. The last section tells you exactly how to apply, and I will not read applications that skip it. Who we are: Restaurant Scaling System. We help independent restaurant owners build marketing systems that actually make money. I am a Michelin-awarded restaurateur and former President of the California Restaurant Association, and this is a real operating business, not an agency reselling templates. Our entire revenue engine runs in GoHighLevel: the masterclass funnel that fills our coaching program, a nurture list of about 6,600 people, 11 Instagram trigger-word automations, roughly 80 client sub-accounts, and a six-restaurant agency account. What I actually need: I need one person to own GoHighLevel. Not help with it. Own it. I have hired for this three times in seven months. Every time, the same thing happened. Not because the people were unskilled, but because: 1. Work was reported as done when it was not tested 2. An automation went live on a published post with nothing built behind it 3. Hardcoded dates shipped a June event date to a July audience 4. A workflow bug quietly dropped 71 of 266 registrants and nobody caught it 5. Messages went unanswered for days with no stated working hours 6. Builds existed that only one person understood, so every departure reset us to zero. I ended up doing the build myself at 11pm If you read that list and thought "those are basic things," you might be the right person. This job is not technically exotic. It is about being the person whose work is finished when they say it is finished. The work: Every two weeks, the masterclass cycle. Flip all dates across the funnel using custom values. Two Zoom webinars configured and tested end to end. Cohort tags rotated. Qualification form and DQ branches verified. Homework unlocks staged. No-show pull and downsell executed. Registrant counts reconciled against Meta ads. Day 1 show-up reported with a recommendation. Weekly. Five nurture emails to 6,600 contacts, hourly drip in batches of 700 to 1,000, all landing 6:00am to 10:00am Pacific. Traffic survey send and sync. Freshdesk tickets under a 24-hour SLA. Monthly. Newsletter builds and sends across six restaurant sub-accounts, design editor only so they stay editable, mobile-checked. Gift card campaign sequences with tight open and close windows. Ongoing. New client sub-account provisioning at 6 to 10 per month against a 10-step checklist. A2P 10DLC registration through to approval. Email deliverability per sub-account: sending sub-domains, SPF, DKIM, DMARC, warmup, bounce and complaint monitoring. Wallet and card health. Instagram comment-to-DM workflows inside the 24-hour window. Make.com scenarios. Monday.com sync. How we work together: -Post your working hours in Pacific time in week one, then work them. I can plan around any constraint you declare. I cannot work with silence. If you do not work weekends, say so on day one and I will build around it. -Acknowledge with a time, not an emoji. "Looking at this now, you will have it by 4pm Pacific" is an acknowledgement. A thumbs up is not. -Set your own deadlines and hit them. You pick the date. If it is going to slip, tell me before it slips, not after. -Test your own work. If I find the bug, the process failed. Nothing is done until you have tested it end to end in the live environment and told me what you tested. -Document as you build. Short written entry plus a Loom for anything non-trivial. No build may exist that only you understand. -Dates live in custom values. Never hardcoded. This is the single most expensive mistake in our history. -Hold your own credentials. I should never have to tap a 2FA prompt for you to do your job. -If the platform will not do it, bring me two workarounds and a recommendation. "GHL can't do that" is half an answer. Requirements Demonstrable deep GoHighLevel experience: workflows with real branching and date logic, custom values, Surveys including multi-step and partial submission capture, funnels and pages, email design editor, Smart Lists and tags, Conversations and SMS, calendars, sub-accounts and snapshots, wallet and rebilling, A2P 10DLC, Social Planner and the Instagram DM API Working knowledge of email deliverability: sending sub-domains, SPF, DKIM, DMARC, warmup, diagnosing bounce and spam-complaint problems Make.com, comfortable building and debugging Minimum four hours of overlap with 9:00am to 1:00pm Pacific, Monday through Friday Excellent written English. Most of this job is writing clearly to busy people Solo only. You do the work. No agencies, no subcontracting, no account managers between us Nice to have: Monday.com, Zoom Webinars and Zoom API, Square, WordPress and Elementor at an embed level, Freshdesk, restaurant or hospitality client experience. Terms 20 to 25 hours per week, ongoing and long term, flexing up during a masterclass week Weekly invoicing with a task-level breakdown of hours We start with one paid trial project, roughly 3 to 4 hours at your hourly rate, described below. It is real work, you get paid for it either way, and it decides whether we move to the retainer 30-day and 90-day reviews against written targets THE PAID TRIAL PROJECT If your application makes the shortlist, I will pay you your full hourly rate for this. Roughly 3 to 4 hours. In a GHL sub-account I give you access to, build a small date-driven event reminder sequence: Three emails and one SMS, timed off a single event date Every date reference driven by custom values, nothing hardcoded anywhere An if/else guard so that if the event date has passed, nobody receives the sequence A tag applied at each touch so completion can be reported Then deliver three things with it: A written handoff doc: what it does, what triggers it, what it depends on, what breaks if it fails, where the custom values live A short Loom walking me through it Your own QA log: what you tested, how you tested it, and the defects you found and fixed in your own build before showing it to me That third item is the actual test. I am not grading the build, I am grading whether you QA yourself. HOW TO APPLY Skip the template cover letter. Answer these questions directly, in order. Applications that do not are not considered. Link or screenshot one GHL workflow you built with 15 or more steps and real branching logic. Tell me what it does in two sentences. Describe a bug you caught in your own work during QA, before the client or your boss saw it. What was it, and how did you catch it? Describe a time you shipped something broken. What happened, and what did you change in your process so it would not happen again? I would rather read an honest answer here than a claim that it never happens. What are your working hours in Pacific time, and what is your rule for weekends when a live campaign breaks? A GHL sub-account throws a high bounce rate warning and email sending gets paused. Walk me through the first five things you check, in order. Start your application with the word CUSTOMVALUE so I know you read to the end.