GoHighLevel · CRM · AI automation
Every lead gets a next step.
I'm Neal. I build the CRM and automation systems that sit between a lead arriving and a job being booked — and the websites those leads land on.
- CRM
- GoHighLevel pipelines, contacts and follow-up
- Automation
- n8n, API integrations, AI-assisted steps
- Web
- WordPress, React and Next.js builds
- GoHighLevel
- n8n
- Make
- WordPress
- Next.js
- PHP
- Figma
- Photoshop
Introduction
I work on the unglamorous part of marketing: what happens after someone fills in the form. Contact records that make sense, a pipeline nobody has to interpret, and follow-up that runs on its own.
I started in web development and moved into CRM and automation as the work demanded it — funnels, lead generation, media buying and the creative that feeds them. That combination is what most accounts actually need: someone who can fix the page and the pipeline behind it.
What I build
- CRM builds and pipeline structure
- Workflow and AI automation
- Funnels and lead capture
- WordPress and Next.js sites
How I work
- Scope before build
- Agree the process on paper first. Automating a broken process just makes it break faster.
- Build in the open
- Short checkpoints, working versions early, no month-long silence followed by a surprise.
- Hand over a system
- Written descriptions of every workflow, so your team can run it without me.
Based in
Cuyapo, Nueva Ecija
Philippines · working remotely with US and UK clients
Lead in, system out.
Most accounts do not need more tools. They need the ones they have to talk to each other, in an order that matches how the business actually sells.
Capture
- Website form
- Social DM
- Landing page
- Referral
Core
GoHighLevel
Contacts · Pipelines · Calendars
Follow-through
- Instant acknowledgement
- Reminders
- Booked call
- Owner notified
Four things I do properly.
Not a list of everything I have touched. These are the areas where the work has been repeated enough to have opinions about.
CRM & pipeline builds
Pipeline stages, contact fields and routing rules that match how the business actually sells. Every stage has a definition and an owner, so nobody has to guess what happens next.
- GoHighLevel
- Pipelines
- Custom fields
Workflow & AI automation
Follow-up sequences, notifications and AI-assisted steps that run without supervision — and stop the moment a person replies. Built to be read later by someone who did not build them.
- n8n
- Webhooks
- AI API
Funnels & lead capture
Landing pages and forms built around one action, with qualification placed before the calendar rather than after it. Reporting ties every booking back to its source.
- Forms
- Landing pages
- Calendars
Web builds
WordPress and Next.js sites that hold the offer, load quickly and can be edited by the owner. The page and the pipeline behind it are treated as one piece of work.
- WordPress
- React
- Next.js
Systems, not screenshots.
Two client engagements and four builds I put together to show the patterns I work in. The demo builds are labelled — none of this is borrowed work.
An inbox that sorts itself
AI-assisted triage that classifies incoming replies and drafts a first response for review.
- n8n
- AI API
- GoHighLevel
A funnel that hands off to a calendar
Landing page, qualification questions and calendar booking, wired so the right call lands with the right person.
- GoHighLevel
- Funnels
- Calendar
Also in the toolkit
WordPress builds
Custom themes and page templates the owner can edit without calling a developer.
Funnel design
Landing pages and lead capture paths built around one action, not seven.
Media buying
Campaign setup and monitoring, with the reporting tied back to booked work.
Graphic design
Social creative, marketing assets and brand pieces that match the site.
Short-form video
Cuts for social built from the same visual system as everything else.
Watch a lead go from form to booked call.
This is the pattern behind most of the builds: capture, clean, store, decide, follow up, book. Run it and read the log.
Workflow lab
Local simulation · sample data
- 1
Form submitted
Webhook · 120msName, email, phone and source captured from the page.
- 2
Validate and dedupe
Validate · 90msNormalise the fields, then check against existing contacts.
- 3
Create contact in GHL
CRM · 210msUpsert the record and tag it with the traffic source.
- 4
Qualification branch
Branch · 40msService and timeline decide the path, not a person reading it.
- 5
Send follow-up SMS + email
SMS + EmailFirst reply leaves before anyone opens the inbox.
- 6
Book the appointment
Calendar · 160msThe reply link opens the calendar and writes the slot back.
- 7
Notify the owner
Notify · 80msOne message to the team with the contact and the slot.
Else → nurture sequence · unqualified leads skip the calendar
Execution log
0 eventsPipeline
New
Contacted
Booked
It runs entirely in the browser with sample data. The real version connects to the client's own GoHighLevel account, calendar and messaging provider.
What it is like to work together.
“We stopped losing the leads that came in after 6pm. The follow-up now goes out before anyone has opened the inbox the next morning.”
Client name
Service business owner
“The handover was the useful part. I can open the account and understand what every workflow is doing and why it exists.”
Client name
Agency account manager
Tools I actually work in.
Chosen because they were right for the job, not because they were new. If an account already runs something else, I would rather learn it than migrate everything for the sake of a clean slate.
CRM & automation
- GoHighLevel
- n8n
- Make
- Zapier
- Webhooks
- AI APIs
Web
- WordPress
- HTML
- CSS
- JavaScript
- PHP
- React
- Next.js
Design
- Photoshop
- Illustrator
- Figma
- Canva
Marketing
- Media buying
- Lead generation
- Funnel builds
- Data collection
- Reporting
Straight answers, working systems.
I have worked in web development, CRM management and marketing automation — usually in small teams where the same person has to fix the page, the form and the follow-up. That is the range I am useful in.
Resourceful
Unfamiliar problem, no documentation, a system nobody has touched in a year. I would rather read the API than wait on an answer.
Adaptable
The brief changes. The account is messier than described. Adjusting scope without dropping the thread is most of the job.
Technical
Enough scripting and infrastructure knowledge to know why something breaks, not just that it did.
Independent
Comfortable working from a written brief across timezones, with checkpoints instead of supervision.
Neal Ramos
GoHighLevel & AI Automation Specialist
- Focus
- CRM, automation, web
- Based
- Nueva Ecija, Philippines
- Clients
- US & UK, remote
- Contact
- ramosneal03@gmail.com
The things clients ask first.
If yours is not here, email it. I answer in plain language, not a sales deck.
What does a GoHighLevel specialist actually do?
Set up and maintain the parts of the account that carry the work: pipelines, contact fields, forms, calendars and the workflows that move a lead from one stage to the next. It is equal parts configuration and deciding what the process should be in the first place.
Can you work inside our agency account instead of a new one?
Yes. Most of the work is done inside an existing sub-account, with the client's own naming and pipeline conventions. If it is white-label, the work stays under your brand and I do not contact your clients directly unless you ask me to.
What does a CRM and automation build include?
Pipeline stages, contact records and fields, forms and integrations, the workflows that run on top, and a short written handover so your team knows what each automation does and when to leave it alone.
How long does a build take?
A single pipeline with follow-up and booking is usually days, not weeks. A full account with multiple services, routing rules and reporting takes longer. It depends mostly on how quickly the process itself can be agreed.
How do you handle handoff and documentation?
Every workflow gets a plain-language description of what triggers it, what it does and what to check if it stops. The point is that the system survives after the engagement ends, and someone on your side can answer a question about it without calling me.
Can you support an existing team instead of rebuilding?
Yes. A lot of the work is fixing and extending what is already there: cleaning up duplicate contacts, tightening half-built workflows, or taking over maintenance. I would rather repair a working system than replace it for the sake of a rebuild.
What timezone do you work in, and does it overlap?
I am in the Philippines, working remotely with US and UK clients. The overlap with US mornings and UK afternoons is where calls and handovers happen; the rest of the day is build time.
How do we start?
Send a short description of where the process currently breaks — the enquiry that goes unanswered, the stage everyone skips, the report nobody trusts. From there we agree scope, and I start with the smallest version that fixes the actual problem.
Let's talk
Pick a time. Thirty minutes, no pitch.
Tell me where the system feels stuck — the enquiry nobody answers, the stage everyone skips, the report no one trusts. Pick a slot below and it lands on my calendar.
Calendar not loading?
Open Calendly in a new tab ↗