[ Case study ]
Open enrollment filled cohorts with mismatches — learners whose employers wouldn't sponsor, or whose goals the program didn't serve. Completion and referral rates suffered, and the sales lead spent hours on calls with the wrong buyers.
CLIENT a corporate-training provider — FOCUS Make the application the filter
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.
Employers sponsor every seat in this corporate-training provider's cohort programs — the learner attends, the organization pays — and both the provider's pricing and its accreditation assume that payer exists. Enrollment had been open: a checkout page, a calendar of cohort dates, and whatever self-selection produced. The sales lead personally handled every enrollment conversation, the operations manager prepared each cohort around whoever arrived, and the accreditation paperwork was reconciled after the fact from whatever the checkout had captured. Referrals, the provider's main growth channel, flowed from employers whose learners had thrived.
Open enrollment filled cohorts with mismatches — learners whose employers wouldn't sponsor, or whose goals the program didn't serve. Completion and referral rates suffered, and the sales lead spent hours on calls with the wrong buyers.
Make the application the filter: a short form that captures the payer's role and the funding source alongside the learner's goals, scored against the program's written fit criteria. Approved applications trigger the enrollment-and-invoice sequence for the sponsoring employer automatically, replacing the email chase, while flagged cases go to the sales lead for a human read. Seat counts and cohort dates render from live data, so every urgency claim on the page is checkable — and every record the funnel produces is one the accreditation file can use as-is.
Just as important is what we ruled out, and why:
Enrollment became a short application with the payer's role and funding source captured, scored against the program's real fit criteria.
Approved applications trigger the enrollment-and-invoice sequence for the sponsoring employer, replacing the email chase.
Seat counts and cohort dates render from the live data, so every urgency claim on the page is checkable.
Delivered by the growth pod — strategist + automation specialist over 5 weeks, with working increments reviewed with the client every week.
Obstacle
The first cohort's application answers were messier than the scoring rubric expected — payer roles did not map cleanly to the criteria as written.
Handled: We revised the payer questions with the sales lead between cohort one and cohort two, and added a flag-for-human-review path instead of forcing scores onto ambiguous cases.
Obstacle
One sponsoring employer's procurement refused the automated invoice and demanded its own purchase-order process midway through an enrollment.
Handled: The workflow gained a branch for PO-based employers, and the application now asks funding preference up front — the exception became a field, not a fire.
Obstacle
The seat-count urgency messaging had to render from live data, but the enrollment system's numbers included provisional holds that were not real seats.
Handled: We defined what counts as a taken seat, excluded holds from public counts, and made the page's scarcity something the operations manager can vouch for in a meeting.
The headline: cohort completion rate range across the two cohorts after the change (prior cohorts: 94% with mismatched fills) — 94% → 88% to 91%, read from LMS completion records. A second check: sales-lead hours per enrolled learner at −41%.
The sales lead's week changed shape: application review is twenty minutes of reading against a rubric, and her calls are with people the program was built for. Instructors open cohorts with funded professionals who chose the program deliberately, and the room feels different in ways they struggle to name but mention anyway. Employer conversations now start at application rather than at invoice, which is where referrals come from. And each cohort's accreditation file assembles itself from records that were designed for it, not reconstructed afterward from a checkout export.
The result was read from LMS completion records against the pre-engagement baseline over the stated window, with a guardrail check on sales-lead hours per enrolled learner. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.
What we would do differently
We would have piloted the application on one cohort before both — the form's payer questions were revised after the first cohort's answers.
[ 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