I build the systems that run the business while you sleep.
I specialize in GoHighLevel lead systems — AI bots that qualify every lead, scoring that decides who's worth a call, and routing that acts on it automatically. Around that core I build the whole stack: automations, CRM, API integrations and the dashboards that prove it works. One person, the whole system, built to hold up in production.
Free · 20 minutes · no pitch — we look at your setup and whether I can help.
n8n
Twilio
WhatsApp Business
Meta Ads
Cloudflare
JavaScript
Node.js
OpenAI
Claude
MailgunNot a pair of hands. The person who owns the whole build.
Takes the ticket. Builds exactly what the ticket says. Marks it done when the workflow is switched on. If the lead still didn't get a call, that's a new ticket.
Take the whole problem, not a slice of it. Design the system, build it, wire the tools together, test it with real data, and hand it over documented. When something breaks at 2am it's traceable, because I built it to be, not stitched together from parts nobody can explain.
One lead, from cold contact to assigned agent.
Five questions, no human involved, answers stored as data rather than buried in a chat thread. Sales only ever sees the leads worth their time.
One person, the whole system.
I'm a full-stack automation and systems person. I build the workflows, wire the CRM, connect the tools through their APIs, add the AI where it earns its place, and put reporting on top so you can see it working. One person who can take a messy operation and turn it into a system that runs itself.
I take businesses that run on manual work and spreadsheets and turn them into systems: CRM, automation, AI, and reporting, built to run without someone watching them. Most recently ran the full acquisition and automation infrastructure for a lead-gen operation across three markets.
- Automation
-
Workflows that run themselves: n8n, Make, and native CRM automation. Webhooks in, logic in the middle, results written back. Scheduled jobs, retries, and failure alerts so nothing silently breaks. If it's repetitive, it shouldn't be done by hand.
n8nMakeWebhooksScheduled jobsError handling
- CRM systems
-
GoHighLevel end to end: workflows, triggers, pipelines, calendars, custom fields and values, surveys and forms, tag architecture, cross-sub-account routing, agency view. A CRM that's structured and enforced, not a junk drawer people stop trusting.
GoHighLevelPipelinesWorkflowsSub-accountsData hygiene
- Custom systems & APIs
-
The hard part most people can't do: gluing tools together through their APIs into one system. Serverless workers, custom dashboards, server-side tracking, database-backed jobs. When no off-the-shelf integration exists, I build it.
GHL API v2Cloudflare WorkersJavaScriptNode.jsREST APIs
- AI & conversational
-
AI put where it earns its keep. Conversational bots for SMS and voice: qualification scripts, extraction into CRM fields, guardrails, kill-switches. RAG agents grounded in your own docs so answers are real, not guessed. LLM-powered steps inside automations.
OpenAIClaudeRetell AIAssistable.aiRAG
- Messaging & comms
-
Twilio and Meta at a technical level: WhatsApp templates through approval, A2P registration, per-segment cost modeling, deliverability, and re-engaging a cold list without getting the number restricted.
TwilioWhatsApp Business APIMetaA2P 10DLC
- Reporting
-
Live dashboards that reconcile data across sources: spend against outcomes, per-source attribution, cost per result. Server-side conversion tracking. Numbers you can actually make decisions on, not vanity metrics.
KPI dashboardsMeta CAPIAttributionData viz
- How I stay honest
- I build systems, not sales pitches. Offer strategy, pricing, and copy belong to you and your marketer. I'll tell you what the data says, then build whatever the decision needs.
Built and running. Not theorized.
Owned the entire acquisition stack for a lead-gen operation across the US, AU and UK — AI bots qualifying leads on SMS and voice, writing to CRM fields, scoring, routing, and booking the good ones automatically. One operator, start to finish.
Split paid and organic traffic for clean attribution, then merged them through one shared bot, page and calendar so nothing gets maintained twice — reschedule-safe workflows, no-show recovery, and country-gated routing across sub-accounts.
See the architecture →A serverless dashboard reconciling CRM, calendar and ad-spend data into live cost-per-booked-call — per-source attribution, paid vs organic, in one view. Built with a Cloudflare Worker and APIs because no off-the-shelf tool did it.
See it live — interactive demo →Designed a WhatsApp re-engagement and qualification architecture for a 20–30k-lead backlog — batched to protect the number's quality rating, running qualification inside the free service window instead of paying per template. Ties Twilio, Meta and GHL into one system.
Seen enough? Let's look at your setup.
Twenty minutes, no pitch — we walk through what's manual or broken and whether I can build the fix.
The part most builds get wrong.
Questions before build, not after
The expensive mistakes get made in the first hour: which calendar, which pipeline, what actually counts as qualified. I ask those before touching anything, not halfway through.
Done means verified
A workflow that's switched on is not a workflow that fires. Every build gets tested with real leads down the real path, and you see the evidence.
It should explain itself
You get a system your team can read without booking a call with me. Named consistently, documented, handed over so it survives without me in it.
Root cause, not a patch
If a lead slipped through, I want to know why the trigger didn't fire, rather than stack a second trigger on top of the broken one.
The questions I get before a project.
What does a build cost?
It depends on scope, but most full lead-system builds land between $1,500 and $3,000, quoted as a fixed price split across milestones — not hourly. Smaller pieces (a workflow fix, a single bot, a dashboard) are less. You'll get a firm number before anything starts, and I'd rather flag scope creep up front than renegotiate mid-build.
How long does it take?
A focused build — bot, scoring, routing, tested — is usually 2 to 4 weeks. A larger system with a backlog migration or custom integrations runs longer. I'll give you a real timeline with buffer, not an optimistic one I'll miss.
Do you work hourly or fixed price?
Fixed price, milestone-based. You know the cost up front, and you're paying for the outcome, not the clock. Milestones are typically kickoff, build complete with a walkthrough, and acceptance once it's tested end to end.
I already have GoHighLevel set up. Can you work in it?
Yes — most of my work is going into an existing account and either fixing what's broken or building the layer that's missing. I screenshot the current state before I change anything, and I don't touch things outside the agreed scope.
What happens if something breaks after you're done?
Every build is tested with real leads down the real path before I call it done, and handed over documented so your team can run it. If something I built breaks, I fix it. I also build for traceability, so when something does go wrong, it's findable — not a black box.
What's not your lane?
Offer strategy, pricing, and sales copy. I'll tell you what the data says about them, but I don't write them — and you shouldn't hire someone who claims they do everything. I build the systems; the offer is yours.