Selected GoHighLevel work.

The Amador Gallery

• GoHighLevel
• Google Tag Manager
• GA4
• Meta Pixel and Conversions API
• Google Ads
• Microsoft Clarity

• Sector: Event venue, Kissimmee, Florida
• Scope: Venue enquiry automation and lead tracking repair

The problem

The venue runs Google and Meta ads to drive event enquiries. Its older tracking fired on thank you page views, so conversion numbers could not be trusted, and every enquiry needed to reach the team, and the CRM, with its ad source attached.

What I built

• A venue enquiry workflow that places each enquiry in the Venue Leads pipeline at New Inquiry, creates a follow up task, emails the team every event detail and texts the enquirer an acknowledgement
• Duplicate protection, so an existing opportunity is kept and updated rather than created twice
• UTM source, medium, campaign, content and term saved on every contact and carried through to the thank you page
• A rebuilt Google Tag Manager container: a custom listener turns each GoHighLevel form submission into one event with a unique event ID
• That single event fires the GA4 generate_lead, Meta Pixel Lead and Google Ads conversion tags, with the old page view tags paused
• The shared event ID deduplicates Meta browser and Conversions API events and doubles as the Google Ads transaction ID
• Microsoft Clarity for session recordings and heatmaps
• A documented end to end QA run, including a page refresh test confirming no duplicate lead in GA4 or GoHighLevel

The outcome

Every venue enquiry lands in the pipeline with its ad source, the team is notified straight away, the enquirer gets a text back, and GA4, Meta and Google Ads each count the lead once.

The system in action

Thank you page receiving the enquiry with UTM parameters intact Workflow log: task, team notification and SMS sent; duplicate opportunity skipped Opportunity in the Venue Leads pipeline with source and ad tags Internal notification email with every event detail mapped UTM fields captured on the contact record One form event fires GA4, Meta Pixel and Google Ads tags Meta browser and Conversions API events deduplicated Tag Manager container: new tags live, old page view tags paused

Personal details and account IDs are blacked out.

Bikram Yoga Works

• GoHighLevel
• Mindbody Public API v6
• Make
• A2P 10DLC

• Sector: Yoga and wellness, four studios across DC and Baltimore
• Scope: Mindbody to GoHighLevel integration and multi location client journey

The problem

The group had the right tools but no connection between them. Mindbody held the client data, GoHighLevel held the messaging, and nothing passed between the two beyond a name and an email.

The result was a welcome sequence that could not tell who had already acted. A new client who booked their free body composition scan on day one kept receiving reminders to book it for the next twenty three days, across seven further messages. Over a hundred automations sat published in the account, built the year before, waiting on signals that never arrived.

What I built

• A live two way connection between Mindbody and GoHighLevel, running on the client's own developer API access rather than a third party reseller
• Purchases, studio location, membership tier and expiry written onto the contact record automatically every fifteen minutes
• Each contact tagged with their home studio and whether they use the fitness or the wellness side of the business, so every yoga client who has never tried recovery services can be found
• A rebuilt welcome journey that splits four ways by studio, each with its own offer, and checks before every single message whether the client has already taken it

The outcome

The chasing problem is solved: nobody is chased for something they have already done. An automation built over a year earlier, which had never enrolled a single person because nothing applied the tag it waited on, is now firing. Over a hundred dormant workflows were archived, and 45 live contacts were migrated onto the new journey without duplicate messaging.

The system in action

Make scenario: Mindbody API to GoHighLevel webhook, every 15 minutes GoHighLevel workflow: create contact, update fields, branch by location Membership name and expiry synced onto the contact, with location tags Booking tag applied automatically for targeted follow up Client ID, studio location and service type mapped from Mindbody onto the contact

Personal details and webhook addresses are blacked out.

Wright Stone Lane

• GoHighLevel
• Snapshots
• Custom values
• UK PECR

• Sector: Lead generation agency, United Kingdom
• Scope: Three phase CRM and automation build

The problem

A UK lead generation agency needed a GoHighLevel system it could deploy repeatedly for client accounts, built to UK marketing law rather than the US defaults most templates assume.

What I built

• Three milestone build with scope and acceptance criteria agreed before each phase
• Workflow suite designed around UK PECR consent requirements
• Custom values used throughout so the entire build exports cleanly as a reusable snapshot
• Review generation that requests feedback from all customers rather than filtering for positive responses
• Reactivation campaign protected by four sequential guards so no contact can be contacted outside consent rules
• Handover documentation plus a versioned deployment guide

The outcome

A portable, compliant system the agency can deploy to new client accounts without rebuilding, and without legal exposure on consent.

The system in action

The numbered blueprint workflow suite: qualification, booking chase, quotes, no-shows, nurture and weekly report

The Royal Method Co.

• GoHighLevel
• Pipelines
• Workflows
• Document collection

• Sector: Accounting and advisory
• Scope: Full CRM implementation

The problem

Client onboarding ran through email threads and spreadsheets. Documents were chased manually and nothing was tracked once a prospect said yes.

What I built

• Full CRM implementation with nine sequenced workflows covering enquiry through to active client
• Pipeline stages mapped to the firm's real engagement process
• Automated onboarding sequence triggered on stage change
• A secure document collection process designed around the firm's confidentiality requirements

The outcome

Onboarding moved from manual chasing to a tracked, automated sequence with every client at a visible stage.

New Chapter Financial Solutions

• GoHighLevel
• Make
• Adobe Acrobat Sign

• Sector: Financial services
• Scope: Five phase build with e signature automation

The problem

Lead intake, document signing and client records lived in three disconnected places, creating delays and lost paperwork.

What I built

• Five phase GoHighLevel build, each phase scoped and priced separately
• Make scenarios connecting GoHighLevel to Adobe Acrobat Sign
• Automated document generation, send, reminder and completion handling
• Signed documents returned to the contact record automatically

The outcome

A single flow from enquiry to signed agreement with no manual document handling in between.

SWL Institute

• GoHighLevel
• Twilio
• UTM tracking
• Forms

• Sector: Education and training
• Scope: CRM and student enrollment automation

The problem

SWL Institute needed one place to manage prospective students from first enquiry through to registration on its EKG and Phlebotomy programmes, including follow ups, deposit payments and enrollment paperwork.

What I built

• A CRM pipeline with stages for New Lead, Contacted, Interested, Not Interested, EKG Registered and Phlebotomy Registered
• Enrollment workflows structured around student registration and deposit payment logic
• Intake forms with UTM tracking, so every lead carries its source
• Domain and DNS configuration fixes, and Twilio integration setup for messaging
• A planned enrollment agreement process with electronic initials and signatures
• Integration planning for Wix course delivery, Mailchimp and Xperiencify

The outcome

A structured enrollment process with clear tracking of every student, organised follow ups, and a foundation for cutting manual admin work.

The system in action

Inquiry form with program interest and separate A2P compliant SMS consent New inquiry workflow: tag, opportunity, team alert, then branch on assessment Journey tags tracking each student from new lead to payment plan

Personal details are blacked out.

Flooring and Coatings Contractor

• GoHighLevel
• Jobber
• Make
• Webhooks
• Conversation AI

• Sector: Specialty floor coatings and lighting, two business lines
• Scope: Jobber to GoHighLevel integration, lead routing and AI chat with human takeover

The problem

Quotes and jobs lived in Jobber while leads and messaging lived in GoHighLevel, across two separate business lines. Nobody could see in the CRM when a quote was sent or approved, and new leads needed a fast first reply without the team losing control of the conversation.

What I built

• Make scenarios receiving Jobber quote events (created, sent, updated, approved) by webhook and routing them by business line
• Jobber OAuth handled in Make, with tokens stored and refreshed automatically for each account
• Quote details fetched from the Jobber GraphQL API and written back to GoHighLevel
• A lead capture and routing workflow that tags each lead, updates its fields and finds or creates the right opportunity
• A new lead notification and response window so the team is alerted the moment a lead arrives
• An AI chat agent with a human takeover workflow: when a team member steps in, the AI pauses for that contact
• Qualification fields for the coatings side, including system type such as flake, metallic, quartz and polished concrete

The outcome

Jobber quote activity and GoHighLevel lead handling are connected, so both business lines can see where every lead and quote stands, and the AI only answers when no person has taken the conversation.

The system in action

Make scenario routing Jobber quote events by business line Lead capture and routing: tag, update fields, find or create the opportunity Human takeover: the AI pauses when a team member replies Coatings qualification field with each system type

Photography and Video Studio

• GoHighLevel
• Calendars
• Round robin
• SMS alerts

• Sector: Photography, video and content production
• Scope: Shoot booking, crew assignment and crew reminders

The problem

Shoots were booked through the studio's calendars, but telling the right crew members about each shoot, and reminding them before the day, was done by hand.

What I built

• A team calendar group with a calendar for each crew member
• Round robin assignment, with the shoot owner written onto the contact automatically
• A crew notification workflow that branches by assigned crew member and sends each one an SMS and in-app alert with the shoot details
• An additional crew field, so every extra crew member on a shoot is notified too
• Reminders timed from the shoot date, sent days before the shoot

The outcome

Every crew member on a shoot hears about it the moment it is booked and is reminded before the day, without anyone in the office sending messages by hand.

The system in action

Booking triggers a branch for each assigned crew member, each with its own SMS alert

Crew and studio names are blacked out.

Real Estate Team

• GoHighLevel
• Funnels
• Email
• SMS
• Calendars

• Sector: Real estate
• Scope: Lead management and follow up automation

The problem

Agents were receiving property enquiries from several places with no single view of who had been contacted, who was qualified and who needed a follow up.

What I built

• A CRM pipeline tracking prospects from first enquiry through contact, qualification, appointment and opportunity
• Landing pages and enquiry forms feeding leads straight into the pipeline
• Automated email and SMS follow up sequences for new leads
• Contact tags and segmentation so each prospect gets relevant messages
• Appointment scheduling with calendar integration built into the lead process
• Follow up workflows driven by lead status and prospect engagement

The outcome

One place to manage every property enquiry, consistent follow up without manual chasing, and clear visibility of the sales pipeline.

Marketing Agency

• GoHighLevel
• Snapshots
• SaaS mode
• Sub accounts

• Sector: Marketing agencies and service businesses
• Scope: SaaS setup and snapshot architecture

The problem

The agency was setting up each new client account by hand, so every onboarding repeated the same work and no two accounts were built quite the same way.

What I built

• Reusable CRM configurations for repeatable client onboarding
• Snapshot architecture for moving supported configurations between accounts
• Pipeline stages, tags, forms and workflows organised into one reusable system
• SaaS mode and white label configuration for offering CRM as a service
• Sub account structure that keeps each client's data and operations separate
• Planning for connections to Zapier and Make for work outside GoHighLevel

The outcome

A repeatable foundation for client onboarding, with less duplicated setup and the same proven process in every account.

Dental Practice

• GoHighLevel
• Missed call text back
• Calendars
• SMS reminders

• Sector: Dental and healthcare services
• Scope: Appointment and lead response automation

The problem

Patient enquiries were being missed when the front desk was busy, and appointment confirmations, reminders and no show follow ups all depended on someone remembering to do them.

What I built

• Lead capture and contact organisation inside the CRM
• Missed call text back so every incoming enquiry is acknowledged
• Appointment booking with calendar integration
• Appointment confirmation and reminder sequences
• Follow up logic for missed appointments and rescheduling
• Planning for an AI voice agent to handle patient enquiries and bookings

The outcome

A consistent way to respond to every enquiry and manage appointment communication, with far less risk of a new patient slipping through.

Local Service Business

• GoHighLevel
• Funnels
• Email
• SMS
• Review requests

• Sector: Home services and local businesses
• Scope: Lead generation and customer follow up

The problem

Lead generation, customer messages and follow ups were handled separately, so enquiries went cold and happy customers were rarely asked for a review.

What I built

• Landing pages and lead capture forms for service enquiries
• A CRM pipeline tracking new enquiries, contacted prospects, qualified leads and booked appointments
• Automated email and SMS responses for new leads
• Follow up workflows for prospects who have not replied
• Review request automation after each completed job
• Workflow triggers and conditions so every message matches the customer's stage

The outcome

Lead generation, communication and follow up connected in one workflow, giving customers a more consistent experience from enquiry to review.