Lancehawks School ERP · in production

One system that runs the whole institution.

Admissions to alumni — fees, attendance, hostel, transport, gate and the people who need to see it. Built for Indian schools and academies, implemented and run by us, with AI layered on wherever it earns its place.

For
Schools, academies and residential campuses
Scope
16 modules · 4 apps · multi-campus
Delivery
One monthly retainer — built, run and improved by Lancehawks
Reference
Chaitanya’s Academy — Baramati & Nagar campuses

What the live system holds today

4,400+Students on the live system
11,000+Admission applications on record
₹60 Cr+Payments processed
21,000+Fee installments tracked
1,350+Hostel beds across 6 hostels

From the live system at Chaitanya’s Academy — Baramati and Nagar campuses. Rounded down.

01 The honest starting point

Your institution already runs on a system. It’s just spread across registers, spreadsheets and six WhatsApp groups.

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.

02 In use

A Tuesday, on the system.

An ERP is really an institution’s clock. Here is one ordinary day on it.

  1. 07:40

    Security guard · Campus app

    Gate opens. Day scholars stream in; a parent arrives unannounced and is checked in against the visitor register with a photo, in about fifteen seconds.

  2. 08:15

    Class teacher · School app

    Attendance for the whole section is marked in one screen and submitted in a single tap. Guardians of absent students get a push notification before first period ends.

  3. 08:50

    Head of school · Console

    The morning dashboard, in one load: attendance today, which registers are still unmarked, dues outstanding, leave awaiting a decision, and which classes need a substitute teacher.

  4. 09:05

    Head of school · Console

    Two teachers are absent. Cover is assigned from the same screen, and it appears on the covering teachers' Today tab before they reach the staff room.

  5. 11:20

    Parent · Anywhere

    A father pays the second installment from a payment link on his phone. The receipt is instant, the ledger updates itself, and nobody in the office touches it.

  6. 14:00

    Admissions desk · Console

    An application that came in through the public form is placed into a class, quoted a fee, and finalised. The applicant becomes a student record — and if they need accommodation, they land in the hostel's Needs a Bed queue automatically.

  7. 16:30

    Warden → Guard · Campus app

    A hostel student is approved to go home for a wedding. The warden issues a gate pass; the guard marks the student out at the gate and back in on Sunday. The hostel leave register and the gate log are the same record — they cannot disagree.

  8. 18:00

    Transport office · Console

    Drivers submit the day's logs from their own app. A vehicle's insurance is expiring in eleven days, so it is already on the compliance digest that went out this morning.

  9. Any time

    Trustee · Console

    Every one of those actions is in the audit log, with who did it and when. Nothing above required a phone call to find out.

03 On screen

The console your office would use.

The head of school's dashboard, showing fees collected, applications, students on the roll, hostel occupancy and fleet compliance
Console · Head of schoolThe morning dashboard. Fees collected, applications in flight, students on the roll, hostel occupancy and fleet compliance — one screen, one load.
The admissions application register, with counts for applications, entrance forms, scholarship forms and students admitted, above a filterable list
Console · Admissions deskThe admissions register. Every application across entrance and scholarship forms — filtered by year, campus, class and status, and exportable whenever the office asks.

04 The system

Sixteen modules, grouped the way you’d think about them.

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.

01

Admissions & enrolment

  • Public application form
  • Enquiries & leads
  • Application register
  • Entrance & scholarship forms
  • Concessions
  • Admission fee
  • Placement & finalisation
  • CSV export
02

Students & families

  • Directory & profiles
  • Guardians
  • Sibling de-duplication
  • Document vault
  • Teacher remarks
  • Transfer & withdrawal
  • Year-end promotion
03

Fees

  • Fee structures
  • Installment plans
  • Per-student ledger
  • Concessions, waivers & fines
  • Offline collection
  • Receipts
04

Payments

  • Razorpay payment links
  • Online collection
  • Automatic reconciliation
  • Settlement tracking
  • Multiple bank accounts
  • Refund handling
05

The school day

  • Classes, sections & subjects
  • Timetable
  • Daily attendance
  • Homework
  • Notices
  • Student leave
  • Substitution cover
06

Hostel

  • Floors, rooms & beds
  • Floor plan & vacancy
  • Allocation & transfer
  • Check-in / check-out
  • Needs a Bed queue
  • Hostel leave
  • Occupancy analytics
07

Gate & campus movement

  • Gate passes
  • Visitor register with photo
  • Pre-registered visitors
  • Who is on campus now
  • Exit & return logging
  • CSV exports
08

Transport

  • Vehicles & drivers
  • Routes & stops
  • Trips
  • Daily & fuel logs
  • Maintenance
  • Insurance / PUC / fitness expiry
  • Monthly reports
09

Facility maintenance

  • Tickets by area & priority
  • Photo attachments
  • Threaded updates
  • Status workflow
10

Library

  • Catalogue & copies
  • Issue & return
  • Reservations
  • Fines
  • Member cards
  • Stock audit
11

Inventory

  • Items & categories
  • Stock in / out
  • Issue to departments
  • Vendors & purchases
  • Low-stock alerts
  • Asset register
12

Oversight & control

  • Head's dashboard
  • Staff directory
  • 15 roles, 92 permissions
  • Departments
  • Full audit log
  • Multi-campus

05 Who gets what

One console. Three apps. Nine kinds of people.

A guard should not be handed the same software as a finance officer. Everyone gets a surface built for their job — and sees only what their role permits.

Office · Web

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.

Students · Guardians · Teachers

School app

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.

Wardens · Guards · Reception

Campus app

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.

Drivers

Driver app

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.

06 The AI layer

Records first. Then agents on top.

Because every admission, fee and attendance mark lives in one place, agents can act on it safely. These are optional — we add them when they earn their place, with the office approving anything that reaches a family.

How we build agents
  • Fee follow-up agent

    Checks who has already paid, drafts reminders in each guardian’s language and sends them once the office approves.

  • Admissions desk

    Answers enquiries overnight from your prospectus and fee structure, books counselling slots and hands warm leads to the office.

  • Ask the ERP

    The head of school asks “which sections have attendance under 85% this month?” and gets the answer with the numbers behind it.

  • Document intake

    Birth certificates, transfer certificates and marksheets read and checked against the application before anyone opens them.

07 Trust

Built like the records matter.

Ready for the DPDP Act conversation

India's Digital Personal Data Protection Act puts extra duties on anyone who handles children's data, and a school handles little else. Role-scoped access, a searchable audit trail and a full export on request mean that when a parent, a trustee or an auditor asks who saw what, you can show them.

Your data is isolated twice over

Every institution's data is separated at the application layer and again at the database layer. Two independent locks, not one.

Permission on every action

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.

Everything is on the record

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.

Attendance can't be quietly rewritten

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.

Money reconciles itself

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.

It is your data

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.”
Sujay Saha · Head of Product Development, Chaitanya’s Academy

08 Commercials

You don’t buy software. You get a team that runs it.

Most school ERPs fail not because of the software, but because someone on your staff becomes responsible for it — and they already have a job. We keep that responsibility.

₹35,000 – ₹3,00,000 per 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.

  • Commercials

    One monthly retainer. Implementation, operations, maintenance and improvements included.

  • Not charged

    No per-seat licensing, no project fee, no change-request billing, no surprise invoices.

  • Getting started

    Typically one to two weeks from first conversation to kickoff.

  • Leaving

    No lock-in. Cancel at the end of any cycle and leave with a full export of your data.

  • Support

    Monitoring included. Critical issues get a response in hours, not days.

  • Your existing records

    Students, applications and fee history come across with you, checked and balanced before you go live.

Next step

Start with a free 30-minute audit.

We map how your institution actually runs, show you where the hours go, and give you an honest answer on cost and timeline. If it isn’t a fit, we’ll say so.

30 minutes · free · no pitch deck

WhatsApp