Fees, exams, attendance, videos, parents. Today they live in a spreadsheet, a WhatsApp group and a stack of paper. Here is what each one looks like inside Course37, in screenshots from the real product.
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.

Enrollments, collections, exam activity and system health as they stand right now. It answers the questions you would otherwise ask three people.
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.

Home, courses, enrollment, about, contact. Open any of them, move the sections, rewrite the copy. Add a new page the week you open a new branch.

Drag sections into place and edit headlines, colors and fonts with the live page in front of you. No ticket, no developer, no waiting.

A real customer site running on Course37: their domain, their logo, their sections. Built in the same editor you get.
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.

Every course with its enrollment count, price and branch, editable in place. Nothing to keep in sync with a second spreadsheet.

Drop videos, PDFs and assignments into chapters. Students get the syllabus in the order you teach it, not as a list of links.
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.

Their courses, today’s live link, past recordings and class resources in one place. Nobody has to message you for any of it.

Recordings file themselves against the class they belong to. A student who missed Tuesday can find Tuesday.
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.

Type math and science questions with live preview and insert diagrams inline. What you see on screen is what prints on paper.

Describe the chapter and the difficulty. Anthropic Claude, Google Gemini or Groq drafts the MCQ, CQ and SQ. You edit and approve.

Every question filed by subject, chapter and difficulty. Next term’s paper starts from what you already wrote, not from a blank page.

Rank, score, percentile and per-question analytics the moment the exam closes. Export the PDF and pin it to the board.
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.

Build an answer sheet for 50, 100 or any question count, in any language, and export a printable PDF. You never buy pre-printed sheets again.

Run the filled sheets through the scanner you already own. The Dynamic OCR Algorithm reads the bubbles and grades every question set.
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.

Every student with batch, enrollment and payment status, filterable in a second. Act on a whole batch at once instead of one name at a time.

Courses, attendance, exam history, assignments and payments together. Answer the parent while they are still on the phone.

Scores over time and subject by subject strength. It tells you which chapter to teach again, not just who failed.

A printable card with subject breakdown, rank and remarks under your institution’s name. Hand it over at the parent meeting.
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.

Register a ZKTeco unit by its serial number and bind it to a classroom. It reports every punch as it happens, and you can see when a device was last heard from, so a dead unit does not quietly stop recording anyone.

Push a student to the device from their profile. Fingerprint, face or RFID card, whichever the unit supports. Their PIN on the device is their roll number, so nothing new to memorize.

Not only students. Teachers and office staff scan too, so the attendance you check on payroll day is the one the door recorded, not one somebody typed up afterwards.
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.

Every payment with its status, gateway and batch, plus manual entry for cash taken at the desk. The ledger closes itself.

Monthly collection, overdue balance and how each batch is actually paying. You find the leak in month two, not at year end.

A branded receipt is generated and emailed the moment a payment clears. Nobody messages you asking for one.

Set each teacher’s share once. Course37 does the split and shows what every teacher brought in and earned.
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.

Page views, visitors, session length, traffic sources and conversions on your own site. See where students actually come from.

Search Console data on keywords, impressions, clicks and indexing. Know the search that puts you in front of a parent.

Where people enroll and where they stop before paying. The drop-off finally has an address.
Fee reminders go out when somebody remembers. Class reminders never go out at all. Build the flow once in n8n and it runs whether or not anyone is at the desk.

Drag triggers, conditions and actions into a flow. A fee goes overdue at midnight and the reminder is already sent by morning.
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.

Every integration in one list with its credentials and a test button. You know a connection works before a student hits it.
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.

Build a role out of module and action permissions, then assign it. The desk records payments and never opens the question bank.
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.
Model Context Protocol
POST /mcp
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.