School ERP for groups and trusts. Comparable numbers, finally.
A trust running four schools usually has four systems, four ways of counting, and a head office that spends the first week of every month turning them into one spreadsheet that nobody fully trusts.
- Go-live
- Next working day
- Price
- ₹49–₹199 per student per year
- Migration
- ₹0 — we do the extraction
- Pilot
- 90 days, pro-rata refund
- Structure
- One organisation, many campuses
- Rules
- Per-campus, where states differ
The reconciliation problem
The issue isn't that head office lacks data — it's that the four campuses count differently. One counts a student who left in August as enrolled for the year; another doesn't. One books a concession as reduced revenue, another as an expense. Comparing them is guesswork with a spreadsheet on top.
One system with one definition of a student, an invoice and a payment means the group's numbers are comparable because they're generated the same way, not because someone normalised them afterwards.
Same organisation, different rules
Campuses in different states face different fee regulations, and campuses on the same street may run different boards. A group structure that forces every campus into one configuration is unusable in practice.
Each campus keeps its own fee structure, board configuration, academic calendar, staff and approval chain. What the group shares is the organisation above them — one directory, one set of policies, one view across the lot.
What head office gets
- Collection, outstanding and enrolment across every campus, compared on the same definitions.
- Campus-level drill-down without asking a principal to prepare anything.
- Staff who work across campuses on one record rather than several.
- Transfers between campuses that carry the student's history rather than starting a new file.
- Group-wide communication where it makes sense, and campus-only where it doesn't.
- Role-based access, so a principal sees their campus and the trust sees everything.
Rolling out across campuses
Almost no group should move four schools on the same day. The usual approach is one campus first — normally the one with the most awkward fee structure, because if it survives that it will survive the others — and the rest at monthly intervals once the pattern is known.
Each campus goes live on a date it chooses, and the group view fills in as they arrive. There's no period where head office loses sight of the campuses still to move.
Frequently asked
What does Inkwelly cost?
₹49–₹199 per student per year, flat at any school size — no enrolment slabs and no per-module upsell. A 500-student school on the middle plan is about ₹49,500 a year. Migration, training and setup are ₹0. The only external costs are WhatsApp message fees and your payment gateway's transaction charge, both billed at cost.
Do all our campuses have to be configured the same way?
No, and they shouldn't be. Each keeps its own fee structure, boards, academic calendar and approval chain — which is necessary if they're in different states. What's shared is the organisation above them, and the definitions that make the numbers comparable.
Can we move campuses one at a time?
That's the recommended approach. Start with the campus that has the most awkward fee structure, then the rest at monthly intervals. The group view fills in as campuses arrive, so head office never loses sight of the ones still to move.
A student transfers between our campuses.
Their history moves with them — academic record, fee ledger, attendance and documents. They don't become a new student with a blank file, which is what happens when each campus runs its own system.
Our principals shouldn't see each other's numbers.
Access is role-based. A principal sees their campus, the trust sees everything, and finance sees what finance needs. It's configured per role rather than being all-or-nothing.
How quickly can we go live?
Go-live can be the next working day. You pick the date; we don't need months of parallel running to get there. Bringing across years of historical records — old marks, past fee ledgers, archived certificates — runs on its own track afterwards and doesn't hold up day one.
Where is our data, and can we get it out?
Hosted on AWS Mumbai. Daily encrypted backups, role-based access, and a full export in standard formats whenever you ask — including on the way out.
See Inkwelly on your school
30-minute demo. We open your current system with you and load your data into Inkwelly on the call. Dated go-live plan by the end of it.