From Banking Software to GoHighLevel + n8n

Day One

EPGR Digital Marketing Services

Web developer at a digital agency. First time I saw an agency from the inside. The seed of wanting to build my own got planted there, even if I didn't know it yet.

2019

Sandstone Technology

Software developer on Australian banking and lending systems. Serious code, serious uptime, no marketing in sight. Then COVID hit, and like a lot of devs stuck at home, I started exploring side hustles.

Post-COVID

IBX Digital

First time I touched GoHighLevel. Setting up sub-accounts, managing them, building workflows and tags for client campaigns. Also the first time I touched n8n. Started seeing how the two tools could carry an entire agency between them.

Then

Noblemen

Webflow developer, kept building n8n workflows for client projects. The pattern was getting clearer: every agency had the same integration problems, and almost no one wanted to write the code that fixed them.

Where I Grew Up

Baton Leads

Built a call-qualifying tool that processes 16,000+ calls a month. Built workflows connecting APIs, webhooks, Slack, Notion. Every time the no-code surface ran out, I dropped into code. AI started showing up in my workflows here too.

Today

My Own Practice

Building my own practice. New GoHighLevel and n8n builds, plus cleanups of setups several people built on top of each other.

Hourly or Fixed, Your Call

I'm fine either way. A quick fix, I bill the hours. A full build gets a fixed price in writing before I start. If the scope moves, I re-quote it with you before I touch the keyboard.

Production Systems Only

I ship workflows that hold up under volume, with logging and error paths in place. Proof-of-concept work and screen-recorded demos aren't what I do. The build runs in your account from the start.

Code Where No-Code Can't

When the no-code surface hits its limit, I drop in JavaScript, TypeScript, or Apps Script. That's the difference between a workflow that almost works and one that ships.

Honest About What Can't Be Automated

Some work belongs to a human: judgment calls, sensitive client conversations, the messy first call with a new lead. I'll tell you when a workflow is the wrong tool, and what to build around it instead.

GoHighLevel

The system of record. I live inside sub-accounts: workflow builder, snapshots, custom values, trigger links, contact notes, Conversation AI. If your operation runs on GoHighLevel, this is where everything else connects back to.

n8n + Make + Zapier

n8n is my main canvas for cross-tool workflows, AI orchestration, and anything the GoHighLevel workflow builder can't do alone. Make is the quick visual build when speed wins. Zapier handles the wiring for apps n8n doesn't reach yet. Most builds use one. Some use all three.

JavaScript, TypeScript, Apps Script

Where the differentiator lives. n8n function nodes for custom logic, TypeScript for anything that has to scale or stay maintainable, Apps Script for custom behavior inside Sheets, Calendar, and Gmail. When a no-code platform stops, code starts.

Claude, OpenAI, and the Data Layer

Claude is the model I reach for first on hard reasoning. OpenAI fills the jobs Claude isn't shaped for. Airtable when a build needs a lightweight database. Slack catches the alerts that matter. Notion keeps the wikis that teams actually read.