Everything outside your licence tier is a scoped add-on on the same codebase. Each has its own tables and a fixed deliverable. Lead time assumes one developer: S ≤2 weeks · M 3–6 weeks · L 6–12 weeks.
The three features that define a modern school ERP for parents — shipped together.
Guardian accounts linked to one or more students; read-only attendance, marks, report cards, fees, notices and timetable, reusing the student pages. The single biggest parity win.
Flutter / React Native client over the existing API, published to both stores, with FCM push, biometric unlock and offline cache. Parent, student and teacher roles.
Razorpay / Cashfree / PayU on the existing fee structure — auto receipt, auto reconciliation to the collection ledger, webhooks and a refund trail. Retires the proof-upload flow.
Behind the current approval-gated notification engine. Templates for daily absentee alerts, fee dues, exam schedules and circulars; push via FCM.
Depth on the academic side and the platform layers a growing group needs.
Subject content library, assignments with rubrics, and a quiz / online-exam engine with a reusable question bank and auto-grading; optional Moodle roster and grade sync.
Enquiry → online application with document upload → application-fee payment → test / interview scheduling → offer letter → one-click convert to enrolled. Extends the reception pipeline.
Cohort performance trends, attendance-and-marks at-risk flags, OBE attainment, and a board-format report-card template library (CBSE / ICSE / State / IB).
Constraint solver over teacher availability, periods per week and room / lab limits; produces a draft grid the coordinator edits. Removes the manual / image workaround.
Google Workspace / Microsoft 365 SSO, Classroom / Meet provisioning, calendar sync, and a documented public API with tokens for third-party tools.
A tenant layer so a trust runs several schools on one deployment, with consolidated MIS, a shared staff pool and cross-campus reporting.
Self-contained modules a school adds when it needs them — each with its own admin screens, reports and permissions.
Salary structures, leave-linked payroll run, payslip PDF, PF / ESI / PT / TDS, loans and advances, and a bank-transfer file. Extends the staff and leave modules.
Routes, stops, vehicles, driver records, student–route allocation and a transport-fee tie-in. GPS tracking is the Tier-3 layer above.
A GPS-vendor feed or a self-hosted Traccar stack, with parent pickup / drop alerts. Sits on top of the Transport module.
Catalogue with ISBN import, member cards, issue / return, reservations, fines into the fee ledger, barcode support and stock audit.
Chart of accounts, expense entry with approvals, vendor payments, bank reconciliation and a Tally / GST-ready export — fee income and school spend in one system.
Template-driven TC, bonafide, character and fee-paid certificates with letterhead, a serial register and PDF output. Builds on the report-card PDF stack.
Cron-driven dues reminders on the WhatsApp / SMS channel, configurable late-fee slabs applied to the ledger, and an ageing report for the office.
eSSL / Matrix / ZKTeco device SDK writing straight into the attendance tables, with an optional gate-entry parent notification.
Room allocation, mess management, hostel attendance and leave / visitor passes.
Stock, issue and return, asset tagging, depreciation and purchase records.
Infirmary records, counselling notes and a behaviour-incident log with follow-ups.
Report-card comment drafting, a parent-facing FAQ / doubt bot over school data, timetable-clash explanation and fee-defaulter prediction.
Secrets to environment config, seeded passwords force-reset, debug & SQL artefacts stripped, audit log on, off-site nightly backups.
Import from spreadsheets or a prior ERP — students, staff, classes, fee history — with validation and exception reports.
Academic-year and rollover configuration, plus report-card templates matched to the school's board.
Admin and staff training sessions and hands-on support through the first reporting cycle.
One developer, roughly 9–12 months end to end. Add-ons are scoped and quoted individually, then built one or two at a time against a shared release train so the live system is never destabilised.
Parent app & portal + online payment gateway + WhatsApp / SMS, shipped together. ~8–12 weeks.
Highest visible impactCertificate generator + automated fee reminders & late fees. Reuse the PDF and messaging plumbing. ~3–4 weeks.
2 add-onsTransport (+ GPS), library, HR payroll, accounting ledger — in the order the school needs them. ~2–3 months.
Revenue-linked: transport, admissionsLMS / Moodle sync, admission CRM, analytics, timetable auto-generator, biometric, SSO — and the multi-branch console. ~3–4 months.
6+ add-onsName, email, position, number of students — that's it. We build your per-student quote on the spot and pick it up with you on WhatsApp.
