Admissions to alumni
Public application form, admissions register, placement and finalisation — an applicant becomes a student record without re-typing.
Case study · Chaitanya's Academy
One system for a two-campus residential academy.
Admissions, fees and online payments, attendance, hostel, gate and transport — one set of records, with apps for guardians, teachers, wardens and drivers. The admin work that used to fill the office's mornings now runs before anyone arrives.
- Client
- Chaitanya's Academy
- Sector
- Education
- Where
- Baramati & Nagar campuses, Maharashtra
- Built
- 2025 · 6-month build, then run by us
- Live at
- chaitanyasacademy.in
4,400+Students on the systemAcross the Baramati and Nagar campuses
95%Less admin timeWork that took hours now runs on its own
0Manual fee remindersEvery reminder is sent by the system
₹60 Cr+Payments processedEvery installment posted and reconciled
01 Before
The situation.
Paper-based records
Student records in physical registers — slow to find, easy to lose, impossible to analyse.
Fees chased by hand
Reminders forgotten, payments missed, and reconciliation taking hours every month.
Parents in the dark
No way to check attendance, fees or results without visiting the campus.
No numbers to decide with
No view of trends, at-risk students or where the money and time were going.
02 Built
What we built.
- React
- Node.js
- PostgreSQL
- Redis
- AWS
- Razorpay
Fees that reconcile themselves
Installment plans, payment links and gateway webhooks post every payment against the right installment.
The school day
Attendance in one screen, guardians notified of absences before first period ends, leave and substitution cover.
Hostel, gate and transport
Beds and hostel leave, gate passes and the visitor register, routes, drivers and vehicle compliance — on the same records.
A dashboard for the head
Fees collected, applications in flight, students on roll, hostel occupancy and fleet compliance in one load.
Access that refuses by default
15 roles, 92 permissions and an audit log on every change.
03 On screen
The system, as its users see it.
Running a school or academy? The full module list, the security model and monthly pricing are on one page.
See the school ERP“Lancehawks didn't just build us software — they took over our entire technology operations. We haven't thought about IT since.”
04 Timeline
Built, then run.
Launch was the halfway mark. We have run the system every month since.
Discovery 2 weeks
On-site with administration, teachers and accountants; workflows and pain points mapped before any code.
Design 3 weeks
Journeys for office staff, teachers, guardians, wardens and drivers; prototype tested with staff.
Build 14 weeks
Students, fees and attendance first; then hostel, gate, transport, payments and the dashboard.
Run Ongoing
Migration from paper, training, phased go-live — then monitoring and improvement every month.
Next step
What’s one job you’d hand to an agent tomorrow?
Bring it to a free 30-minute audit. We’ll tell you whether an agent should do it, what it would take and what it would cost — or that it shouldn’t.
30 minutes · free · no pitch deck