LiveOwn productBusiness systems

EasyTutor

A tuition centre that runs itself.

Tuition centres keep their timetable in one book, attendance in another and fees in a WhatsApp thread. EasyTutor puts the whole operation in one place, so the work of chasing and recording stops being a person’s job.

Type
Own product
Status
Live
Category
Business systems
Technology
Next.js, PWA, Google Workspace, DuitNow QR
EasyTutor home page with the teaching calendar of a tuition centre

A tuition centre is a scheduling business, a billing business and a reporting business at the same time. EasyTutor is what happens when all three stop being separate jobs.

Key features

  • Classes, sessions and attendance in one timetable
  • Fee invoicing and payment tracking
  • Parent reports and tutor payslips
  • Separate workspace per centre, with team access

The situation

Almost every tuition centre runs on the same three things: a timetable in a book, attendance on a printed sheet, and fees in a WhatsApp thread. None of them are wrong on their own. The problem is that they never agree with each other.

The cost shows up at the end of the month. Someone sits down to work out who attended, what they owe, what was already paid, and what each tutor is owed for the hours they taught. That reconciliation is a full evening of work, and it is rebuilt from scratch every month because none of it was recorded in a form that adds up.

It also means the answer to a parent asking "did my child go last Tuesday?" depends on whether the right person is holding the right book.

What was built

One timetable for the whole centre

Classes, sessions and attendance sit in the same place. Marking a student present is the same action that feeds the invoice, the parent report and the tutor’s hours - not three separate records that have to be made to agree later.

Fee invoicing and payment tracking

Invoices are issued from the sessions that actually happened, and what is outstanding is visible without anyone building a list. Chasing a payment stops being an act of memory.

Parent reports

Attendance and progress go back to the parent from the record the centre already keeps, rather than being written out by a tutor at the end of a long day.

Tutor payslips

Hours taught become a payslip. The same attendance data that produces the parent’s report produces the tutor’s pay, so the two can never disagree.

A workspace per centre

Each centre gets its own space, its own team accounts and its own billing. Staff see their centre and nothing else.

Why it was built this way

Attendance is the spine, not a feature

Fees, payslips and parent reports are all downstream of one fact: who actually turned up. Building attendance as the centre of the system rather than one module among many is why those three outputs cannot drift apart. Most of the month-end reconciliation disappears because there is nothing left to reconcile.

Collect money where the money already moves

Malaysian parents already pay by DuitNow QR. Building a payment flow that asks them to learn something new costs collections, and the centre pays for that in unpaid fees. The invoice meets the payer where they already are.

One codebase, many centres

Every centre runs the same application with its own data. It means a fix reaches everyone the day it ships, rather than being applied one installation at a time - and it means the system can take another centre without another build.

Built to be handed over

A system that only its author can operate is a liability for the business paying for it. The admin side is written to be used by the centre’s own staff, without a developer standing behind them.

Where it stands

Live at easytutor.my and in use. Development is ongoing - it is a product, not a finished project, and it gets changed as centres run into things it does not yet handle well.

← All projects