✦ Fathma Mutia · AI & Automation Builder

Your repeat work, running on its own.

For Meta ads and GoHighLevel agencies.

Lead follow-up, client reports, morning checks. Built on tools you already own, live for a 50-client agency.

Fathma Mutia

Fifty clients, read every morning, by one system.

Meta and GoHighLevel in, one screen and a briefed team out. Paid client build, in production on the agency’s own accounts. Hover a card to follow its path; click one to open the case study.Tap any card to open the case study.

  • Every failure visibleA sync that crashes files a failure row, and an account that cannot be read shows as a named failure, never as a zero.
  • 0 lead names kept outside GoHighLevelEach workflow drops the contact before it writes anything and keeps no run history. Counts reach the dashboard; names, phone numbers and messages stay in the CRM.
  • A new lead is checked in secondsThe moment a lead lands in GoHighLevel, its address is checked against that client’s service area and the answer is written back on the contact.

The screen the team opens every morning

Flagship · Paid Client App

Agency Command Center: Meta Ads + GoHighLevel

Each client’s spend, billing, leads and speed to lead, from Meta and GoHighLevel, side by side. Built for an agency with about 50 home-service contractors. Every screenshot is sample data.

The command center's daily triage on sample data: 15 of 35 clients flagged, lead, spend and booking tiles, and a needs-a-hand list

In Production Right Now

Counted on live systems. Not projections.

51
Agency clients synced every morning
108
Ad accounts inventoried for one agency
60+
Production AI workflows
40
Client accounts running my GoHighLevel workflows
7
Live web & app builds
  • Read-only, on accounts you ownMeta and GoHighLevel through your own API access. Nothing writes back without your OK.
  • Alerts where your team already worksA chat channel, a direct message, a task on the board. Nobody has to remember to check.
  • Documented for handoffExported workflows and a plain-English guide, so your team runs it without me.

Fifty Clients. Fifty Tabs. Checked by Hand.

You find out on Friday

A card fails on Tuesday, and the first person to notice is usually the client, in Friday’s report.

Spend in one tool, leads in another

Meta has the spend. GoHighLevel has the leads. Cost per lead and speed to lead live in neither, so the report is built by hand and the misses slip through.

Reports that say success while the data is dead

One agency's stats feed had been dead for six and a half months. Every run still reported success. The reports kept going out.

All fixable. Build it once, make every failure visible, and it keeps running. The same goes for any task your team repeats by hand.

A day in the system.

Every time below is a real schedule on the agency’s own n8n, in Central time. The team arrives to numbers that are already checked.

  1. Touch-base check: who last spoke with each client
  2. Facebook Page snapshot per client
  3. New ad accounts matched to their client
  4. Lead-quality sweep, 7 days of conversations, counts only
  5. Meta sync: 28 days of spend, leads, billing
  6. GoHighLevel sync: leads per day, jobs won, stages
  7. Lead-quality alerts open one task per client
  8. Hourly: alerts to each client’s channel and the team
  9. Real time: lead events in, service area checked in seconds

If any step crashes, the error rail files a failure row and alerts the team. The morning screen shows a failed sync, never yesterday’s numbers.

How I Work

Same four steps, every engagement. Written or on a call.

  1. 01

    Map the manual work

    A free call, or your task in writing. What your team does by hand today, what you run, what a system can take over.

  2. 02

    Blueprint

    A scoped proposal: what I build, what it costs to run per month, when it ships.

  3. 03

    Build in the open

    You review the real thing on live URLs. Feedback ships in fast rounds, often on the call.

  4. 04

    Handoff that sticks

    Working system, exported workflows, a plain-English guide. You own everything.

Fathma Mutia

From manual chaos to systems that run themselves.

Physics degree, two years as a virtual assistant, HighLevel certified admin. I build on the Meta and GoHighLevel APIs every day. I've done the copy-paste. Now I build what erases it.

More About Me

Who this is for.

Five seconds to know whether to keep reading.

✓A good fit

  • Meta-ads agencies running GoHighLevel for home-service clients, ten to a hundred accounts.
  • Service businesses with one task the team repeats every week: lead follow-up, client reporting, checks done by hand.
  • Teams already on Meta, GoHighLevel, n8n, Sheets or Supabase. I build on what you own; nothing moves to a tool of mine.
  • Owners who want failures visible, not reports that always say green.

×Not a fit

  • You want more leads from ads. I don’t run ad campaigns; my work starts when a lead arrives: follow-up, routing, reporting.
  • A chatbot that “does everything”. I automate reading, sorting, drafting and clear decisions, with a human on anything irreversible.
  • Nothing exists yet: no tools, no leads, no process. Automation needs a task your team already does every week, so that comes first.
  • You need it by Friday. A first version takes weeks; you get a realistic date on the call, before anything starts.

How pricing works.

No price list, because no two weekly tasks are the same. The method is always the same.

TIER 1
The smallest version that solves itOne workflow or one screen. Proves the idea on your real accounts before anything bigger.
TIER 2
The full buildEverything in the blueprint, with alerts, logging and the handoff guide.
TIER 3
The build, kept runningTier 2 plus a monthly retainer: monitoring, fixes when an API changes, small additions.

Four rules on every quote

  • Three tiers, always. You pick the size; nothing is hidden in a single number.
  • Build cost and run cost, separately. What I charge to build, and what it costs you per month to run: tools, API calls, hosting, in real figures.
  • Real per-run numbers. Lead research about $0.15 per company. The scrape-score-rebuild engine about $8 per 1,000 leads.
  • You own everything. Workflows, code, accounts and keys stay yours. No hourly meter on systems work.

Not ready for a call? Send the task.

Four lines is enough. I reply within one working day with whether it’s worth automating, what I’d build, and a rough cost.

What happens next

Your message lands in my inbox and on my phone the moment you send it. No list, no newsletter, no follow-up sequence. If the timing is wrong for your team, say so and I’ll check back only when you ask.

  • Arrives in my inbox, with your email as reply-to
  • Pings my phone at the same moment
  • One reply within one working day, Philippines time
No account, no newsletter. Your message goes only to me.

Questions I Get a Lot

We map the manual work and your stack. If it fits, you get a scoped proposal: what I'd build, what it costs to build and run, when it ships. No obligation.

Send the task in writing: what it is, how often it happens, which tools it lives in. I reply within one working day with whether it's worth automating, what I'd build, and a rough cost. If the timing is wrong for your team right now, say so and I'll check back when you ask, not before. Send it in writing →

Read-only, on accounts you own: a Meta system user scoped to reads, your GoHighLevel agency API, your own n8n and database. Nothing writes back. Any write needs your OK first.

Reading, sorting, drafting, extracting, choosing between clear options. Grounded in your data, with a human approving anything irreversible. I'll say when the answer is "don't automate this."

I quote both. Every build comes with real per-run numbers: lead research about $0.15 per company, the scrape-score-rebuild engine about $8 per 1,000 leads.

Both. Audit and untangle what you have, or build from zero. Rebuilding is the last resort.

The working system, exported workflow files, and a plain-English guide: what triggers it, what it needs, how to run it. Nothing is locked to me.

Yes. Projects, ongoing or full-time remote. Philippines (GMT+8), overlap hours around your timezone.

Available for remote work

Have one task your team repeats every week?

Lead follow-up, client reports, support emails, anything repetitive. Bring it to a free 30-minute call or send it in writing. I'll tell you honestly whether it's worth automating, what I'd build, and roughly what it costs. No prep needed.

Send the task in writing

I reply within one working day: whether it's worth automating, what I'd build, and a rough cost. No obligation.

To mutia.fathmaaliah@gmail.com

Or paste it wherever you already talk to me: WhatsApp, LinkedIn, a reply to any email.