← All case studies
Learning Operations

Learning operations on autopilot

How an education platform grew its next cohort 40% with zero new hires.

Industry
Cohort-based education
Team
15 person operations team
Scope
Learner health, mentor matching, cohort analytics
Engagement
6 weeks, audit to deployment
50%
of operations capacity recovered
40%
larger next cohort
0
new operational hires
01 / The problem

Running a cohort is an operations treadmill. Someone has to notice which learners are falling behind before they quietly drop out. Someone has to match learners with the right mentors, and rematch when schedules or needs change. Someone has to answer, week after week, the same question: how is this cohort actually doing? All of it was manual, all of it scaled linearly with learner count, and all of it meant that growing the next cohort meant growing the ops team first. Growth had a headcount tax.

02 / What the audit found

The operations team's week divided into three recurring loops: monitoring learner engagement signals scattered across the learning platform, community, attendance and assignment data, coordinating mentor availability and matches by hand, and assembling cohort status reports from raw exports. None of the three required judgment most of the time. All three required attention all of the time. That's the exact profile of work agents take over cleanly: high frequency, clear signals, occasional escalation.

03 / The system

Three agents running the treadmill

Learner health agent

Watches engagement signals continuously, scores every learner's trajectory and flags the ones drifting toward dropout while there's still time to intervene, with the reason attached.

Mentor matching agent

Collects mentor availability in real time and matches learners to mentors on expertise, schedule and need, rematching automatically when circumstances change.

Cohort intelligence agent

Maintains a live picture of cohort health: completion trajectories, engagement trends, at-risk clusters, so "how is the cohort doing" is a glance, not a reporting product.

04 / How it rolled out
Week 1

Audit. Mapped the three operational loops (monitoring, matching, reporting) and the signals feeding each.

Weeks 2 to 3

Learner health agent live in shadow mode, its flags compared daily against the team's manual catches until precision held.

Week 4

Mentor matching agent live for new enrollments, rematching logic tested on schedule changes.

Week 5

Cohort intelligence agent live, weekly reporting assembly retired.

Week 6

Full handover. Ops team working from agent queues and escalations only, manual monitoring loops shut down.

05 / The numbers
50%

of a 15 person operations team's capacity recovered. Not by working faster, by retiring the monitoring, matching and reporting loops entirely. That's the working hours of roughly 7 people, returned.

+40%

larger next cohort, enrolled against the same ops headcount. The growth ceiling stopped being the team's attention span.

0

new operational hires to get there. Interventions got earlier rather than sparser, because the health agent doesn't get busier when the cohort gets bigger.

Growth stopped carrying a headcount tax. The next cohort opened 40% larger, the ops team ran it from agent queues and escalations instead of spreadsheets and the question "how is the cohort doing" became a glance at a live picture instead of a weekly reporting product.

06 / What compounds

The health agent's flags get sharper every cohort as it sees more patterns of who struggles and who recovers. The platform now has something most education businesses never build: an operational memory that doesn't leave when a team member does. Effects we haven't counted: mentor retention, since mentors get matched to learners they can actually help, and the founder's time, which stopped going into weekly status assembly.