A learning platform built around one school, from the inside out
When the tools don't fit, the school bends. We're building the one that bends instead.
A licensed online school runs on a stack of rented tools: an LMS, a CRM, an automation service, a funnel builder, a scheduling app, and the glue between them. Each works; together they leak. Cohorts, live sessions, certification requirements, state records, a professional directory, and a community all live in different places, and the staff are the integration.
We're building the school a single platform of its own: programs with evergreen eLearning and a live cohort piece, a learner dashboard per cohort, live seminars with Zoom joined in-page and recordings that land where learners expect them, certification requirements kept as checklists that save as you go, a directory that lists learners the moment they enroll and upgrades them when they graduate, the state's records and audit packs generated from the same data, SCORM and Rise packages housed edge to edge, and an assistant that answers from the course material and knows what it is not allowed to say.
In private testing with the school's faculty and staff. Students won't see it until everything is provisioned. The current direction, after a hard look with the school's director: narrow it back toward the LMS, decide what ships at launch and what keeps growing in the background.
Read the whole story
The school had done what most small schools do: rented a tool for each job and stitched them together. An LMS for the courses, a CRM for the people, an automation service to move data between them, a funnel builder for enrollment pages, a scheduling app for live sessions, and a shared drive and a spreadsheet for everything the tools didn't cover. Every one of those pieces worked. The problem was the seams. A learner who enrolled in a cohort existed in four systems, and whether those four agreed depended on an automation nobody wanted to touch. The state's reporting requirements lived in a spreadsheet maintained by hand. The professional directory was a page someone updated when they remembered.
We spent the first stretch not building anything. We mapped what the school actually does in a year: programs with an evergreen self-paced track and a live cohort track, seminars that need a Zoom room and a recording, certification requirements that have to be evidenced and signed off, student records the state can audit, a directory that should reflect enrollment and graduation on its own, and a community that didn't want to be another login. Then we asked which of those the rented tools did well and which they only pretended to do. The honest answer was that the LMS was fine at hosting lessons and bad at everything around them.
So the platform is built around the school rather than around a course catalog. A learner lands on a dashboard for their cohort: what's next, the next live session with the join button right there, the recording of the one they missed, and the requirements checklist that saves as they go. Staff see the same data from the other side: who's enrolled, who attended, what's been signed off, and the records export the state asks for, generated rather than typed. SCORM and Rise packages sit edge to edge inside the page instead of in a frame with scrollbars. The directory lists a learner the moment they enroll and promotes them when they graduate, with nothing for anyone to remember. The assistant answers from the course material and is explicit about what it won't do: no grading, no medical advice, no answers that aren't in the program.
Where it stands is the interesting part. After a hard look with the school's director we narrowed the first release back toward the learning experience and the cohort tools, the pieces that replace the most seams, and pushed the rest to grow behind it. Faculty and staff are testing it privately. Students won't see it until every program is provisioned and the records are proven against the state's format, because a school can't have two sources of truth for even a week.