Online learning platform
A student moves through the course step by step, submits work and sees their progress, a teacher reviews and replies, and payment is what opens access.
- Buildfrom $3,550
- Timeline6–10 weeks
- Supportfrom $420/mo
Who this suits: A course that already lives in recordings, a chat and a spreadsheet: access is granted by hand, assignments are reviewed in private messages, and nobody knows who stopped where.
What is in the first version
- modules and lessons
- assignments and review
- student progress
- payment and access
The figures above are the package this sits on: MVP or full product. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
Payment opens exactly what was bought
Access opens by itself after the payment and follows from the payment state, not from a mark in a spreadsheet.
- 02
The student moves in steps
The system remembers where the person stopped, opens the same place on another device and shows the next step.
- 03
Into a queue and back answered
Once reviewed it comes back with a comment and moves the progress, so both sides look at one state.
What decides whether this works or annoys people
Video is not a server file
It goes through a delivery service with short-lived links, though copying stays possible: what a copy cannot take is the review.
Review runs at human speed
The platform is as fast as the teacher, and people leave over silence, so the student sees the review deadline.
The access term is decided first
Forever, for a cohort or while a subscription runs are different promises, and they cannot be rewritten after the first payments.
What to measure once it is live
- students who reach the end of the course
- time from a submission to a reply
- the lessons where people most often stop
- payments that open access without an administrator
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- Frontend and the student screensTypeScriptReactNext.js
- Server and dataNode.jsPostgreSQLPrismaRedisS3Docker
- Payments and notificationsStripePaddleTelegram Bot APIGrafana
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- video storage and delivery
- the payment fee on every course payment
- email to students: access, reminders, replies
- hosting, the database and space for student work
Asked before the first call
- Why not a boxed course platform?
- Usually you should use one, and we will say so. Your own pays off where teaching is part of the product, or where the revenue share and the limits already get in the way.
- Where does the video live and whose is it?
- In your own account with the video service: the invoice comes to you, the files can be taken without us, and we keep no copy. The platform holds the link.
- Can we add courses and lessons ourselves?
- Yes: courses, lessons, materials, assignments, prices and access terms are set from an admin screen. A new kind of assignment is code, so it goes through us with the price named first.