The LessonCraft Backstory
After 15 years in corporate training and 25+ keynote presentations, I kept watching educators manage their work across four different apps. LessonCraft is the attempt to fix that.
I spent fifteen years in corporate training.
That means I've delivered somewhere north of twenty-five keynote presentations, designed curriculum for organizations ranging from small teams to enterprise-scale rollouts, and sat in enough planning meetings to develop strong opinions about what makes educational software useful — and what makes it a burden.
The pattern I kept seeing was the same across every context: educators spending more time managing tools than teaching.
The Patchwork Problem
Talk to a K-12 teacher about their software stack and you will hear a familiar list. There's the LMS they're required to use by the district. There's the attendance system that doesn't talk to the LMS. There's the quiz platform they actually like but have to export manually into the grade book. There's the assignment tool, the communication platform, the resource library, the rubric builder. Each one has its own login, its own export format, its own quirks.
The teacher's job is to teach. But a non-trivial portion of their working hours go to data entry, format conversion, and the cognitive overhead of context-switching between four systems that were never designed to work together.
This isn't a new observation. EdTech has been promising integration for decades. What actually gets shipped is another standalone app with an API that, technically, supports data export.
I've watched this frustration play out in corporate training environments too — just with different job titles. Instructional designers wrangling content between an authoring tool, a SCORM package, and an LMS. Learning and development teams pulling reports from three different systems to build a picture of learner progress that should have been one dashboard.
The problem is structural. Most educational software is built by people who optimize for their specific vertical — assessment, or attendance, or communication — without thinking about how a teacher actually moves between all of these in a single hour.
What LessonCraft Is Trying to Do
LessonCraft is my attempt to build the thing I kept wishing existed: an integrated K-12 education platform where the core workflows live in one place.
That sounds like a large claim, so let me be precise about what that means in practice.
A teacher shouldn't have to export a roster from the attendance system to upload into the quiz platform. A student's assignment submission, their quiz performance, and their attendance record should be visible from the same interface, because they're all data about the same student. When a teacher builds a lesson plan, the resources, assessments, and assignments associated with that lesson should travel with it — not live in separate systems that happen to share a student ID.
That's the thesis. The execution is harder than the thesis, which is why LessonCraft is in beta and not shipping a version 2.0.
What's Live
LessonCraft is currently in beta at lessoncraft.cc.
The core platform handles lesson planning, assignment management, and student progress tracking. The ecosystem products being built around it include:
ClassCabinet — classroom management tools for attendance, seating, behavior tracking, and class configuration. The infrastructure layer that other features need to work.
Quizdex — assessment and quiz tooling with multiple question types, auto-grading, and results that feed directly into the grade book without a CSV export step.
Mira Tutoring — AI-powered learning support. The use case I'm most focused on here is differentiated instruction: giving teachers a tool that can adapt to individual student pace and learning gaps without requiring thirty separate lesson plans.
QuizCraft — live quiz hosting for classroom use. Real-time participation, leaderboards, the format that keeps students engaged. Coming soon.
DataCraft — analytics for educators. Aggregate view of class performance, early indicators of students who are falling behind, data that helps a teacher intervene before a student is already struggling. Also coming soon.
These aren't separate products with their own accounts and separate billing. They are components of LessonCraft. A teacher who uses LessonCraft has access to all of them, and the data flows between them.
What I've Learned Building It
A few things have become clear through building LessonCraft that weren't obvious at the start.
Teachers have almost no time. This sounds obvious, but the implication for software design is significant. Every onboarding step, every import wizard, every configuration screen is a reason to abandon the tool. Educator software needs to do more of the work automatically, surface the right information without requiring navigation, and reward the first five minutes of use rather than the fifth hour.
The district is a stakeholder whether you design for it or not. K-12 software exists inside institutions with their own procurement processes, data governance requirements, and technical constraints. Building something that a teacher loves but can't get approved by their IT department is not a complete solution. This is a hard problem that most EdTech startups handle poorly — usually by ignoring it until it becomes a sales blocker.
Accessibility in education software is not optional. Students use these tools. Some of them are blind, or have motor impairments, or use assistive technology. Building LessonCraft with accessibility as a first-class requirement is the only defensible position — practically and ethically. This one I feel particularly strongly about.
Where It Goes From Here
LessonCraft is early. The beta is live and I'm working with educators to understand what's working and what needs to change. The component products are in various stages of development.
If you're an educator, administrator, or someone in the EdTech space who wants to talk about this — I'm genuinely interested. The email is ryan@robworks.info.
Building software for education is a longer game than building a productivity tool. The feedback cycles are slower, the stakes are higher, and the customer relationship is more complex. I'm committed to it because the problem is real and the existing solutions are not good enough.
That's been true for the fifteen years I've been watching it. Time to do something about it.