The key points
- Modules and the number of branches shape cost more than the number of students.
- Integrations such as payment gateways, WhatsApp and biometric attendance each add scope.
- Migrating years of records from registers or spreadsheets is real work and must be priced.
- Ongoing costs, including hosting, support and per-student licences, matter as much as the first bill.
Which factors move the price most?
Scope is the largest factor. A school that needs only admissions, attendance and fees is a smaller build than one that also wants transport tracking, library, hostel and payroll. Each additional module has its own screens, rules and reports, and every school has a few unusual rules that take longer than the standard flow.
Scale comes next. A group with several branches needs consolidated reporting, shared student identities across campuses and permission levels that differ by branch. That structure is more work than a single school, even when the total student count is similar. Board-specific report-card formats, regional-language support and parent apps add further scope.
Why do integrations and data migration add cost?
Every integration connects your software to a system you do not control. A payment gateway, a WhatsApp messaging provider, a biometric or RFID attendance device and an accounting package each need setup, testing and handling for the case where the other system fails. Third-party fees for these services are separate from the build and continue after launch.
Migration is the item schools most often forget. Moving years of student records, fee ledgers and marks from registers or spreadsheets means cleaning duplicates, fixing inconsistent names and deciding what history to keep. Ask any vendor whether migration is included, how many years of data it covers and who checks the result.
How should you compare quotes and ongoing costs?
Two quotes are comparable only when they list the same modules, the same integrations and the same support period. Ask each supplier to state what is included, what is billed per student or per branch each year, who owns the source code and the data, and what happens if you leave. Our guide to comparing software quotes gives a longer checklist.
A licence charged per student can look cheap for a small school and become expensive as it grows, while a fixed-price custom build has a larger first cost and fewer recurring ones. Neither is always better; the right choice depends on how long you plan to use the system. Our school software pricing guide explains the cost drivers in more detail, and what custom software costs applies the same logic more broadly.
What to prepare before asking for a quote
- The modules you need now and the ones you may want later
- The number of branches and the approximate number of students
- Your fee structure, including concessions, sibling discounts and late fees
- Your report-card format and the board it follows
- Existing data to migrate and the form it is in
- The devices or services it must connect to, such as payment gateways or attendance readers
Sources
Rules and guidance this answer relies on. Policies change, so check the current version before acting on it.