Fees, exams, attendance, videos, parents. Today they live in a spreadsheet, a WhatsApp group and a stack of paper. Here is each one inside Course37: watch it work, then see the real screens.
Monday morning you check the bank app for fees, a register for attendance, a spreadsheet for who enrolled. The dashboard answers all three before your tea goes cold.
How it works
What the dashboard pulls together
See it in the app
The person who built your site stopped replying. Changing one batch fee costs you a message and a three day wait. Edit the page, see it change, publish when you are ready.
How it works
From idea to live website
See it in the app
Today a course is a Drive folder, an unlisted video link, and a fee list in someone’s head. Build the syllabus once, then decide exactly who is allowed to open it.
How it works
How a course is put together
See it in the app
You paste the class link, then answer "link please" eleven times, then upload the recording somewhere and forget where. Schedule the session here and it lands in the student dashboard, recording included.
How it works
A live class, start to finish
See it in the app
The scripts are on the desk, the red pen is out, and tomorrow you will type the merit list into a spreadsheet. Write questions once, run the exam, publish results the same evening.
How it works
From question bank to result
See it in the app
Paper exams still end in a stack of answer sheets and an evening of ticking boxes. Design the OMR sheet, print it on plain paper, scan the filled copies, read the merit list.
How it works
How OMR checking works
See it in the app
A father asks how his daughter is doing. Attendance is in a register, marks are in a notebook, payments are in a spreadsheet, so you promise to call back. One profile holds all three.
How it works
One record for every student
See it in the app
Ten minutes of every class goes to reading out names, and the register still says a boy was present when he was not. Put a device on the door. The scan is the record, and it is in the system before the teacher reaches the board.
How it works
How attendance is taken
See it in the app
Friday goes to a spreadsheet: who paid, who paid half, who promised last month and vanished. Payments record themselves as they land, and the ones that did not land get flagged.
How it works
How a fee is collected
See it in the app
You spend on boosts and banners and cannot say which one filled the batch. Traffic, search rankings, enrollments and payments sit in one view, so you can stop paying for what does not work.
How it works
What the numbers tell you
See it in the app
Fee reminders go out when somebody remembers. Class reminders never go out at all. Build the flow once and it runs whether or not anyone is at the desk.
How it works
How an automation runs
See it in the app
Nobody wants to abandon the payment gateway, the SMS provider and the meeting tool they already use. Connect them from one screen: paste the key, test it, go live.
How it works
How an integration connects
See it in the app
Everyone works from the owner’s login because making a second one was never worth the trouble. Give each person a role that reaches only what their job needs, and keep a record of what they did.
How it works
Who can see what
See it in the app
Connect any MCP-compatible agent and it does what an admin does: record a payment, schedule a class, pull a merit list. It signs in with OAuth2 and reaches only the scopes you grant.
How it works
How an AI agent works with Course37
See it in the app
Tell us how you run batches, fees and exams today. We will show you the parts of Course37 that replace it, and the parts you can ignore.