We've Taken Courses on Every Stack Teachers Use. Every One Broke Somewhere.
July 7, 2026
This piece comes from years spent as a paying student before Grishya existed — serious courses, serious fees, many teachers, and every setup below. Each teacher chose differently. Each course broke somewhere. Here is the honest tour.
Stack 1: WhatsApp + Zoom + Google Drive
The default. The one almost every independent teacher starts with.
What it gets right: everything starts instantly. Everyone already has WhatsApp. Zoom works. Drive is free. A teacher can announce a batch on Sunday and hold the first class on Tuesday.
Where it breaks: everywhere, slowly. The group floods, the notes scroll away, the recordings pile into a folder, and the discussion that made the course worth taking becomes unfindable within a month.
We wrote a whole piece about this one — the nine signs, if you haven't seen it. The short version: chat was built to move messages, not to keep them.
Stack 2: Teachable (and its cousins)
The "proper platform." Also the loneliest way to learn anything.
What it gets right: the recordings, finally, have a home. Videos in sequence, organized by module, playable on demand. After the Drive folder, this feels like civilization.
Where it breaks: that's all it is. A series of video sequences behind a login. The discussion layer is clearly not the product's focus — a comments box under each video, disconnected from any batch or cohort, with no fellow students you can actually see.
So you buy a course, receive a login to a walled-off site, and watch alone. The subject you joined a community of practice to learn — you now study in the most isolated format ever devised. And in practice, the teacher's real discussion still happens somewhere else: usually back in a WhatsApp group. The "modern platform" quietly needs the chat crutch anyway.
Stack 3: Private YouTube links
Free, smooth playback. And nothing else.
What it gets right: the video experience itself. YouTube plays everywhere, on everything, at every bandwidth. After Drive, this is what streaming is supposed to feel like.
Where it breaks: you get the videos — but where do the discussions go? YouTube is a broadcast channel. Unlisted links arrive in a chat group, live in the scroll, and carry no structure: no sequence, no "which class is this," no place to ask the question the video just raised. The learning half of the course happens nowhere.
Stack 4: Google Drive as the classroom
Storage, asked to be a streaming service.
What it gets right: it's where the recordings were going to end up anyway.
Where it breaks: playback that stutters on mobile, quality that drops when you need the diagram on screen, and — the part many students discovered the hard way — Google itself pushing back. When a whole batch streams the same files, Drive's limits kick in: quota errors, videos temporarily unavailable, the class recording refusing to play the night before the next class. Drive was never meant to be a video platform, and at batch scale, Google enforces it.
Teachers get forced to move mid-course because of exactly this — we've seen an entire batch migrate stacks halfway through a curriculum. Whatever moves in a migration like that, one thing never does: the accumulated discussion.
Stack 5: Telegram
WhatsApp's problems, with better file storage.
What it gets right: larger files, a proper channel for announcements, history that syncs across devices. On paper, the fixes for chat's worst habits.
Where it breaks: the same disease, different symptoms. The channel broadcasts, the linked group floods, files are marginally easier to keep and exactly as hard to find. Discovery is just as dead: the brilliant answer from March is as gone on Telegram as it ever was on WhatsApp. A better container for files is still not a container for knowledge.
Five stacks. The same three failures.
Different teachers, different tools, different fees — and every course broke along the same three lines:
The noise wins. Wherever discussion lived — group, comments, channel — volume beat signal, and the serious student with a job lost first.
Nothing has a home. Recordings in one place, notes in another, announcements in a third. Every stack scattered the course somewhere.
The memory never forms. Not one of these setups could answer the simplest question a learning community generates: "where is that thing from before?"
If those three sound familiar, they should — they're the same three ways chat groups quietly die. The stacks differ. The failure doesn't.
And then there's the sixth problem — the one nobody talks about
Here is the part every guide misses, because every guide is written from the teacher's side of the desk.
Serious students don't study under one teacher. In any deep subject, you learn from many — a foundation course here, an advanced batch there, a specialist workshop somewhere else. Five teachers is normal. And each teacher chose a different stack.
So the student's actual reality is: one course on WhatsApp + Drive, one on Teachable, one arriving as YouTube links, one on Telegram, one mid-migration between two of these. Five different systems, five different logics, five different answers to "where are the recordings?" — for one field of study.
The teachers each duct-taped one course. The student duct-tapes all of them, simultaneously — relearning a new broken stack for every teacher they study under. Your own learning — the thing all of this exists for — is the most fragmented artifact in the entire system.
Every teacher solved their own course. Nobody solved the student's shelf.
What we took from all of it
Years and serious money across these stacks taught us something no single course could: the problem isn't which tool a teacher picks. Every pick fails, because every tool solves a slice — checkout, playback, chat, storage — and no tool knows what a course-with-a-community actually is: a batch that moves together, discussions that belong to classes, recordings that live inside a structure, knowledge that accumulates, and a student whose learning deserves one home.
Until something does, every teacher will keep assembling the machine by hand — and every serious student will keep carrying five versions of the same broken shelf.
But the deepest cost isn't the teacher's hours or the student's patience. It's the knowledge itself. Every one of these stacks loses it the same way: the explanation that untangled a concept, the discussion that went somewhere no book goes, the answer that took a teacher twenty years to be able to give — written once, scrolled past, gone. Across five stacks and many teachers, that was the one constant: the knowledge is always what suffers. It gets taught, and taught again, and never gets to accumulate.
That, more than anything, is what needs a home.
This is the second piece in our notes on knowledge-first communities. Start with the first: Signs your WhatsApp or Telegram community is quietly dying →