Founder-led, teacher-shaped, beta-tested
ClassMind is being built around the everyday planning loop teachers already use: plan, adapt, resource, teach, review and reuse.
ClassMind is in active beta. That means we are not presenting invented testimonials or unmeasured time-saving claims. We are collecting real workflow feedback first, then using it to improve the product and publish evidence responsibly.
What guides product decisions
- Teachers should stay in control of the final resource.
- One lesson idea should flow into plans, worksheets, slides and support materials without duplicate typing.
- Differentiation should use inclusive Support, Core and Greater Depth language, not crude labels.
- Feedback should measure editing effort before ClassMind makes claims about time saved.
How beta feedback is used
The in-app feedback form asks what was generated, how much editing was needed, what was accurate or wrong, whether the output was classroom-ready, and whether the teacher would recommend it. This is the raw material for product fixes, real case studies and permissioned quotes.
What comes next
The immediate focus is product quality, safety documentation, first-session workflow and reduced editing friction. Whole-school and MAT features should come later, after enough teacher proof and procurement evidence exists.