Case study
Stephanie Center Wellness — a functional-medicine funnel, rebuilt in GoHighLevel
A women’s hair-health practice with a working marketing ecosystem needed its website rebuilt and improved inside GoHighLevel — without losing the brand it had already built, and without tearing out the email and consultation tools that already worked. This is an account of the system I implemented, and a careful line between what was mine to build and what was the client’s to begin with.
- Industry
- Functional medicine · women's hair health
- Platform
- GoHighLevel
- Preserved stack
- AWeber · Practice Better
- My role
- Rebuild, migration & integration
What was mine, and what was the client’s
My work
Rebuilding and implementing the pages inside GoHighLevel — the responsive build, the landing pages, connecting lead capture, integrating the marketing forms, and wiring the site into the existing stack. The engineering and implementation, not the message.
The client’s
The brand, the voice, and every word of copy. The medical program and its framework, the quiz’s diagnostic content, the testimonials, and Stephanie’s own story and credentials. I presented her work well; I didn’t write it.
01
The business problem
Stephanie Center Wellness helps women get to the root cause of hair loss — a functional-medicine practice, not a quick-fix brand. The customer is a woman who has been told her labs are “normal” and is still losing hair, and who needs to be educatedbefore she’s ready to invest in a program.
The practice already had the hard parts: a distinct brand, an email list on AWeber, and consultations running through Practice Better. What it needed wasn’t a reinvention — it was a website rebuilt and improved inside GoHighLevel, so the whole funnel could live on one platform and feed one CRM, while the tools that already worked stayed exactly where they were.
So this was a migration and implementation job, not a redesign. The brief was to preserve the visual identity, rebuild the pages properly (responsive, mobile-first), and connect the lead-generation the practice runs on — without disrupting the marketing ecosystem already in place.
02
The customer journey
The funnel is built to teach before it asks for anything. A visitor meets the practice through education, trades an email for something genuinely useful, gets nurtured over time, and only then is invited to a consultation and the program. Here is that path — with an honest mark on which parts I can show you and which run behind the scenes.
Visitor arrives
Education-first — the homepage teaches the root-cause idea before it sells anything
Guide · quiz · cheat sheet
A free lead magnet or the Hair Loss Type Quiz — a reason to raise a hand
Lead capture
An email form on the page — the low-friction first step
Email nurture — AWeberbehind the scenes
The practice's existing email tool, kept in place, carries the follow-up
Consultation booked
A “Book a Call” / Root Cause Assessment invitation — the human step
Practice Betterbehind the scenes
The client's existing consultation, portal, and appointment tool
Hair Growth Accelerator program
Enrollment in the client's root-cause program
03
System architecture
The shape of the decision was: put the web layer on one platform, and leave the tools that already workedalone. GoHighLevel became the site, the pages, the forms, and the place leads land. AWeber and Practice Better — both already part of the practice — stayed, and the build connected out to them rather than replacing them.
GoHighLevel — the web layer & CRM
Website, landing pages, the quiz and guide funnels, the lead-capture forms, and the contact record they land in. The one platform the rebuild consolidated onto. Why: one place for the site and the leads it generates.
AWeberpreserved
Email marketing & nurture. Why kept: the list and the sequences already lived here — replacing it would have thrown away working infrastructure.
Practice Betterintegrated
Consultation, client portal, appointments. Why kept: the clinical side of the practice already ran here — the site connects to it, not around it.
CRM back officenot shown
Contacts, pipelines, workflows, calendars. Prepared and supported as part of the build — but the internals aren’t evidenced on this page, so they aren’t detailed (§06).
04
Technical decisions
Each of these is something I did in the build, and the reason it was the right call for this practice:
Rebuild inside GoHighLevel
Consolidate the website, landing pages, forms, and CRM onto the one platform the practice was moving to — so the funnel and the leads it captures live in the same place.
Preserve the visual identity
Keep the client's editorial brand — its serif typography (Playfair Display, Crimson Pro, Montserrat, Merriweather Italic) and warm, premium tone — intact through the rebuild. A migration, not a restyle.
Responsive & mobile-first implementation
Build the pages to hold up on the phones most of this audience actually reads on — the mobile experience treated as the primary one, not an afterthought.
Keep AWeber, don't replace it
Respect the working email stack. The nurture sequences and subscriber list stayed on AWeber; the build fed it rather than forcing a risky migration.
Integrate Practice Better
Point consultations at the tool the practice already used for its client portal and appointments, instead of rebuilding clinical scheduling from scratch.
Move toward native GoHighLevel forms
Shift lead capture toward native GHL forms so a new lead lands directly in the CRM — the first step in tightening the path from form to follow-up.
05
The business system
The point of the build isn’t the pages — it’s the path they make. Education earns trust, trust makes a small ask (an email) easy, and the CRM turns that email into someone the practice can actually follow up with. Two of the pages carry most of that weight.
Both pages do the same job in different registers: give something genuinely useful, ask only for an email, and drop the new lead into the CRM where the follow-up can begin. The quiz trades a result for a contact; the cheat sheet trades a reference for one. From there the path is nurture (AWeber) → consultation (Practice Better) → program.
What I can show ends at the page. The parts that make it a systemrather than a set of pages — how contacts are organised, the pipeline a lead moves along, the workflows that fire — are real work but live in the client’s GoHighLevel account. Rather than describe them from memory, here’s exactly what would evidence them:
06
Trade-offs
The honest decisions — what stayed manual, what was left in place on purpose, and what a next phase would tackle:
The consultation stays human
The funnel automates the teaching and the capture, but the step into the program runs through a real consultation — a booked call and a Root Cause Assessment. In a clinical practice that human step isn't a bottleneck to remove; it's the point.
Two tools kept, not consolidated
Email stayed on AWeber and consultations on Practice Better instead of being rebuilt natively in GoHighLevel. The cost is more surfaces to keep in sync; the gain is not breaking infrastructure the practice already depends on.
Toward native forms, not all at once
Lead capture was moved toward native GoHighLevel forms so leads land straight in the CRM — a direction the build started, not a wholesale switch flipped in one go.
Back office not documented here
The pipeline, workflows, and integration wiring are real but unshown on this page. That's a deliberate limit of what I'll claim without evidence — captured as a checklist (§05) rather than described from memory.
07
What it reinforced
This project didn’t teach me a new philosophy — it tested the one I already hold against a different industry, and it held up.
Fitting the business beat showing off the tool. The most valuable decision here was restraint: not rebuilding AWeber and Practice Better inside GoHighLevel just because it was possible. The practice runs on those tools; a good system bends around how the business already works, not the other way around.
The human step belongs to the human. Just like a boutique resort keeps the availability call with a person, a functional-medicine practice keeps the consultation with a practitioner. Automate the teaching and the capture; leave the judgement — clinical, here — to a person, on purpose.
Same spine, different industry.A hospitality booking flow and a healthcare education funnel look nothing alike on the surface, and underneath they’re the same system: teach, capture once, keep it somewhere findable, and route to the human at exactly the right moment. That the pattern carried from a resort to a wellness practice is the whole point.
The thinking behind all of this lives on the business systems page — this project is one place it met the real world.
Systems that fit the business they’re built for
Product engineering, a resort booking pipeline, a wellness funnel — the same systems thinking, adapted to each. Have a look at how it’s put together, or let’s talk.