A school's daily life fits in three questions
Who is enrolled in what? Who attended? Who has paid? Three simple questions — but asked every week, for dozens of students, across different formulas (individual lessons, group classes, workshops, ten-session cards), they produce an administrative load that quickly eats into teaching time.
Existing school-management software targets conservatories and large structures: priced accordingly, and rigid precisely where your specificity lies — your formulas, your periods, your make-up rules.
Your formulas, your slots, your application
Describe your school: “I run a music school. Students enrol in weekly lessons (piano, guitar, voice) with a teacher and a time slot. I record attendance; absences can be made up within the term. Families pay per term. I want this week's attendance, due make-ups and late payments.”
The generated application fits that organisation: students and families, classes and slots, attendance sheets, per-period payments — and the dashboard answering the three daily questions.
- Student (and family) records with enrolments
- Classes, slots and teachers
- Attendance sheets and make-ups
- Per-period payments with statuses
- Dashboard: headcount, attendance, arrears
A tool the teaching team adopts
A school tool succeeds or fails in the classroom: if the attendance sheet takes more than thirty seconds, it won't be kept. The generated application is a web application usable on a phone or tablet: the teacher opens their slot, ticks who's present, the information is centralised.
Generated demo data simulates a living school — students, varied enrolments, attendance history — so you evaluate the tool immediately, before entering real data.
The school grows, the tool follows
A new discipline, summer workshops, a new pricing rule: regenerate the application from an enriched description, or export the code (ZIP, GitHub) and evolve it freely — it's standard Next.js + Prisma.
The Discovery plan (€0) covers the first version. Pro (€25/month) and Max (€149/month) provide credits to iterate, with the cost shown before each generation.
Typical generated entities
- Student
- Class
- Time slot
- Attendance
- Payment
Generated screens
- Student list and enrolments
- Class schedule per teacher
- Slot attendance sheet
- Per-period payment tracking
- School dashboard
Dashboard indicators
- Headcount per discipline
- This week's attendance rate
- Pending make-ups
- Late payments
Frequently asked questions — class management
Our formulas are unusual (session cards, family bundles). Can it handle them?
Yes — that's the principle: describe your real formulas (10-session card, sibling discount, week-long workshop) and the generated structure reflects them. You validate the plan before generation.
Can teachers take attendance on their phone?
It's a responsive web application: a slot's attendance sheet opens and fills from a phone or tablet, with nothing to install.
Can we track students' progress?
If your description provides for it (levels, exams, lesson notes), those concepts become fields and histories in the application.
Do families get access to the tool?
The generated application is the school's internal tool. Since the code is exportable and standard, a family portal can be added later by a developer if the need is confirmed.
How long to get started?
One generation produces the complete application, deployed at its URL, with demo data. Describing your school takes minutes; the proposed plan is validated before generation.