CRM and Automations Specialist (Full-Time, Remote — PH)

About Amplified

When their phone rings, that's us.

We build systems that work, run campaigns that perform, and answer to clients who pay us to deliver.

Over the last year we've built a stack of AI-powered automations. AI qualification bots, lead-routing flows, WhatsApp sequences, GHL pipelines that quietly do a huge amount of work we used to do by hand every morning. It runs. Now it needs an owner: someone to keep it healthy, extend it, and build the next layer.

What You'll Actually Do

• Wire the full path: Meta lead form → GHL contact created → WhatsApp confirmation → calendar booking link, with the goal of every step firing inside 90 seconds of submit. Then build the error handling so it doesn't die silently at midnight. This is normally done through make or n8n.
• Stand up GHL pipelines per client vertical (FA, insurance, property), each with its own stage triggers and follow-up logic. You'll take a client's messy process and turn it into a clean flow.
• Build webhook listeners that catch lead data from landing pages, Typeform, and survey tools, and drop each lead into the right GHL sub-account with the right tags.

• Build GHL conversation-AI bots on the OpenAI API: prompt engineering, context injection, fallback handling, clean handoff to a human when it's time. These bots qualify leads. They're not glorified auto-replies.
• Set up Make.com or n8n scenarios that call GPT to classify inbound messages, draft personalised follow-ups, or summarise a lead's history before anyone on the team opens the conversation.
• Keep the bots current as client offers, qualifying questions, and objections change. This is a living system, not build-once-and-walk-away.

• Audit GHL sub-accounts for dead automations, broken webhooks, and leads that slipped through. Things break quietly. Your job is to catch it before the client feels it.
• Build Make.com / n8n syncs between GHL and outside tools (sheets, Notion, reporting dashboards) without duplicating or losing a record.
• Document everything you build: what it does, what fires it, what breaks it. Six months from now, you or a teammate should understand the flow in five minutes flat.

• When a client asks "why didn't I get that lead notification?", you dig in, find the actual cause, and write back a clear answer: what went wrong, what's fixed. Not "we're looking into it."
• Join client check-ins when automation is on the agenda. You won't run the call, but you'll need to explain your work in plain English to someone who's never heard the word "webhook."

• Build the automations that take repetitive work off the team — spinning up new client sub-accounts, scheduling reports, firing alerts when something upstream goes sideways.
• Scope new ideas with the founder: is this worth building, how long, which tool. Your read on that matters, and we want it.

How We Work / What We Value

Ownership is the floor, not the ceiling. If you built it, it's yours — including when it breaks at an inconvenient hour. "That's not my task" isn't a phrase we use. If a client's affected and you're the fastest person to fix it, you fix it.

You don't have to be a writer. You have to think before you type.

No scorekeeping. A teammate's underwater and you've got air — you ask what they need, you don't wait to be asked, and you don't tally who carried what. The load is never split evenly on any given week; some weeks you carry more. If "but I'm already doing more than them" is a sentence you've said at work, this will frustrate you, and you'll frustrate us.

People who treat this as "just a job to execute" do fine for a few months, and then we both feel it. We'd rather you self-select out now than three months in.

We give you room. We'll tell you the outcome we need and hand you the context. Then we get out of the way and trust you to figure out the how. No looking over your shoulder.

• Your first instinct when a flow fails is hunting for whose fault it is, not fixing it.
• "It works, mostly" is good enough for you, and checking edge cases feels like a waste of time.
• You get defensive when someone gives you feedback. We give feedback often, and it's never personal.
• You send client replies that are technically a response but don't actually answer the question.
• You're still learning GHL from scratch. We need someone who opens the platform and immediately knows where to go.
• You enjoy office politics. Small team. There's nowhere for it to hide and no patience for it.
• You'd describe yourself as someone who "just needs clear instructions to execute." This role needs someone who scopes their own work and speaks up when something doesn't make sense.

If any of those made you bristle instead of nod — we're probably not a fit, and that's completely fine. Better we both know now.

What We're Looking For

• Hands-on, production experience with GoHighLevel — sub-accounts, pipelines, workflows, conversation AI, automation triggers. Not "I've poked around." Real builds for real clients.
• Hands-on experience with Make.com — multi-step scenarios, error handling, API modules, data mapping. You know exactly what to do when a module throws a 422.
• OpenAI API — Bot-building is the biggest chunk of this role.
• Comfortable building and debugging HTTP requests from scratch — headers, auth (API key, Bearer, basic OAuth), JSON payloads, webhook setup. You don't need a no-code wrapper to hit an API.
• Able to read and write JSON
• Clear written English with non-technical clients.

• n8n — even basic cloud or self-hosted experience is a real plus.
• A background in digital-marketing tools or CRM management (any CRM — the logic carries over).
• A track record debugging multi-step automations where the failure point isn't obvious.

• IDR 8-10M/month, based on your real depth in the stack. The top of that band is for someone who brings the full picture — GHL + Make mastery plus n8n and hands-on OpenAI API bot-building, not just one or two. We'll be straight with you about where you land and why.
• 13th-month pay, as standard.
• Full-time, fully remote, Indonesia-based.
• Async-first, with a structured daily overlap window with the Singapore team.
• Direct line to the founder. No layers, no chain to run things up, no bureaucracy.
• You'll work on systems live businesses depend on, not internal dashboards nobody opens.
• The stack keeps growing, and so does the scope. If you want to go deep on AI automation instead of staying a generalist, this is the seat.