Why We Built LessonNest
The frustration, the early conversations with teachers, and the decision to bring planning, assessment and reflection into one place.
Why We Built LessonNest
Every teacher we spoke with described some version of the same problem: the tools meant to support their work were scattered across separate systems that never quite talked to each other.
Listening first
Before writing a line of code, we sat with teachers at Brightpath Education Trust and watched how they actually planned a week of lessons.
The pattern was consistent — plan in one place, assess in another, reflect nowhere in particular, and report everything manually at the end of term.
Choosing simplicity
We could have built something exhaustive from day one. Instead, we followed a principle that now shapes everything we build: clarity over complexity.
That meant shipping a smaller, clearer version of LessonNest first, and letting real classroom use tell us what to build next.
What happened next
Brightpath's early feedback confirmed the direction, and became the foundation for the workflows LessonNest now supports across planning, assessment and reflection.