From WhatsApp links to one platform: how we gave a growing tutoring centre its time back

The challenge: great teaching, buried in admin

The centre's teaching was strong. Its operations were not built to grow.

Like most tutoring businesses, they had tried the well-known tools: Zoom, Google Meet, Microsoft Teams and Google Classroom. Each one handled the video call. None of them handled the business around it.

A normal week looked like this:

• Links sent by hand. Before every class, staff opened WhatsApp or Facebook Messenger and sent the meeting link to each group, one by one.
• Every change meant starting again. Move a class by an hour and someone had to contact every affected student a second time.
• Documents everywhere. Course materials travelled through chats and Classroom posts, and nobody could be sure who had what.
• No single view of a client. When a student bought a second course, their details lived in several places. Filtering by class, subject or programme was guesswork.
• Feedback and exams were awkward. Collecting student feedback or running a test meant yet another tool.

With a handful of groups, this was annoying. Once numbers grew, it became the main thing holding the business back.

How we started: we lived their days before writing any code

We didn't start with a requirements document. We started by becoming the client for a few days. Over three to five days, our team:

• Sat in on real classes alongside teachers, to see how a session actually ran.
• Played the student, joining meetings and waiting for links like any learner would.
• Tested the administration hard. We messaged the centre's WhatsApp and Facebook page with every kind of request, on purpose, to see where the process strained.
• Talked to everyone: owners, teachers and students.

Interviews tell you what people think the problem is. Living the problem shows you what it really is. It also let us suggest solutions the client hadn't thought to ask for, because we had felt the same friction ourselves.

Our approach: one feature first, then the snowball

We could have planned a huge platform and disappeared for a year. Instead, we shipped one feature in one month and let the client touch it.

The first feature: one-click classes. We studied the Zoom API in depth, then built two small portals and a simple admin side:

• The centre enters names, days and times once, and the platform creates an account for every student and teacher.
• Each student sees their own classes, often 10 to 15, in their dashboard. Each teacher sees theirs.
• On the day, the teacher clicks Launch. Students click once and they're in. No link was ever sent.

The moment it clicked. The first time a teacher pressed that button and found every student already waiting in class, the client's reaction said it all. They stopped seeing a video tool and started seeing a system to run the whole centre.

Then the snowball. Because we had already lived the client's days, we knew what came next. Each new feature answered a real request:

1. 1.Class recordings, because the first thing students asked after a class was to watch it again.
2. 2.Documents, so course materials live next to the class they belong to.
3. 3.Attendance lists for teachers, so the centre can see exactly who showed up.
4. 4.Direct contact tools, so staff can call or message a student from their profile, like a CRM app built into the platform.
5. 5.Two-click rescheduling: change a time, and every affected student is notified automatically.
6. 6.Session reminders, so students always know what's next.
7. 7.A live admin dashboard with students, teachers, groups, courses and statistics on one page.
8. 8.An end-of-year revision module, which lets existing students sign up for final-exam preparation.

What went wrong, and what it taught us

No real project runs perfectly. These are the moments that shaped how we build today.

Returning students landing in old accounts. When a student came back the following year, the centre sent them a fresh link. But cookies from the previous year were still in their browser, so the link opened their old account. We spotted it quickly and fixed how accounts and links are handled for returning students.

30% of classes weren't being recorded. At first, teachers had to start the recording manually at the beginning of each class. People forget, and about 30% of sessions went unrecorded. After digging into the Zoom API, we switched on automatic cloud recording. Now every class is recorded without anyone lifting a finger.

The lesson behind both: remove the human step. Early on, when the owner wanted something done, he told the teachers. But instructions get missed. If you want a process to be measurable and close to error-free, it has to be built into the system as a click or a request, not left to someone's memory. Every manual step you leave in is a place where things break.

That principle now guides every platform we design.