I design CRM systems and automation workflows that keep leads and follow-ups moving.
I build complete systems — from business problem to working automation — inside GoHighLevel. Pipelines that reflect how the business actually runs, and workflows that carry the routine so the humans can focus on the strategy.
From business chaos to a system that runs itself.
Every CRM project starts messy — missed leads, manual follow-up, no single source of truth. This is the path every project takes from that chaos to a reliable, engineered system.
Business Problem
Start with what's actually breaking — missed leads, dropped follow-up, manual gaps.
Process
Map the current flow end-to-end so the system reflects real work, not assumptions.
CRM Structure
Design pipelines, stages, and contact segmentation around that real process.
Automation
Build the triggers, waits, and actions that carry the routine steps automatically.
Better Follow-Up
The outcome: consistent, on-time follow-up that no longer depends on memory.
Business Problem
Start with what's actually breaking — missed leads, dropped follow-up, manual gaps.
Process
Map the current flow end-to-end so the system reflects real work, not assumptions.
CRM Structure
Design pipelines, stages, and contact segmentation around that real process.
Automation
Build the triggers, waits, and actions that carry the routine steps automatically.
Better Follow-Up
The outcome: consistent, on-time follow-up that no longer depends on memory.
Systems I've built from the problem up.
Each project below is a self-directed systems project — a realistic business scenario I designed and built from scratch to practice CRM architecture and automation work. None of these are paid client engagements.
The systems capabilities I bring to a build.
Not a list of buzzwords — each capability below is something I've actually used to design or build inside a portfolio project.
CRM Setup & Administration
End-to-end configuration of GoHighLevel for a business's actual workflow.
Pipeline Design
Stages that mirror how deals or patients truly move — not generic templates.
Contact Segmentation
Tags, custom fields, and lists that make the right message reach the right person.
Workflow Automation
Triggers, waits, conditions, and actions wired into reliable sequences.
Lead Follow-Up
First-touch and long-term nurture cadences that keep leads warm.
Appointment Workflows
Booking, layered reminders, and confirmations to protect the schedule.
Missed Appointment Recovery
Same-day recovery paths so no-shows don't quietly become lost revenue.
Email & SMS Sequences
Multi-channel sequences with clear intent behind each message.
Forms & Landing Pages
Capture surfaces that feed cleanly into the CRM from day one.
Opportunity Management
Structured deal tracking with visibility into what's stuck and where.
GoHighLevel
Primary platform — pipelines, workflows, calendars, forms, sequences.
Process Mapping
Turning fuzzy business processes into a clear system before building.
Healthcare Workflow Understanding
Grounded in real prior-auth and insurance-verification experience.
I don't just build automations. I first understand the process.
A workflow that automates the wrong steps just breaks faster. Every system I design follows this arc so the automation reflects real work.
Understand the business problem
Get specific about what's actually breaking — not just symptoms.
Map the current process
Trace how work moves today, from first touch to final follow-up.
Identify manual gaps
Find the moments that depend on someone remembering something.
Design the CRM structure
Pipelines, stages, custom fields, and segmentation the process needs.
Build the automation logic
Triggers, waits, conditions, and actions wired together deliberately.
Test the workflow
Walk contacts through the system end-to-end and watch what fires.
Improve the process
Refine based on what the system reveals about the real workflow.
GoHighLevel Certification
Focused on the core GoHighLevel platform capabilities I use in every project — pipelines, workflows, calendars, forms, and messaging sequences.
The stack I actually work in.
A short, honest list — only what I use regularly.
I learn by building complete systems, not by watching them.
I'm building my CRM and automation practice the way I'd build a system: from the problem up. Every portfolio project on this site is a realistic simulation — a cleaning company, a clinic, a marketing agency — that I designed and built from scratch to practice real CRM architecture and automation work.
I'm not pretending to have years of agency-side client history. I'm demonstrating something more useful for the businesses I want to work with: how I think through a problem, how I structure a CRM around it, and how I decide what to automate versus what belongs in a human's hands.
If you're building or fixing a CRM setup, that's the kind of thinking I'd bring to it.
Have a process that feels more manual than it should?
If you're setting up a new CRM, cleaning up an old one, or trying to stop leads and follow-ups from slipping — I'd like to hear about it.
Building GoHighLevel systems and taking on CRM administrator / marketing automation VA work with small businesses and agencies. Remote — Philippines-based, working across US, CA, AU, and UK time zones.