The console
The full system for office staff, heads, and managers. Admissions, fees, academics, hostel, transport, campus operations and administration — with navigation that hides whatever a person has no permission to see.
Lancehawks · Education operations platform
Admissions to alumni — fees, attendance, hostel, transport, gate, and the people who need to see it. Built for Indian schools and academies. Implemented and operated by us, so your staff never manage software.
In production
From the live system at Chaitanya’s Academy — Baramati and Nagar campuses.
The honest starting point
Nothing here is a criticism of how you work. It’s what happens when an institution grows faster than its tools. The office knows one number, the hostel knows another, and the only person who can reconcile them is on leave.
What that costs is rarely one big failure. It’s the slow tax — fees chased by phone, attendance copied twice, a parent who finds out about an absence at dinner, and a trustee asking for a number that takes three days to produce.
What it looks like in use
An ERP is really an institution’s clock. Here is one ordinary day on it.
On screen


The system
Not a menu of add-ons. One platform where admissions already knows about fees, fees already knows about the hostel, and the hostel already knows about the gate.
Who gets what
A guard should not be handed the same software as a finance officer. Everyone gets a surface built for the job they actually do — and sees only what their role permits.
The full system for office staff, heads, and managers. Admissions, fees, academics, hostel, transport, campus operations and administration — with navigation that hides whatever a person has no permission to see.
Students sign in with a roll number and PIN — no email needed. Attendance, fees, homework, timetable, notices and leave. Guardians see the same, per child. Teachers get their register, classes, and a compose screen for notices and homework.
The movement of people around a residential campus. Presence, residents, gate passes, exits, the visitor register, and maintenance issues raised with a photo from where the problem is.
Trips, daily logs and fuel entries from the driver's own phone, in their own language. Works with no signal and syncs when it returns — which matters on a route.
Why it can be trusted with student data
Every institution's data is separated at the application layer and again at the database layer. Two independent locks, not one.
15 roles and 92 distinct permissions. A warden sees their hostel. A class teacher sees their section. A guardian sees their own children. Access is checked on every single request, and defaults to refusing.
Every change — a mark amended, a fee waived, a pass approved — is written to an audit log with the person and the time, and is searchable. Disputes get resolved by looking, not arguing.
A class teacher can correct the same day. After that it takes a specific permission, and the correction is recorded. Approved leave marks a student excused automatically rather than someone remembering to.
Online payments post against the right installment automatically, through a verified gateway webhook. The ledger, the receipt and the bank settlement stay in agreement without anyone reconciling by hand.
No lock-in. Your records are yours: full export on demand, and on the way out a complete handover of your data with the documentation to go with it.
Lancehawks didn’t just build us software — they took over our entire technology operations. We haven’t thought about IT since.
How this works
The reason most school ERPs fail is not the software. It’s that somebody on your staff becomes responsible for it, and they already have a job. We keep that responsibility.
₹35,000 – ₹3,00,000per month
Depending on size, campuses and the modules you run. For most institutions that is less than a per-student licence plus the person you’d hire to run it.
We map how your institution actually runs, show you where the hours are going, and give you an honest answer on cost and timeline. If it isn’t a fit, we’ll say so.