Role overview I run a growth consulting firm that installs AI-enabled systems for service businesses and course creators. We don't just hand clients a Zap and call it done — we build intelligent workflows that connect their full tech stack, incorporate AI decision-making via API, and actually change how their businesses operate. I'm looking for a freelance automation specialist to work with me on an ongoing project basis. This is not a one-off gig. The goal is a long-term working relationship — one where we develop a shared rhythm, you understand how I think about client problems, and the work gets better over time because we know how to collaborate well. You'll be handed a brief, you'll ask the right questions, you'll build something clean, and you'll explain it clearly. That's the job. What you'll build Projects vary by client but typically include: lead scoring and segmentation automations, student churn detection systems for course creators, content repurposing pipelines, morning briefing automations pulling from calendar and inbox, sales call analyzer integrations, custom Slack reporting scenarios, AI receptionist builds for local service businesses, and operations, sales, and client communication workflows across a range of industries. No two builds are identical. Platform agnosticism is essential — you will regularly work across tool combinations you haven't seen before, and I need someone who figures that out without hand-holding. Required skills Make (Integromat) Primary build environment. Advanced scenarios, error handling, and data transformation are expected — not bonus skills. Zapier Some clients are on Zapier. You need to be comfortable in both without missing a beat. Claude API / OpenAI API Experience calling LLM APIs inside workflows for classification, summarization, routing, or content generation. Claude Code familiarity You don't need to live in it, but client builds regularly produce AI-generated code outputs. You need to be able to read, adapt, and explain those outputs clearly — without me translating. CRM fluency At least two of: GoHighLevel, HubSpot, Salesforce, ActiveCampaign, ConvertKit. Course / community platforms Kajabi, Teachable, or Skool. Project management tools Asana, Monday.com, and/or Notion. Communication tools Slack and/or Voxer integrations. Intake-to-delivery workflows You've built end-to-end operational workflows for professional service businesses — law firms, med spas, dental offices, home services, agencies — and you understand the real-world complexity they involve. Light scripting Comfortable writing or adapting simple JavaScript or Python when a build requires it. You don't need to be a developer, but you cannot freeze the moment a build leaves the drag-and-drop layer. Webhook debugging / API auth When something breaks, you're the one who figures out why. I bring the big-picture brief; you own the technical problem-solving. I am not the fallback for "what do we do when this doesn't work." Fluent written + spoken English Non-negotiable. You'll communicate directly with me and occasionally document builds in plain language a non-technical client could follow. Nice to have Background working with marketing agencies or consultants — you understand that client work has a different pace and higher stakes than internal tooling. Familiarity with AI receptionist or voice AI tools (VAPI, Bland, Retell). This is a direction we're actively moving toward, so relevant experience is a genuine growth opportunity in this role, not just a checkbox. Prompt engineering beyond just passing text to an API — you understand how to structure instructions for consistent, reliable outputs inside a workflow. How we work Work is project-based with scope and timeline agreed per project. I provide a brief — you ask clarifying questions before building, not after. Short Zoom calls are sometimes the fastest way to align on a complex brief and you should be comfortable with that. You flag blockers early, not the day before a deadline. Deliverables include a clean build and a brief written or recorded walkthrough of what you built and why. Rate is open — please propose your project rate or hourly in your application. Application questions Please answer both questions. Applications without answers to both will not be reviewed. Question 1 — Technical Describe a Make scenario you built recently that required an API call. What was the workflow trying to accomplish, what did the API call do inside it, and what was the hardest part of getting it to work reliably? Question 2 — Communication & process How do you typically communicate progress on a build, and what do you do when you hit a blocker you can't immediately solve? Walk me through your actual process — not what sounds good, but what you actually do.