Case study 02Web2026

A school ERP, from scratch.

ClassSec is a white-label school management system for small private schools in Tier-2 and Tier-3 Indian cities — one product, where each school only brings its own name, logo and colours.

Role

Solo — design, backend, product

Stack

Flask · SQLite

Users

6 roles

Status

Paused

ClassSec principal dashboard for a demo school: attendance, fees and notices at a glance

All screenshots use a demo school with made-up students and staff.

01The problem

Small private schools juggle attendance registers, fee books, homework diaries and WhatsApp groups. Many of them need one simple system that works in English and Gujarati, handles multiple mediums and streams, and doesn't need an IT team to run.

02What I built

A working Flask + SQLite app with separate portals for every kind of user:

Super admin — me. Creates schools, uploads their logo and branding, and sets up their principal.
Principal — staff, classes, notices and school-wide analytics.
Teacher — attendance for assigned classes, homework and marks.
Student and Parent — timetable, homework, attendance, notices and fees.

It's built to handle real school structure: many standards, English- and Gujarati-medium divisions, and Science/Commerce streams in 11th and 12th — with Noto Sans Gujarati bundled in.

03Security decisions

Coming from a security background, a few choices were non-negotiable:

No payment gateway. Fees are recorded by school staff, so the system never touches card or bank data.
Role-based access. Teachers only see the classes they're assigned to; parents only see their own child.
Password resets, not visible passwords. Nobody — including admins — can read a user's password.
Click-to-chat alerts instead of a paid WhatsApp integration — no third-party API holding parent numbers.

Accounts page: passwords are stored scrambled and can only be reset, never read — Logins — passwords are hashed and can only be reset, never read back

04Screens

Every school gets its own name, logo and colours — this is the same product dressed as a demo school, with Gujarati alongside English throughout.

Sign-in page with separate portals for student, parent, teacher and principal — One sign-in page, four portals

Attendance overview showing present and absent counts per class — Attendance — every class at a glance

Fees office with collection progress and parents to call — Fees — collection progress and who to call today

Timetable builder with posted timetables for each class — Timetable builder — posted only when the principal is ready

ClassSec sign-in screen on a phone — Works on the phones parents actually use

05What I learned

I built ClassSec, took it to schools, and they said no — and that taught me more than the code did.

Good software isn't enough to make people switch. Every school I spoke to already had a system they were used to and a vendor they could call. Moving years of records and retraining staff is real work for them, so "we already have something that works" wins — even when the new option is faster, safer and cheaper.

To a buyer, school software is school software. If I can't show the difference in the first two minutes — something their current system makes painful and mine makes easy — it looks the same as what they already have.

Trust comes before features. A new, young founder is a bigger risk to them than an old vendor, no matter how good the demo is. Next time I'd lead with a free pilot running alongside their old system, references, and a clear support promise.

So ClassSec is paused, not dead. If a new school opens without existing software, it's ready — and the next product I build, I'll find the pain and the buyer before I write the code.

Next case study
Lyrics display