School-aware
The calendar has to tell the truth.
Teachers do not work on a generic Monday-to-Friday grid. Planlark is built around cycle days, holidays, PD days, assemblies, and the real timetable that actually drives the week.
Planlark exists because most planning tools flatten teaching into a checklist. Real teaching is messier than that. It runs through rotating schedules, curriculum documents, last-minute changes, hallway voice notes, and the constant need to adjust tomorrow based on what happened today.
We are building Planlark as a teacher-led workflow where schedule logic, curriculum, unit planning, assessments, and AI actions all work together instead of living in separate tools. The work is being shaped by Andreas Much, Founder and CEO of Planlark, whose more than 25 years of actual in-classroom teaching experience in bilingual education continue to inform the product. His focus on technology integration and practical AI use in the classroom is central to how Planlark approaches planning, assessment, and day-to-day teaching workflow.

Why it feels different
The planner, the unit view, and the AI all work from the same school context.
What we optimize for
Less admin drift. More usable plans that survive the week teachers actually have.
Teacher-built
Planlark is being shaped around the rhythm of classroom work. That means the product has to respect planning as teachers actually do it: in fragments, across multiple classes, with curriculum pressure, and with constant small revisions after each day of teaching.
Planlark is made by teachers, for teachers, with product direction shaped by classroom reality rather than generic productivity trends.
Andreas Much, CEO and founder, brings more than 25 years of actual in-classroom teaching experience, including extensive work in a bilingual program.
Technology integration and practical AI use in the classroom are part of the founder perspective, not a trend added later for marketing copy.
The workflow starts from the materials teachers already use: curriculum documents, textbook excerpts, weekly pacing decisions, quick voice notes, and after-class adjustments.
We pay attention to the moments most products ignore: the class that gets bumped by an assembly, the lesson that runs long, the unit that needs to shrink, and the assessment that has to be rebuilt tonight.
That is why the product keeps circling back to the same idea: planning, teaching, reflection, and revision are one connected loop.
What we believe
School-aware
Teachers do not work on a generic Monday-to-Friday grid. Planlark is built around cycle days, holidays, PD days, assemblies, and the real timetable that actually drives the week.
AI that acts
Lark is being built to create, edit, move, delete, and regenerate real planning records inside the product instead of behaving like a disconnected chatbot.
Curriculum first
Outcomes, units, lessons, assessments, and daily adjustments should live in one connected system so teachers can see what they taught and what still needs to happen.
Built for reality
If a planning tool breaks the moment a class gets bumped, a lesson runs long, or a teacher wants to revise one assessment question by voice, it is not really built for school. Planlark is.
Teachers often plan in the hallway, in the parking lot, or right after the bell. Voice capture and quick edits are part of the product because that is when real planning happens.
A good plan is rarely finished in one pass. Planlark is designed so lessons, units, and assessments can be adjusted without rebuilding everything around them.
Different classes need different pacing, reading levels, and supports. The product is moving toward class-aware planning rather than one-size-fits-all templates.
Early access
Join early access and help us keep Planlark grounded in real classroom work, not generic software habits.
No credit card required. Early access updates only.