
Batches, not one class per year
Classes run as batches with their own days and times and no academic year behind them, and one member attends several, which is what a member taking two instruments actually looks like.
Loading…For music schools, dance and art academies, sports clubs and driving schools: members rather than a year group, recurring monthly fees, and lessons that get rescheduled without anyone keeping a private list.
An academy has members who join in any week, take a class at a level rather than in a year, and pay every month for as long as they keep coming.
A member joins in the third week of the month and the system wants an admission date in an academic year.
Levels are grade 1 to grade 8 of an instrument, or a belt, and they have nothing to do with a school grade.
Fees are monthly and recurring, and stop when someone stops coming.
A missed lesson is made up the following week, and there is nowhere to record that it was.
The same person takes guitar on Tuesday and drums on Saturday, and the system says one class.
Half the members are adults, and every screen assumes a guardian.
Members, schedules and recurring money, without an academic year anywhere in sight.

Classes run as batches with their own days and times and no academic year behind them, and one member attends several, which is what a member taking two instruments actually looks like.

A monthly membership or a pack of sessions bills on its own cycle and runs until it is stopped, rather than an annual fee split into terms. Stopping a membership stops the billing, and the ledger keeps the trail.

Fee heads and structures, invoices generated in runs, payments recorded against them, concessions, refunds and late fines. Every reversal needs a reason and keeps its trail, so the books reconcile rather than merely balance.

Permissions are set per role and per person, and enforced on the server on every request. Hiding a button is not security here: a request crafted by hand gets the same answer as one that came from a click.

Full staff records with departments, designations and qualifications, one leave flow that marks attendance when it is approved, and Nepal payroll with PF, SSF, TDS and festival allowance.

Bulk import with a dry run first: validate, see exactly what would change, fix it in a grid, then commit. Guardian records are de-duplicated and Bikram Sambat dates are detected rather than mangled.

Your data is backed up nightly to storage held with a different provider in a different jurisdiction, encrypted before it leaves our servers, and we practise restoring it. A backup nobody has restored from is a hope, not a backup.

A missed lesson and the make-up that settles it are both recorded against the member, so the member and the instructor can see what is owed without anyone keeping a private list.
Your levels, your schedule and your billing cycle go in first.
Tell us how your academy runs: levels, schedules, and how members pay.
Send us the member and staff records you already keep, in whatever form they are in.
We validate them before anything is written and show you exactly what would change.
Your classes, levels and membership plans are set up to match how you teach and charge.
Members, schedules, make-up lessons and recurring fees all run from the same records.
Show us how your academy works today, registers, spreadsheets or another system, and we will show you what moving across actually looks like. No pressure, and a straight answer on price.