Loading…For entrance, bridge course, Loksewa and tuition centres: turn enquiries into admissions, run batches that start when they start, and keep the money straight. One learner, several batches, one ledger that reconciles.
Ask a centre owner what hurts and they rarely say attendance. They say the fifty people who called in Baisakh and the eleven who came back.
Enquiries live in a phone, a diary and three WhatsApp threads, and nobody can say how many turned into admissions.
A counsellor leaves, and their follow-ups leave with them.
The same student is in the morning MBBS batch and the evening bridge batch, and the software insists a student is in one class.
A batch starts in the middle of the month, so a system built on one annual fee has nothing sensible to charge.
Instalments are tracked in a notebook, and the reminder happens when somebody remembers.
A student moves from the 6am batch to the 5pm batch and the fee record has to be unpicked by hand.
The funnel, the batches and the money, in one system that already knows who each learner is.
Every enquiry is held with its source, the counsellor responsible, each follow-up and the outcome, then converts into a student without retyping anything. Reports show conversion by source and by counsellor, and why the lost ones were lost.
One learner sits in several batches at once, and each batch carries its own start and end date, days and time, instead of one class per year. Moving a student between batches moves the enrolment and leaves the ledger alone.
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 course is priced as a package with an instalment schedule counted from the batch start rather than from a school year, so a batch beginning mid-month bills correctly without anyone doing arithmetic.
Your batches and your fee shape go in first, because everything else hangs off them.
Tell us how your centre runs: batch shapes, how you take fees, how enquiries reach you.
Send us what you already have, in a spreadsheet or an export, and we validate it before anything is written.
Your batches, timings and course packages are set up to match how you actually teach.
Enquiries start landing in the funnel with a counsellor against each one.
Fees, attendance, staff and permissions run from the same records from day one.
Show us how your coaching centre 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.