One Platform, Hundreds of Hours Back: Unifying a Boutique Online Academy

The brief

A boutique online academy — a lean team of around fifty, with an alumni network in the thousands — had built its name on hands-on, personal instruction. Students chose it precisely because it wasn’t a faceless mass-market course mill; the relationship with instructors was the product. But its technology had grown the way most small companies’ does: one off-the-shelf tool at a time, each solving an immediate need and none of them talking to the others.

The result was a patchwork the team was constantly fighting:

Lessons lived in three places at once. Live classes streamed on one platform, slides and code went to a separate cloud drive, and grades were tracked in spreadsheets. A single course was scattered across tools that had no idea the others existed.
Student data was scattered. Engagement, attendance, and feedback were spread across vendors, so building a clear picture of how a student was actually doing took real, manual effort — exactly the kind of effort a lean team can’t spare.
Reporting was a multi-day job. Cohort reviews and year-end reports meant exporting from several systems and manually merging numbers that didn’t agree with each other. By the time a report was finished, the moment to act on it had often passed.
Privacy was a growing worry. The more outside vendors held student data, the harder it was to govern who could see what — a real concern for an institution responsible for thousands of learners’ records.

The irony wasn’t lost on the team: an academy whose whole value was close attention to each student was spending its time wrestling software instead of teaching.

Untangling the stack

Before proposing a single line of code, we mapped the full sprawl — every tool in use, what data lived where, and which manual steps existed only to paper over the gaps between systems. A surprising amount of the team’s “admin work” turned out to be glue: re-keying the same information from one tool into another. That map made the goal concrete. The new platform didn’t just need to add features; it needed to make entire categories of busywork disappear by removing the seams the busywork existed to bridge.

What we built

We replaced the stack with one custom platform — video streaming, course materials, feedback, and analytics under a single architecture — built with a Vue front end, WebRTC for live sessions, and a Django backend over PostgreSQL. The build ran about five months.

Teaching in one place. Instructors move from a live, WebRTC-powered lecture to handing out materials and collecting work without ever leaving the interface. The tab-juggling that used to fragment every class is simply gone; the lesson, the materials, and the submissions all live together.
An AI tutor on the course material. Rather than waiting on an after-hours email reply, students get instant, context-aware help: the tutor draws on the actual course content to unblock a coding or concept problem in the moment. It doesn’t replace the instructors — it covers the gaps between their hours, so a student stuck at 11pm isn’t stuck until morning.
Analytics that surface trouble early. A live engagement dashboard makes a struggling student visible right away — when someone stalls on a module or goes quiet, it shows up immediately instead of in a post-mortem. The academy’s signature personal attention now has data behind it, so intervention can happen while it still matters.
Data governance as a feature. With everything housed in-house, the academy controls exactly who can see student data, in one secure environment, rather than trusting a rotating cast of external vendors.

Bringing instructors on board

A platform is only as good as the instructors’ willingness to live in it, so we built and rolled it out in close collaboration with the people who’d teach on it — shaping the live-class and grading flows around how they already worked, then onboarding the team in stages rather than all at once. Because the platform removed steps instead of adding them, instructors took to it quickly; the version that replaced the most tedious parts of their week didn’t need to be sold.

How it landed

Work that used to mean hours of jumping between tabs now takes minutes, and the year-end reports that once swallowed days are generated on demand. The administrative drag that had been quietly taxing every instructor’s week eased, handing the team back time to spend on the thing students actually pay for.

More than the time saved, the academy moved from hindsight to foresight. It can see engagement as it happens and step in while a student is still recoverable, rather than discovering the problem in a report weeks later. The personal, hands-on instruction that made the academy’s name is now backed by a system that helps it scale, instead of one that fought it at every turn.

For a small team, that’s the difference between scaling and stalling — the technology finally works for them, not against them.