From "We Need an LMS" to Building Classory
Almost every educator who moves online eventually says the same four words: "we need an LMS". This is the story of what those words really mean in India — and how answering them became Classory.
"We need an LMS."
Four words that sound like a software request. In practice they are usually a cry for help. Behind them sits a teacher running live classes on one app, sharing recordings on another, collecting fees through screenshots, answering doubts in a WhatsApp group of several hundred students, and quietly discovering that last month's lectures are circulating on a Telegram channel they never created.
Building an LMS — a learning management system — was never our goal in itself. Solving that sentence was. This article is the product story behind Classory: why generic tools kept failing Indian educators, the decisions we made instead, and an honest checklist for anyone thinking about building their own. (If you want the engineering deep dive on multi-tenancy, data isolation and scale, we wrote that separately in how we built Classory.)
TL;DR
- The problem wasn't features. It was fragmentation — too many tools, none of them designed for how Indian educators teach and get paid.
- Six decisions shaped Classory. Your own brand and domain, all-in-one, Clay the AI assistant, CodeLoop, secure video, and 0% commission with your own gateway.
- An LMS is a business system. Payments, protection, peaks and support matter more than the course page.
- Build only if the platform is your edge. Otherwise, run a white-label LMS and spend your energy on teaching.
Why generic tools fail Indian educators
Most global LMS products are designed around a corporate training department or a Western university. Indian educators — coaching institutes, tuition centres, independent teachers, colleges running value-added courses — work differently. The gaps show up in the same places again and again.
Fragmentation is the default
The typical stack is assembled one emergency at a time: a video-call tool for live classes, a cloud drive for notes, a form builder for tests, a spreadsheet for attendance, and messaging groups for everything else. Each tool is fine alone. Together they create a system that nobody designed, where students juggle logins and teachers spend evenings on administration rather than preparation.
WhatsApp is the real LMS
For many institutes, the messaging group is where announcements, links, doubts and fee reminders actually live. It's familiar and free, but information scrolls away, there is no structure, no progress tracking, and no way to separate a paid batch from a free one.
Payments don't fit
Indian learners pay through UPI, cards and instalments, often for batches rather than single courses. Chasing payment screenshots and reconciling them by hand is a hidden tax on every educator. Many course marketplaces solve this by taking a cut of every sale — which punishes the educator for succeeding.
Content leaks
Paid recordings are an educator's product. A plain video link can be forwarded in seconds, and once a lecture is loose on a piracy channel, the revenue it represented is gone.
Nobody sees your brand
On most marketplaces the student relationship belongs to the platform. The educator becomes a seller in someone else's store, under someone else's name.
Coding needs practice, not videos
For programming courses, watching a lecture is the easy part. Learners need to write code, run it and get feedback — which usually means sending them off to yet another third-party site.
None of this is unique to one institute. It's the shape of digital education in India as it moved online — a shift that bodies like UNESCO's digital education programme and India's Ministry of Education have treated as central to access and quality. The tools simply hadn't caught up with how Indian educators work.
The decisions that shaped Classory
We could have built a thinner product faster. Instead we made a small number of decisions early and let them shape everything else.
- Your brand, your domainClassory is a white-label LMS. Every academy gets its own workspace and identity, so students see the educator's brand — not ours. The relationship stays with the person who earned it.
- All-in-one, not another toolCourses and batches, live classrooms, exams with 18 question types, Drive, learning paths and gamification live in a single system. Adding a tool to the pile was the problem; we set out to remove tools.
- An AI co-teacher, inside the workflowClay is Classory's AI assistant. It helps learners understand concepts and practise, and helps educators generate questions — within the course, not in a separate chatbot tab.
- Practice where the learning happensCodeLoop gives learners an in-browser coding environment with autograding, so a programming course can include real practice without sending anyone elsewhere.
- Protect the productCourse video is delivered through signed, time-limited access and watermarked per viewer. No system can stop every screen recording, but casual forwarding becomes far harder — and traceable.
- 0% commission with your own gatewayMonetisation covers course sales, a wallet and subscriptions through Razorpay. When educators connect their own gateway, we take 0% commission on their sales. Their growth shouldn't be our toll booth.
You can see how these fit together on the Classory features overview, and dig into Clay, the AI teaching assistant, CodeLoop's in-browser coding practice and Classory's secure video delivery.
We didn't want to build a marketplace that owns the student. We wanted to build the infrastructure that lets an educator own their academy.
What building an LMS really involves
Here is the part most "we need an LMS" conversations skip. A course page with a video player is a weekend project. A learning platform that an institute can run its business on is a permanent product. If you are considering building an LMS for Indian institutions, this is the realistic scope.
| Area | What it really means | Why it's harder than it looks |
|---|---|---|
| Identity and roles | Students, teachers, admins, parents, multiple batches | Permissions multiply quickly; mistakes expose data |
| Courses and batches | Cohorts, schedules, drip content, learning paths | Indian institutes run batches, not just catalogues |
| Live classrooms | Sessions, attendance, recordings, discussions | Must work on patchy mobile connections |
| Assessments | Question banks, timed exams, many question types, grading | Exam day is your biggest traffic spike |
| Video | Upload, transcoding, streaming, signed access, watermarking | Storage and delivery costs grow with every lecture |
| Payments | Gateway integration, subscriptions, refunds, invoices, reconciliation | Money bugs are the ones customers never forgive |
| Branding | Custom domain, logo, themes, emails | Multiplies with every institution you serve |
| Practice and AI | Coding sandboxes, autograding, AI assistance | Needs isolation, cost controls and predictable usage |
| Operations | Backups, monitoring, security reviews, support | Never finished — this is the real long-term cost |
Then add the things nobody budgets for: mobile responsiveness on low-end phones, accessibility, data protection, and the steady stream of feature requests once real teachers start using it. We designed Classory's serverless architecture for 2M+ concurrent users precisely because exam mornings and batch launches don't care about your average traffic — the full reasoning is in our serverless write-up.
Build vs buy: an honest guide
We build software for a living, so it would be convenient to tell everyone to build. We won't. The right answer depends on where your advantage lies.
Build your own LMS if…
- The learning platform itself is your product or your core differentiator.
- Your workflows are genuinely unusual — deep integration with internal systems, unique assessment formats, regulated data handling.
- You can fund a permanent team for development, security, infrastructure and support, not just a launch.
Use a white-label LMS if…
- Your advantage is your teaching, your faculty and your results.
- You need to be live in days, not months, under your own brand.
- You would rather spend on content and marketing than on servers and on-call rotas.
For most coaching institutes and independent educators, the second list is the honest fit. That's exactly the gap Classory for coaching institutes is designed to fill.
Weighing the cost of building against running on a ready platform? Compare Classory's plans — no commission when you use your own gateway.
See Classory plans →If your needs truly are custom — an LMS woven into a larger enterprise system, say — that's the kind of SaaS product development our software team takes on, applying the same lessons we learned the hard way on our own product.
Why a product company builds for educators
Classory didn't come from nowhere. Incrix has worked in education from the start: through Incrix University we have trained 50K+ students across 50+ courses with 10+ partner institutions. We know what a batch looks like from the inside, and we know how much time goes into everything that isn't teaching.
Building Classory was also a deliberate choice to own a product rather than only deliver projects — a theme we explore in why we build products, not just projects and, more personally, in our founder's note on not wanting to just deliver projects. And it sits comfortably alongside our hardware work, which is why we write about building across software, hardware and design as one discipline. The bigger picture of how it all connects is in what we're actually building at Incrix.
From four words to a working academy
"We need an LMS" is rarely about software. It's about wanting one place to teach, one place to get paid, and one brand students remember. Our answer was to build that place properly, once, and let educators run their own academies on top of it.
If that sounds like the sentence you've been saying, start by exploring Classory — and if your problem is bigger than an LMS, tell us what you're building.