[ Case study ]
The webinar funnel registered well but converted poorly: the replay page buried the offer below an hour of video, registration reminders relied on one email, and nobody could say where drop-off actually happened because tracking ended at registration.
CLIENT a professional-coaching program — FOCUS Resolve the version split first
Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.
Behind a professional-coaching program's enrollment results sits a webinar funnel built years ago and maintained by nobody. The coach is the program's product and its only presenter; a small team around him manages delivery, and the funnel itself survived a half-finished migration between ClickFunnels versions that left the account split in two. Live cohorts run on a fixed calendar, so the funnel is not just a page — it is the program's front door for months at a time, and it had settled into being tolerated rather than understood.
The webinar funnel registered well but converted poorly: the replay page buried the offer below an hour of video, registration reminders relied on one email, and nobody could say where drop-off actually happened because tracking ended at registration.
Consolidate the account on 2.0 before anything else, because tracking and automation behaved differently across the two halves and every later improvement would have been built on split data. Then rebuild the replay page as a decision page — offer, proof, and deadline above the video, with an always-visible call to action — so the recording supports the decision instead of delaying it. Reminder sequences gain an email-plus-text cadence with engagement tracked per registrant, and registration through order becomes one measured sequence, ending the era of optimization by opinion.
Just as important is what we ruled out, and why:
The Classic remnants were identified and the funnel consolidated on 2.0, because tracking and automation behaved differently across the halves.
The offer, proof, and deadline moved above the replay video with an always-visible call to action — the video supports the decision instead of delaying it.
Registration, reminder opens, replay start, offer click, and order became a tracked sequence, so optimization arguments stop being opinions.
Delivered by the growth pod — strategist + automation specialist over 5 weeks, with working increments reviewed with the client every week.
Obstacle
Three years of registrant contacts lived in the Classic half, and their tags and purchase history did not map cleanly onto the 2.0 account's fields.
Handled: We wrote a field map, imported in batches, and reconciled every batch against order records so no past customer lost history or access during the cutover.
Obstacle
The next live cohort was only three weeks out, which compressed the redesign's testing into real traffic with actual enrollment stakes riding on every change.
Handled: We split traffic between the old and new replay pages for the first week and promoted the new page only after reminder opens confirmed the sequence behaved, trading a little speed for safety.
Obstacle
The redesigned replay page needed proof imagery, and the only source was frames buried inside the hour-long webinar recording the coach was never going to re-shoot.
Handled: We pulled stills from the existing footage, chose the moments that carried the proof, and cleared them with the coach in one email — the page shipped with zero new recording demands.
The headline: replay-to-enrollment conversion across the next two cohorts versus the two prior — 2.9% → 7.8%, read from Funnel analytics plus order records. A second check: reminder-driven registration shows at +41%.
The Monday enrollment meeting changed character: the team opens the funnel report and reads the step where numbers moved, instead of hosting a theory contest. Nobody asks the coach to re-record when conversion wobbles, because the page now carries the offer and the data says where attention goes. Planning a new cohort means editing a known funnel with known numbers, and the low dread that something fixed on one half had stayed broken on the other left with the Classic account.
The result was read from Funnel analytics plus order records against the pre-engagement baseline over the stated window, with a guardrail check on reminder-driven registration shows. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.
What we would do differently
We would have fixed tracking before redesigning — one week of real drop-off data would have pointed at the replay page without the debate.
[ Related service ]
[ Related builds ]
4.1% 9.3%Visit-to-demo-request conversion across all ad groups, 8 weeks after launch versus 8 weeks before
38 96Mobile Lighthouse performance score (lab diagnostic), with p75 LCP moving from 4.2s to 1.3s in field data
[ Next step ]
Next case study