Why WhatsApp and Google Drive Break Your Music School After 20 Students
Three concrete failure modes that appear once your music school starts growing. Not as a warning, but as recognition.
A student is looking for last week’s PDF. He cannot find it. He asks you. You search in WhatsApp. You scroll. Five minutes later you send a link. The lesson continues.
That is how it goes with 15 students.
With 25 students you do this 25 times a week. With 50 students you do it twice a day. At some point you never stop searching. You are searching continuously.
Failure mode 1: Scattered files
The standard setup of a music school growing without a system:
- Lesson material in WhatsApp conversations
- Sheet music in a Google Drive folder (sometimes several)
- YouTube links in the chat
- Notes in a notebook or your head
This works perfectly with 8 to 12 students. You know every student, remember what you sent, know where everything is.
With 20 students it starts to creak. With 30 students it is broken.
What specifically goes wrong:
A new student starts. You create a folder in Drive. Drive folder A. In WhatsApp you send the link. Later you also send a direct file. Then a colleague sends something. Now this student’s lesson material is in three places.
The student searches. Does not find everything. Asks you. You search. You send it again.
Repeat this with 30 students.
What solves it: one place per student. Not one folder per student in Drive. One lesson plan per student in a system built for exactly that. The student clicks on it. Everything is there. Done.
Failure mode 2: No visibility on progress
Ask yourself: which students are behind on the programme?
If you need more than two seconds to answer that, you have no system. You have a memory. And a memory does not scale.
With 15 students you know the answer by heart. With 35 students you are guessing.
What specifically goes wrong:
You stand in front of a student you have not seen for three weeks. (Holiday plus sick message plus his father called off.) You do not remember where you left off. You ask. The student does not quite remember either.
You improvise a lesson. The lesson is not bad. But it is not what you intended to do.
What solves it: a lesson plan with progress tracking. Not in your head. Not in a spreadsheet. In a system where you can see per student what has been done, what is current and what comes next. Click and you know.
Failure mode 3: Zero substitutability
What happens if you are ill tomorrow?
At most music schools: the lessons do not go ahead. Students get a message. Some parents are annoyed. You have no income. A week later everything starts again.
This is not bad luck. This is a structural problem.
What specifically goes wrong:
You ask a colleague to cover. The colleague asks: what should they do? You quickly send something via WhatsApp. The colleague half understands it. The students have a strange lesson. You would rather just do it yourself.
What solves it: a lesson plan a substitute can open and understand without you. Not “see WhatsApp from last week”. But: open this lesson plan, this is the structure, this is what the student can already do, this is what is planned for today.
The difference between a job and a business.
The threshold is around 20 students
This is not a magic number. But it is the point where most teachers first notice that their system — or lack of one — is slowing them down.
Below 20: you remember everything, it works. Between 20 and 35: it starts to creak. Above 35: without a system you are more administrator than teacher.
This is not a criticism of you. This is the nature of growth. Every profession has a point where informal stops being scalable.
For music schools the answer is a lesson platform. Not a better folder in Drive. Not stricter WhatsApp discipline. A system built for one-place-per-student.
Two questions to answer:
- Which of the three failure modes do you recognise?
- When does something need to be bad enough to change it?
Try Musicdott — First month free. First student live within 10 minutes. See the three plans or start now.
Questions? Email mail@musicdott.app or WhatsApp.
— Stefan, drum teacher and maker of Musicdott
Note: this piece started as an AI draft (Claude), edited and rewritten by Stefan. Numbers and recognisable scenarios come from personal experience and conversations with beta users.