Automation & Integrations Developer — GoHighLevel Focus (Long-Term, Task-Based Paid Trial)

Start your proposal with the word **SHIPPED** so we know you read this. We're an established agency running marketing and operations automation for service businesses. Our stack: **GoHighLevel** (multiple sub-accounts), **Zapier**, webhooks/custom APIs, **QuickBooks**, **Shopify**, custom forms with conditional logic and pricing calculators, and conversational + voice AI bots. This is mostly a **GoHighLevel automation role**, but the honest scope is broader: whatever's on fire, half-finished, or untested on a given day becomes your problem too. Why we're being direct about this We've hired developers who had great portfolios and said all the right things in the interview — and then went quiet mid-task, marked things "done" without testing them, or disappeared the moment something broke in production. We've had automations silently fail for days because nobody was watching run history. We've had "finished" builds that were actually 80% finished. We are done being surprised by this. If you're excellent at demos but bad at attendance, follow-through, and finishing the last 20% of a task — this isn't the role for you, and we'd both rather find that out before either of us commits real time. What the job actually is - **Build:** GHL workflows, pipelines, and sub-account setups; Zapier integrations and field mapping; forms with conditional logic and price calculators; conversational and voice AI bots (lead qualification, missed-call textback, call routing) - **Integrate:** third-party API syncs (CRM ↔ QuickBooks, CRM ↔ Shopify, webhooks) — and debug the silent failures that come with them - **Test:** nothing goes live untested. Staging tests and a short Loom walkthrough are part of finishing a task, not an optional extra - **Handle emergencies:** something breaks, a client-facing automation misfires, a deadline gets tight — you show up for it instead of going quiet - **Follow through:** half-built things get finished, documented, and handed off cleanly — not left for someone else to untangle - **Attend:** standups are a contract term, not a suggestion. If you routinely go quiet or miss them, we'll find out fast — see below How We're Vetting This (Task-Based, Not a Class) This isn't a training program — it's one real, practical build from our actual backlog (something like standing up a voice AI intake bot, mapping it into our CRM via Zapier, and building the custom form/calculator that feeds it), paid across 4 milestones so you get paid as you go and we get to see real work at every stage, not just a finished product at the end. | Milestone | Pay | What it takes | | 1 | $15 | Discovery & plan — scope the task, ask the right questions, submit a written plan with time estimates and risk flags | | 2 | $35 | Core build — construct the form/calculator or bot flow in a staging sub-account, correct field mapping and naming | | 3 | $35 | Integration & edge cases — wire it into the rest of the stack via Zapier/webhooks; find and fix planted errors we leave in the test environment | | 4 | $15 | Test, document, ship — staging test proof, a Loom walkthrough, clean documentation, and handoff | **Total: $100 for the test project.** This price is for the test project only — if it goes well, it rolls straight into ongoing paid work, and your rate is negotiated separately based on skill and experience. We're grading more than whether it works: naming conventions, field discipline, whether you found the planted errors, whether your Loom is honest about what's unverified, and whether you delivered on time (or flagged a slip early instead of going silent). Who Does Well Here - Real, shown GHL + Zapier work — Loom required, don't just tell us - Comfortable with webhooks, APIs, and debugging silent sync failures, not just building in the UI - Bonus: QuickBooks, Shopify, Twilio/Voice AI, or custom API experience - Obsessive about naming conventions, documentation, and "the next person can read my work" - Gives honest estimates and hits them — or flags risk before the deadline, not after - Wants stable, long-term work with fixed weekly hours, not a pile of one-off gigs Not a Fit If - You're juggling too many clients to commit fixed hours - You mark things "done" without testing them - You go quiet when something breaks or a deadline gets tight - You need step-by-step instructions for every task Hiring Process 1. Application review (Loom required — see below) 2. Short video call — confirm fixed weekly hours and standup availability 3. Milestone 1: paid discovery & plan 4. Milestone 2: paid core build 5. Milestone 3: paid integration & edge-case handling 6. Milestone 4: paid test, document, ship — strong performers move straight into ongoing weekly work To Apply 1. Link a 2–4 minute Loom walking through a GHL workflow, Zapier automation, or integration you built — what it does and one bug you found and fixed in it 2. What fixed weekly hours (EST) can you commit to, and what other client work are you currently carrying? 3. Describe a time a deadline slipped on you. What did you do — and when did you tell the client? 4. A client-facing automation silently fails for two days before anyone notices. Walk through your first 30 minutes once you find out. 5. What CRM, automation, or API work have you done with QuickBooks, Shopify, or voice/conversational AI? We're looking for someone who finishes what they start, tells us early when something's wrong, and shows up. If that's not you, please don't apply — we'll both save time.