El-Professor
A multi-tenant SaaS that runs tutoring schools end to end: scheduling, attendance, payroll and billing.
Problem
Tutoring schools juggled professors, students, rooms and payments across spreadsheets, with overlaps and lost revenue everywhere.
Approach
I built the whole thing: isolated schools, role-based portals (admin / professor / student), and a scheduling engine with conflict-detection so no professor, room or group gets double-booked.
Outcome
It's live, and a client pays for it: 1,000+ student records, 4,200 classes and 8,100 teaching hours processed in a single year. Student debt computes from attendance; professor salaries from the classes actually delivered.
Hardest part
Conflict detection across three independent axes (professor, room and student group), where any one collision invalidates a slot.
Tenancy
Every school is isolated. One deployment, no cross-tenant leakage, role-based access enforced server-side.
Version 2
A second version is in progress. Version 1 runs for its client on a private link.