How Much Does Private School Software Cost in 2026?

The bands a school network build falls into

The first release band is $60,000 to $130,000 over 12 to 16 weeks. For a school network that almost always means the household data model, a unified family ledger that computes what a household owes net of every award across every campus, and the admissions funnel, with your existing billing processor and student information system still in place and connected.

The full platform band is $150,000 to $400,000 phased over 6 to 12 months. That is where you take over the student information layer itself and run scheduling, gradebook, attendance and the parent portal on software you own, rather than layering on top of Blackbaud or Veracross.

There is a narrower piece worth pricing separately. The household ledger alone, with effective dated enrollment records, sibling tiers, staff remission and split billing allocations, plus deterministic recalculation on a mid year transfer or withdrawal, runs $32,000 to $55,000 over seven to nine weeks. For a network whose only acute problem is that nobody can answer what a family owes today, that is the proportionate fix and it retires the reconciliation spreadsheet on its own.

What drives a school network build up

Distinct tuition and fee schedules are the first driver. Each schedule brings its own rates, its own fee bundles, its own payment plan options and its own interaction with sibling and remission rules. Networks that grew through acquisition carry grandfathered schedules that must remain correct for existing families while new families join the current one, which means the ledger has to be effective dated by household as well as by year.

Historical data migration is the second, and it is the line item vendors most reliably lowball. Ten years of Rediker or a legacy Blackbaud instance with inconsistent household linkage runs $15,000 to $35,000 on its own. The time goes into reconciling sibling and guardian relationships, because legacy systems stored those differently across years and every mismatch needs someone at your school who knows the families to resolve it.

Financial aid volume is the third. A network with 15 percent of families on aid and a straightforward methodology is contained work. One reviewing 300 aid files a year with document extraction, committee override capture and versioned award rationale is a distinct module with a distinct budget.

Integration count is the fourth. FACTS, Clarity, your accounting system, Google Workspace or Microsoft 365 for rostering and a payment processor each add real weeks, and each has its own authentication and pagination behaviour.

Finally, if you accept state voucher or education savings account funds, the reporting obligations attached are neither optional nor small, and they need to be scoped explicitly rather than discovered in month five.

What keeps the number down

Keep the payment processor. FACTS or Blackbaud Tuition Management handles card and bank rails, payment plans and collections competently, and rebuilding that adds payments compliance scope you do not want. Own the ledger and the rules; let the processor collect the settled amount.

Keep the aid methodology if you are happy with it. Call Clarity or your existing provider, store the answer, and own the decision record with the override and its written reason. That is a fraction of the cost of rebuilding a methodology and it is the part that actually loses institutional memory today.

Model the household properly once rather than modelling four campuses thinly. Divorced guardians, split billing, three children across two campuses on three different award types is the test case. If the model handles that, the rest is configuration.

Migrate five years with full structure and keep older records as a searchable archive. Nobody needs an effective dated ledger reconstruction of 2014.

Cut over between cycles, not during one. A ledger that goes live in the middle of a billing month costs more in confusion than the weeks you save.

Protect internal capacity. Every project of ours that slipped in this category slipped because registrars could not give the team six focused hours a week. That is not a budget item but it is the single largest schedule risk.

A worked example that adds up

A four campus independent network, roughly 1,600 students, three tuition schedules because one campus was an acquisition, about 22 percent of families on aid, currently running Blackbaud Enrollment Management, FACTS for billing, Veracross as the student information system and ParentSquare for communication.

• Discovery, including writing down every sibling, remission and split billing rule as the business office actually applies it: $11,000
• Household aggregate with guardians, students, billing responsibility and custody attributes, all effective dated: $19,000
• Unified family ledger evaluating three tuition schedules, sibling tiers, remission and aid awards at invoice generation: $26,000
• Enrollment contract as an executable policy object, with refund schedule, deposit terms and tuition insurance interaction: $15,000
• Admissions funnel with timestamped stage events, conversion by campus and source, and a weekly forecast range: $18,000
• Integrations to FACTS for collection and Veracross for enrollment state: $13,000
• Migration of ten years of household, enrollment and billing history with relationship reconciliation: $22,000
• Testing, deployment and one parallel billing cycle: $11,000

That totals $135,000, marginally above the first release band because the migration is heavy and there are three schedules rather than one. A two campus network on a single schedule with five years of clean history lands nearer $74,000 on the same core.

Adding aid document extraction and committee workflow, the communication engine with custody aware audiences, and the parent portal takes the same network to roughly $215,000 to $270,000 in total.

How the spend phases

Discovery is three weeks and around 8 percent. The deliverable is your billing rules written down as they are applied rather than as they are documented, and in every network we have worked with those two differ. Get the business office and the registrars in the same room for that, because they usually disagree about what enrolled means.

The household model carries roughly 14 percent across weeks three to six and it gates everything, because no ledger, no audience and no forecast can be built until the household is a real object with effective dated relationships.

The ledger and the executable enrollment contract together are the largest block at around 30 percent, weeks five to thirteen. This is where the money is recovered, because it is what stops mid year transfers and withdrawals producing wrong invoices.

The admissions funnel is around 13 percent and runs largely in parallel, since it touches inquiry data rather than billing.

Migration is around 16 percent and it is the piece that slips. Reconciling household relationships needs your people, not just ours, so schedule it against your calendar rather than ours.

The remainder is integration, testing and parallel running.

The ongoing costs nobody quotes

Infrastructure runs $300 to $800 a month for a network of this size. Aid documents are the part that grows, because tax returns and supporting files are stored per family per year and they are retained.

Your payment processor fees do not change. You are not replacing FACTS, so its per transaction economics carry on exactly as before, and any proposal implying you will save that money is wrong.

Communication volume is per message once you are sending re-enrollment nudges, aid deadline reminders and billing notices from your own system rather than through a broadcast tool.

Annual schedule and policy updates are a recurring configuration cost. New tuition rates, a changed refund schedule or an amended remission policy each require somebody to version the rules and confirm that historical families still compute against the terms in force when they signed.

Support and enhancement typically runs 12 to 18 percent of the build cost annually in our delivery experience. Budget the heaviest support window around your enrollment and billing cycles rather than evenly across the year.

Comparing a build against your current renewal

Start with your actual software spend: the student information system, the enrollment management module, the aid platform, the communication tool and the billing processor. That is a real number and it is usually smaller than people expect for a network this size.

Then price what runs outside it. The hours the business office spends reconciling tuition against enrollment changes each month. The three staff and nine hours a single mid year campus transfer consumes. The days spent assembling a forecast the Director of Enrollment cannot produce from the tools. The audit findings each June where tuition was billed wrong, discounted twice or never invoiced after a mid year add.

That last one is the number to establish before you commission anything. Ask your auditor or your business manager for the total value of billing corrections in the last two closed years. If it is a few thousand dollars, your process is working and you should not build. If it is five figures annually, you now have a defensible input, and it sits alongside the payroll cost rather than replacing it.

Be honest that the subscriptions mostly continue. In the recommended architecture you keep FACTS and possibly your aid methodology, so the comparison is subscriptions plus build against subscriptions plus payroll plus correction losses.

When buying beats building

Buy if you run one or two campuses under about 800 students with a single tuition schedule and under 15 percent of families on aid. Veracross does this job well at that size, and the workarounds cost less than the build. We tell schools this regularly and it costs us work.

Buy if your pain is a process problem wearing a software costume. If three people at your school define enrolled differently, custom software will encode the disagreement and execute it faster.

Build when these arrive together: your business office spends 40 or more hours a month reconciling tuition to enrollment, you carry more than one billing entity or campus with different schedules, your annual audit surfaces five figures of billing errors, your Director of Enrollment cannot answer a forecast question without a two day export, and you have a chief operating officer or director of operations who can own product decisions week to week.

The tipping point is the multi campus household. The moment one family has children at two campuses on two schedules with two award types, no configuration screen in Blackbaud or Veracross expresses what they owe, and a spreadsheet becomes your real system of record. That spreadsheet is what you are paying to replace.

When the shortlist is down to two and you need a tiebreaker, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You can take that specification to any other firm on your shortlist.