Design system · 2026 · LessonCruncher
LessonCruncher
An AI-forward lesson-planning design system for educators and administrators — prompt-to-standard alignment, measurable outcomes, and a practice loop built to merge into state K–12 ecosystems.
Summary
Executive summary
Problem
Teachers are expected to teach to standards, connect lessons to student interest and regional context, and prove measurable impact — often with tools that generate content but not accountability.
Approach
Designed and shipped LessonCruncher as a licensable district product: Google Stitch for high-fidelity surfaces, DESIGN.md tokens translated into Next.js components, standards mapping before generation, a Plan → Teach → Measure → Lift loop, and procurement-ready Stripe checkout with PO invoicing.
Outcome
Live at lessoncruncher.com with interactive demo and self-service checkout. Portfolio interactives and the production app share LessonCruncherDemoApp — the same five-step educator loop readers walk in the prototype below.
Guided Flow
Walk the LessonCruncher loop
The prototype follows the same five-step educator loop as the shipped app — prompt, standards alignment, generated lesson, practice loop, and district merge.
Problem
Diagnosis
Teaching to the test is not inherently wrong — it becomes a problem when alignment is invisible, student relevance is an afterthought, and administrators cannot audit whether a single lesson moved proficiency for students, families, or the educators around them.
Educator interviews
Teachers wanted AI help but distrusted outputs that did not show which standards, rubric items, and formative checks a lesson would hit before they edited it.
Administrator procurement
District buyers asked for one mergeable product — SSO, roster sync, standards packs, analytics — not another standalone generator.
Student relevance
Lessons that connected local economy and student interest saw higher engagement, but teachers lacked time to weave those threads into standards-heavy units.
Constraints
What was fixed
Standards before generation
The system must show standards mapping and assessment bridges before lesson content appears — administrators need auditability, not surprise alignment.
Audience: educators and administrators
Teacher workflows and district dashboards share one design language but different information density; neither surface can feel like a consumer chat toy.
SKU-ready packaging
Visual and interaction patterns had to communicate licensable product boundaries — pilot, merge, procurement pack — not a single-school experiment.
Illustration-only brand
No photography. Nickelodeon-influenced characters and thick-outline illustration keep the brand approachable for K–12 without looking childish to administrators.
Principles
Design principles
01
One lesson, generational leverage
Every generated plan should tie classroom work to measurable outcomes that families and peer educators can extend — not a disposable worksheet.
02
Make alignment visible
Standards codes, rubric tags, and exit-ticket bridges appear in the UI before teachers commit to a lesson.
03
Practice loop, not one-shot AI
Plan → teach → measure → lift is the core operating model for educators and the admin rollup that proves impact.
04
Design for merge
Components assume eventual district SSO, roster sync, and state standards packs — the system is built to be purchased or merged, not forked per school.
Exploration
Concept exploration
Before locking the district SKU, I explored four product postures in Google Stitch. Two consumer-style directions failed the trust test with teachers and administrators. The shipped system pairs a standards gate before generation with admin rollup and procurement surfaces district buyers expect.
- Rejected — no standards audit path
Direction A
Consumer chat-first generator
MagicSchool-style prompt-to-lesson flow optimized for speed. Teachers got output fast, but alignment appeared after the fact — if at all — with no audit path for administrators. - Rejected — teachers distrust retroactive tags
Direction B
Post-hoc alignment panel
Generate first, then tag standards in a side panel. Familiar to teams shipping fast, but educators in interviews said retroactive tags felt like cover, not accountability. - Shipped — standards accountability first
Direction C
Standards gate before generation
Teachers lock Massachusetts framework codes and formative bridges before AI runs. The generate action stays blocked until alignment is explicit — the core differentiator versus consumer AI lesson tools. - Shipped — companion surfaces for district buyers
Direction D
District admin rollup and procurement pack
Administrators audit practice-loop completion, standards coverage, and teacher activity from one SKU rollup. Pricing, formal quotes, and checkout support card and PO paths school business offices expect.
Specification
Development-ready standards gate
Direction C moved forward into specification — the screen engineering estimated against before any lesson content could ship. The figure below is the standards gate handed to development: framework selection, locked standard chips, formative bridge, and a blocked generate action until teachers approve alignment.
- Framework picker — Massachusetts Curriculum Frameworks scoped by grade band
- Standard chips — codes locked before generation, not tagged afterward
- Formative bridge — exit ticket and rubric hooks tied to each standard
- Teacher approval — explicit confirm before the lesson draft appears
- Blocked generate CTA — AI cannot run until alignment is locked
- Admin audit hook — alignment state rolls up to district coverage maps
Decision
What moved forward
| Option | Buyer trust | Engineering scope | District procurement fit |
|---|---|---|---|
| Teacher consumer SaaS | Low for districts — no audit trail | Smallest initial build | Poor — principals cannot defend spend |
| Standards-first district SKU | High — alignment visible before generation | Moderate — gate, loop, admin, checkout | Strong — COMMBUYS-ready packaging |
| LMS module / white-label only | Depends on host LMS | Largest integration surface | Delayed — no standalone procurement story |
Standards-first district SKU
The standards-first district SKU moved forward because it satisfied both educator distrust of black-box AI and administrator need for one mergeable product. Consumer SaaS was faster to sketch but could not survive a procurement conversation; white-label-only deferred the SKU story districts were actually buying.
Outcome
What shipped
LessonCruncher ships as a district-licensed product with a live marketing site, interactive demo, and payment flows principals and procurement offices can use without a sales call.
- Product site
- Live
- Practice loop
- 5-step
- Checkout
- Stripe
lessoncruncher.com with subdomain routing
Prompt, align, lesson, lift, merge
Card checkout + PO invoice requests
The design work extended beyond the prompt box — procurement quotes, admin coverage maps, and checkout had to feel as credible as the teacher loop for district buyers signing purchase orders. Stitch accelerated the visual language; production work translated DESIGN.md tokens into Ubuntu via next/font, wired Stripe and PO routes, and deployed through subdomain middleware on Vercel.
Reflection
Looking back
LessonCruncher sits at the intersection of systems design and sector politics. Google Stitch produced annotated HTML in LessonCruncher/stitch_automated_attachment_executor; DESIGN.md tokens became lessoncruncherUi.ts and the live Next.js app at src/app/lessoncruncher. The interface had to earn trust from teachers burned by AI that hides its alignment work, and from administrators who need merge paths, not demos. Building it as a SKU-first design system — not a feature page — is what made the state ecosystem story credible.
Available
Need something similar?
Best fit for platform UX, growth systems, internal tools, and teams that need a senior IC who can shape the problem and ship the details. I respond to most inbound within a day.
