I build the systems that run the business while you sleep.
Automations that run without babysitting. A CRM that's actually organized instead of a junk drawer. Bots that qualify leads, dashboards that tell the truth, and the API glue that ties tools together into one system. I don't hand you a piece; I build the whole thing and make it hold up in production.
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 full stack for a lead-gen operation across three markets: AI bots that qualified leads on SMS and voice, wrote answers to CRM fields, scored and routed them, and booked the good ones onto a calendar, all running automatically.
Master booking, disposition and recovery workflows: reschedule-safe, reminder sequences, no-show handling, and country-based routing that copies contacts into a separate sub-account where they belong.
A serverless dashboard (Cloudflare Worker plus APIs) reconciling CRM contacts, opportunities and calendar data against ad spend: live attribution, cost per outcome, paid vs organic. Built from scratch because no off-the-shelf tool did it.
See an interactive demo →API integrations across GoHighLevel, Twilio and Meta; server-side conversion tracking; automation pipelines with retries and failure alerts. The plumbing that makes separate tools behave like one system.
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.