Skip to content
Rathaworks

Case study · Bidyasagar ClassesAn online coaching platform that runs its own live classes

Admin, teacher and student portals for a competitive-exam institute — courses, batches, automated live classes, mock tests, a referral wallet and a book store in one system.

Built at GravitonesLive
Industry
EdTech
Location
Bhubaneswar, India
Timeline
Lead since May 2026
Year
2026
Illustration of an online coaching platform: course structure, a live class and a timed mock test
Illustration of the product. The client's production interface is confidential, so it isn't shown here — I can walk you through it on a call.

Results

role-based portals — admin, teacher and student
0
role-based portals — admin, teacher and student
screens across the three portals
0+
screens across the three portals
API routes behind the platform
0+
API routes behind the platform
question types with per-type negative marking
0
question types with per-type negative marking

The challenge

What the client needed.

An online coaching institute is quietly five businesses: a video library, an exam board, a live-classes operation, a store and a publisher. When I took over as lead developer, the platform existed, but teaching hung off courses, live classes were coordinated by hand against a small pool of Zoom licences, and growth tools like referrals didn't exist. The job was to make it run itself — without breaking it for the students already using it.

My role

Lead developer since May 2026 — took over an existing platform, re-architected teaching around batches and built live-class automation, the referral wallet and exam-engine upgrades

The approach

How I built it.

  1. 01

    Re-architected teaching around batches: content, live classes, recordings and access now belong to a batch, so one course can run many cohorts cleanly.

  2. 02

    Automated live classes: the platform allocates a free Zoom licence per slot, blocks clashes at scheduling time, shares one session across several courses and batches, and issues per-student registration links.

  3. 03

    Published class recordings automatically as soon as Zoom makes them available, and auto-closed stale sessions.

  4. 04

    Extended the exam engine: six question types with per-type negative marking, timed attempts, bulk spreadsheet import with duplicate detection and test series sold as products.

  5. 05

    Built the growth layer — coupons with limits, referral codes for students, teachers and partners, a wallet usable at checkout and admin-approved withdrawals — plus role-based access, a central doubt panel and support tickets.

Key engineering decisions

The hard problems, and how I solved them.

The decisions that made the difference — each one a trade-off chosen on purpose.

  1. 01

    Dozens of classes, a fixed pool of licences

    Problem
    Each Zoom licence hosts one meeting at a time; manual scheduling meant clashes discovered when students couldn't get in.
    Decision
    Dynamic host pooling: the system picks a free licence for the window and rejects a clash at the moment of scheduling.
    Outcome
    Class-start failures stopped being part of the working day.
  2. 02

    Teaching belongs to batches

    Problem
    Content and classes hung off courses, so running a second cohort of a course meant duplicating it.
    Decision
    Moved content, classes, recordings and access from the course to the batch, with batch management on its own screens.
    Outcome
    Launching a new cohort is an assembly job, not a rebuild.
  3. 03

    An exam engine students trust

    Problem
    Mock tests must mirror real exams — mixed question types, negative marking, strict timing — and years of questions lived in spreadsheets.
    Decision
    Per-type marking rules, answers saved as students work, and bulk import with duplicate detection.
    Outcome
    Instant, consistent results, and the question bank arrived as one bulk operation.
  4. 04

    Word of mouth, made measurable

    Problem
    Most enrolments came from recommendations nobody could see or reward.
    Decision
    Referral codes with a visible wallet, spendable at checkout or withdrawn through an approval queue, every credit recorded.
    Outcome
    An invisible channel became trackable and auditable.

What shipped

Everything that went live.

  • Admin portal

    Courses, batches, syllabus library, question bank, test series, live classes, payments, coupons, payouts and content.

  • Teacher portal

    Own subjects and batches, live classes, recordings, student doubts and support tickets.

  • Student portal

    Enrolled courses with progress, live schedule, study material, tests, results and analytics.

  • Live-class automation

    Zoom licence pooling, clash detection, shared sessions and automatic recordings.

  • Exam engine

    Six question types, per-type negative marking, timed attempts and bulk import.

  • Commerce & growth

    Razorpay checkout, coupons, referral wallet, withdrawals and a digital + printed book store.

Tech stack

  • React
  • Vite
  • TanStack Query
  • Node.js
  • Express
  • PostgreSQL
  • Drizzle ORM
  • Razorpay
  • Zoom API
  • AWS S3
  • KaTeX

Want results like these for your business?

Tell me what you need in two minutes. You'll hear back within 24 hours, and get a fixed-price proposal within 48 hours of our call.

  • Reply within 24 hours
  • Fixed quote in 48 hours
  • NDA on request