Licensing
Schoolyi uses quote-based licensing rather than fixed public tiers. Tell us your school size, campuses, boards, and first-phase modules so we can explain the scope, assumptions, implementation work, and support behind the quote.
Compare vendors with our software comparison guide or explore fees and finance workflows before reading about ERP for small schools.
Quote clarity
A quote should separate recurring licensing from implementation work and third-party costs. We will identify the assumptions before you compare proposals.
Licensing approach
School ERP is not a self-serve SaaS tier list. Licensing follows your rollout, modules adopted, school size, and boards served.
Licensing reflects size, boards, and launch modules, expand when more teams come on board, not before.
Start with admissions and fees. Add academics and HR when ready. Roles gate modules from day one.
Replace spreadsheets and point solutions with connected records, fewer integrations, fewer reconciliation Fridays.
We quote after understanding your workflows. Public pricing pages with three fake tiers rarely match how schools actually adopt software.
Focused demos on your priority modules precede licensing. Pilots align to phase-one admissions, roster, and fees when data is ready.
Add timetable, exams, payroll, and operations in later terms. Licensing grows with adopted modules, not a forced all-in bundle.
What shapes the quote
A useful proposal shows what is included, what is phased, and which assumptions still need confirmation.
Student and staff volume, campuses, boards, academic calendar, and the teams that need access.
Choose the workflows that need to work first, such as admissions, roster, fees, attendance, or exams.
Data cleanup, migration, integrations, training, support coverage, and any deployment-specific controls.
Total cost of ownership
When you evaluate school management software pricing, record the one-time, recurring, usage-based, and internal costs that affect the decision.
This is the practical way to assess school management system cost and school software implementation cost without mistaking an incomplete quote for a lower total cost. Use the implementation guide and trust and procurement guidance to ask who owns each dependency, what evidence is required, and how the school can export or review its data later.
Illustrative scope
A quote becomes easier to evaluate when it names the campus, users, workflows, dependencies, exclusions, and acceptance checks. The example below is a planning pattern, not a promise or a fixed package.
Cost drivers
Useful mainly because two of these are the opposite of what schools expect, and budgeting against the wrong driver is how a business case comes apart at the second meeting.
The primary driver, because it scales the licence and the support load together. It is also the figure most often quoted loosely: quote enrolled students, not capacity, and say whether you are counting the current year or the one you are planning for.
A phase-one of admissions and fees is a different agreement from the full platform including payroll, boarding, and transport. Licensing follows what you adopt, which means a narrow first phase costs less and a later expansion is a change rather than a renegotiation.
Each campus adds configuration, roles, and reporting boundaries. Two campuses sharing one roster and one finance function is closer to one school than two; two operating independently is closer to two agreements.
The largest variable one-time cost, and the one most sensitive to the state of your existing data. A clean export from a structured system is a fraction of the work of reconciling several spreadsheets with disputed opening balances. This is why the data-readiness worksheet changes your quote.
Driven by staff numbers and how much of the training your own team can deliver. A school with a capable internal owner who trains teachers themselves pays less here than one that wants every session delivered.
Managed hosting, a specific data region, or an on-premise deployment carry different infrastructure and operational costs. Ask for this to be itemised rather than absorbed, because it is the line most likely to change if your regulatory position changes.
Standard business-hours support and extended coverage during a fee deadline or reporting week are different commitments. Decide which weeks of your year actually need the higher tier rather than buying it for all of them.
Schools expect this to be expensive and it usually is not. Configuring a second grading model and reporting template is real work but it is bounded, one-time, and does not scale with enrolment. It affects implementation, barely the licence.
Teachers and office staff are not separately licensed per seat, so adding an administrator or a covering teacher is not a commercial event. If another vendor prices per user, normalise for that before comparing.
Ten years of historical academic records is a migration question, not a storage cost. Document attachments at scale can matter; ordinary school record volumes do not.
Worked examples
What phase one contains for three recognisable school profiles, what shapes the cost for each, and what the school supplies itself. No figures, because a figure without your data would be a guess.
Around 600 students, one national curriculum, records in spreadsheets, tuition collected in cash and bank transfer.
What shapes the cost: Migration is the swing factor rather than the licence. Spreadsheet sources mean duplicate reconciliation and disputed opening balances, and the state of that data can change the one-time cost more than the student count changes the recurring one.
Around 1,200 students, two curricula with different assessment models, tuition billed in local currency, an incumbent system in place.
What shapes the cost: The second curriculum adds bounded, one-time configuration work in assessment and reporting rather than a recurring premium. Enrolment drives the licence; curriculum count drives implementation. Extraction from the incumbent is the risk to price for, since what it will release is not known until asked formally.
Three campuses, shared finance function, separate rosters. Read the limits first: this is a partial fit, and if consolidated group reporting is a hard requirement it is not one we meet.
What shapes the cost: Campus count is a strong driver because each one adds configuration, roles, and reporting boundaries. The cost falls sharply if the campuses accept a shared configuration and rises if each keeps its own conventions. That decision is governance, not software, and it should be made before the quote. Budget separately for whoever assembles group reporting from per-campus exports each month, because the product will not do it for you.
Build the internal case with the ROI calculator, which computes from your own figures rather than ours, and take the RFP and data-readiness templates to every vendor on your shortlist.
Assumptions register
Ask every vendor, including us. A proposal that leaves these unstated is not cheaper than one that states them; it is less finished.
A licence quoted against 600 students and one quoted against capacity for 800 are not comparable, and the difference will not be visible in the total.
Ask: Which enrolment figure is this priced against, and what happens when we exceed it mid-year?
The commonest source of a misleading comparison is a quote that covers a narrower set of workflows than the school assumed, discovered when a workflow turns out to be a separate line.
Ask: List every module included, and every module needed for the workflows in our requirements that is not included.
Migration priced as a fixed line usually has exclusions. The exclusions are where the second invoice comes from.
Ask: What data will you migrate, what will you not, and what happens if our data is worse than assumed?
Somebody deduplicates the guardian records. If the quote assumes the school does it and the school assumes the vendor does, the project stalls in week two.
Ask: Is data cleaning in scope, and if so whose staff perform it?
Training quoted as a lump sum can mean two administrator sessions or every teacher trained. Both are legitimate; they are not the same purchase.
Ask: How many sessions, for which roles, delivered how, and what does a repeat session cost?
Payment gateway fees, SMS charges, and domain costs are billed by those providers. A quote that appears to include them and does not, or excludes them without saying so, distorts the comparison.
Ask: Which costs in this rollout will be billed to us by someone other than you?
The number that matters over five years is the renewal, not the first year. A first-year discount against an unstated renewal is a common structure and a poor basis for a decision.
Ask: What is the renewal price, how is it adjusted, and what happens when enrolment grows by a hundred students?
What you can extract, in what format, and within what notice period. This costs nothing to state up front and is expensive to discover later.
Ask: On termination, what do we receive, in what format, and how long do you retain our data afterwards?
Comparing proposals
Six steps that make two proposals answer the same question. They work regardless of which vendors you are comparing, and they work against us.
Add first-year cost plus four renewals, including any stated escalation. A first-year discount against a higher renewal is a common structure and it inverts many comparisons.
Migration, configuration, and training are one-time; licence and support recur. A quote that bundles them looks cheaper in year one and is harder to compare in year three.
Gateway fees, SMS charges, your own staff time, and any hardware. These are identical across vendors only if the platforms need the same amount of manual work, which they do not.
List the workflows in your requirements and mark which quote covers each. Then price the gaps. Two quotes for different scopes are two answers to different questions.
If one vendor licenses per user and another does not, project your staff count over the term. A per-user model is often cheaper at signature and more expensive by the third year.
What you can extract and in what format. This has no line on either quote and is the cost you pay if the decision turns out to be wrong.
What this page does not do
Every one of these is a decision rather than an oversight, and the reasoning is given so you can disagree with it.
Not as a sales tactic, but because the honest range for a school ERP across the school sizes, campus counts, module scopes, and migration conditions we work with is wide enough that publishing it would tell you nothing you could plan against. A figure you cannot rely on is worse than no figure.
There is no permanently free plan. Where you see school software offered free, it is usually open-source software you host and maintain yourself, which is a real option with a real cost in staff time rather than licence fees.
A quote needs your enrolment, campus count, module scope, and data condition. Anything produced without those is a guess, and a guess presented as a quote is how procurement processes get restarted three weeks in.
We do not know what another vendor will quote you, and any platform can be configured into being the cheaper option for some school. Where a competitor is genuinely lower-cost for your situation, our comparison pages say so.
Get a quote
Request pricing after a walkthrough on admissions, fees, or exams. This sequence gives principals and bursars a clear scope to review before a licensing decision.
Tell us student count, curriculum mix, and which modules must go live first, admissions, fees, exams, or full ERP.
We demo live screens on your list: apply and track, fee receipts, timetable, or exam publish gates, not generic slides.
Licensing matches rollout scope and school size. You expand modules in later terms without renegotiating from scratch.
Most schools start calendar, roster, and fees in weeks when data is ready. Academic and HR modules follow as teams are trained.
Straight answers about Schoolyi licensing and rollout.
Licensing matches school size, boards, and launch modules. We quote after understanding your rollout, rather than publish a one-size-fits-all tier list.
That lets buyers compare school management software on the scope they will actually use.
Yes. Most schools begin with admissions, roster, and fees, then add timetable, exams, HR, and operations in later terms.
The right starting point depends on the workflow costing your team the most time, not on buying every module on day one.
Platform access to scoped modules, role based access for staff and families, public admissions flows, onboarding guidance, and rollout support.
Confirm which implementation tasks, data migration steps, and support response expectations are included in the proposal.
We run focused walkthroughs and scoped pilots. Contact us with size and priority modules, and we propose a rollout plan rather than a generic trial.
A realistic pilot should use the school workflows you will need to trust first.
A quote depends on school size, campuses, boards, users, modules, rollout phase, data migration, integrations, support coverage, and deployment requirements.
Ask for those assumptions in writing so a school ERP comparison reflects the full cost of going live.
Yes. Migration, configuration, training, integrations, support coverage, and deployment needs depend on your starting data, workflows, systems, and rollout scope.
We identify these assumptions before proposal approval so the best platform for schools is judged on implementation fit, not only licence price.
Compare the same modules, users, campuses, implementation work, integrations, support, renewal assumptions, internal effort, and exit responsibilities, not only the headline license.
The best ERP for schools is the one whose complete operating scope matches the work your teams actually need to run.
Schoolyi is a web application. Staff, teachers, and families sign in through a browser with role based access, with no desktop install for day to day work.
That makes it a practical school management system for teams working across campus and at home.
Yes, most schools start with admissions, roster, and fees, then add timetable, exams, HR, and operations when teams are ready.
Roles gate modules from day one, so a phased school ERP rollout does not expose unfinished workflows to every user.
Guardians use a parent portal for fees, receipts, published grades, and attendance.
Public admissions apply and track pages cut status calls before enrollment, giving families a clearer path from application to everyday school communication.
Share your school profile and first-phase workflows. We will discuss scope, assumptions, implementation needs, and the next decision step.
Already using Schoolyi? Sign in
