No admission enquiry left unfollowed. No fee reminder forgotten.
A system for the two seasons that decide an institute's year: admissions and fees. Enquiry capture, counsellor follow-up, fee schedules, results and parent communication — built around how your office already works, not how a generic ERP thinks it should.
The admission journey, end to end.
Five steps where enquiries currently leak — and where the system plugs each one.
- 01 · Enquiry
Website forms, walk-ins, phone calls and WhatsApp all land in one place, tagged by source — so you finally know whether your website, your hoarding or your referrals bring parents in.
- 02 · Follow-up
Every enquiry gets a counsellor, a status and a next-action date. Reminders fire on time, because the system remembers what a busy Tuesday makes everyone forget.
- 03 · Admission
Application status, document collection and pending items in one view. Parents stop calling to ask "did you receive the transfer certificate?" — they can see it.
- 04 · Fees
Fee schedules per class and term, installment plans, automatic WhatsApp reminders, receipts and a dues ledger your accountant can actually trust.
- 05 · Through the year
Attendance, results, certificates, report cards and parent communication — the daily work that currently runs on registers and scattered SMS.
Buy first, build when it matters.
We will point you to an off-the-shelf product if it fits. Genuinely.
A system nobody uses is worse than the registers it replaced.
That is why every school project includes data migration (your records arrive clean, with history intact), role-based training for office staff and teachers, and a parallel-run period before cutover. Screens are shown and approved before any code is written. Admissions season starts around December for the April session — the institutes that fix their follow-up in autumn walk into the season with a system that already works.
Common questions.
Should we buy a ready-made school ERP instead?
Maybe — and we will say so. Established products publish their prices openly (for example, Fedena lists annual plans at $999–$1,699 per year on its own pricing page, checked November 2026). If your fee structure and reports fit their boxes, buy it. We build when the product cannot bend to how your institute actually works.
What does it cost with Codeloom?
A school portal — admissions page, enquiry tracking, fee reminders, staff and student logins — starts at ₹45,000. The first ERP module (fees, attendance, results) starts at ₹60,000. Data migration and staff training are part of the quote, not extras.
Will our staff actually use it?
That is a design question, not a training question. We build screens around how your office already works, show every screen before the build, and train staff until they are comfortable. Most people are fluent within a few days because the system speaks their language.
What about our existing records?
We migrate them. Registers, spreadsheets and old software exports are cleaned up and imported, so you start with your history intact. Migration is planned in the first phase and tested before cutover.
Map your admissions journey.
Bhagat Ki Kothi, Jodhpur, Rajasthan 342001