NexusOne.coach
LMS, Live Classes & Coaching Platform
Problem
Coaches and course creators running live cohort-based programs need more than a video call link — they need enrollment, scheduling, attendance that actually reflects who showed up, automated assessments, and a way to get paid per-instructor across potentially many collaborators on one platform. Most LMS tools handle content well and live delivery poorly, or vice versa.
Architecture
Full-stack coaching platform architected around three pillars: content (courses, cohorts, automated assessments), live delivery (Zoom Meeting SDK sessions scheduled against Google Calendar, with Socket.IO tracking join/leave events to build real attendance records instead of trusting self-reported presence), and money (Stripe Checkout for one-off purchases, Subscriptions for recurring cohort access, and Connect for splitting payouts to instructors). REST APIs are guarded by a comprehensive RBAC layer — students, instructors, and admins see different capabilities from the same endpoints — and every privileged action writes to an audit log. Firebase drives the notification layer: automated reminders fire ahead of live classes and engagement nudges go out based on activity.
Trade-offs
Deriving attendance from Socket.IO join/leave events instead of a manual instructor checklist is more accurate but more fragile — a flaky connection can look like a student left when they didn't, so the attendance record reconciles brief disconnects (under a threshold) rather than logging every blip as a leave event. Using Stripe Connect for instructor payouts pushed onboarding complexity onto each instructor (they must complete Stripe's own KYC), but it moved compliance and payout-timing risk off the platform entirely rather than the platform holding and manually disbursing funds.