Case Studies

Systems I've built, and what they fixed.

Six builds, anonymised. Each one starts with what was broken, covers what I actually put in place, and ends with the result. Client names are withheld; the systems are described as built.

Selected Work

Six Builds, Start to Finish

Restoration, coaching, insurance, beauty, flight training, and lending. Different industries, mostly the same underlying problem: leads arriving faster than anyone can handle them by hand.

Restoration Services Company (US)

The problem

Emergency calls were coming in at all hours and going to voicemail. No system tracked which lead came from where, and follow-up depended on whoever remembered to call back.

What I built

A full CRM in GoHighLevel with nine automated workflows covering intake, qualification, estimate follow-up, and job completion. Added a Voice AI receptionist to answer after-hours calls and book directly into the calendar. Every booking generated its own reschedule link, so clients could move an appointment without calling the office. Also handled A2P brand registration for compliant SMS, including resolving a rejection caused by an EIN and address mismatch.

Outcome

Missed calls stopped going nowhere. After-hours enquiries are answered and booked straight into the calendar, and every lead is tracked to its source in one pipeline instead of depending on who remembered to call back.

Read the full build

Business Coaching Practice (US)

The problem

Leads came from several sources and got handled inconsistently. Discovery calls were booked manually, and no-shows were not being recovered.

What I built

A ten-workflow client acquisition system, from first touch through booked call and post-call follow-up. Included an AI assistant that handles first-response conversations with strict guardrails on what it can and cannot say, so it never oversteps into advice or pricing it is not authorised to give.

Outcome

Every enquiry gets a first response automatically, whichever source it came from, and discovery calls are booked and no-shows chased without anyone tracking them by hand.

Read the full build

Life Insurance Agency (US)

The problem

Policies were tracked in a spreadsheet. Renewals were being missed and there was no clear view of where any given prospect sat in the process.

What I built

A six-stage pipeline with seven workflows, including a renewal cycle that reactivates policyholders ahead of their date and a central exit workflow that cleanly removes a contact from all active sequences when they convert or opt out. That last piece matters more than it sounds: without it, clients receive contradictory messages from two sequences at once.

Outcome

Renewals are triggered ahead of the policy date instead of being watched in a spreadsheet, and every prospect sits at a visible stage in one pipeline. The exit workflow means nobody receives two conflicting sequences at once.

Read the full build

Beauty Studio (US)

The problem

Bookings lived in a separate scheduling tool that did not talk to the CRM, so reminders and follow-ups were manual.

What I built

Connected the existing booking platform to GoHighLevel through Zapier so every appointment created and updated a CRM record automatically. Built four workflows for confirmations, reminders, no-show recovery, and rebooking prompts. Took the business through A2P 10DLC approval for compliant text messaging, and resolved a subdomain DNS issue so the booking pages loaded on their own domain.

Outcome

Every appointment lands in the CRM on its own, so confirmations, reminders, no-show recovery, and rebooking prompts all send without manual work. The booking pages load on the studio's own domain, and the account is cleared for compliant SMS.

Read the full build

Flight Training School (US)

The problem

A partially built system with gaps nobody had mapped, and a need to reach prospective students on WhatsApp rather than SMS.

What I built

Ran a full QA pass on the existing build and produced a written checklist of every gap and fix. Wrote WhatsApp Business API message templates that meet Meta's approval requirements, then specced and built a nurture and re-engagement sequence for enquiries that go cold before enrolment.

Outcome

Every gap in the half-built system is documented in a written checklist the school can act on, and enquiries that go cold before enrolment are followed up on WhatsApp using Meta-approved templates.

Read the full build

Mortgage and Lending Business (US)

The problem

A meaningful share of applicants preferred Spanish, but every automated message went out in English only.

What I built

A bilingual CRM where language preference is captured at intake and routes the contact into the matching sequence for the rest of the lifecycle. English and Spanish contacts receive the same follow-up quality without the loan officer switching anything manually.

Outcome

Spanish-speaking applicants receive the same follow-up as English speakers, routed automatically from the language captured at intake, with nothing for the loan officer to switch manually.

Read the full build

Next Step

Want the same for your setup?

Every project starts with an audit of what you already have, sent to you in writing before any building starts.