For Schools

Is This Actually Worth It?

LittleLives

31 Mar 2026 — 4 min read

It’s the question behind almost every decision - but rarely answered properly.

Not because the numbers don’t exist. But because the right numbers aren’t being looked at.

Most school operators don’t struggle with understanding their numbers. They know what they’re charging, how much fees they should be collecting, and what their monthly costs look like. On paper, everything is there.

What’s harder to see is everything that doesn’t show up cleanly in a spreadsheet.

The 6-8 hours a week spent on billing and reconciliation. The lag between invoices sent and payments received. The quiet leakage: missed follow-ups, small errors, delayed collections - that never quite gets tracked, but is always felt.

Individually, none of these look like a big problem. Collectively, they add up to something much more expensive than most teams realize. And yet, when it comes to evaluating a new system, the focus immediately shifts to cost. Subscription fees are scrutinized. Line items are compared. Budgets are questioned.

But the existing inefficiencies? They’re treated as “part of operations”. Because when you’re evaluating a new system, the cost is very clear. It’s upfront, visible, easy to compare. But the return is harder to pin down. It’s not always obvious how much time you’re actually saving, or how much inefficiency you’re quietly absorbing today.

That’s where the gap is. Because when you actually start putting numbers to the current state, the conversation changes.

There’s another layer to this that doesn’t always get considered upfront. Not all systems are built with schools in mind. Some are adapted from more generic platforms, which can look cost-effective at the start.

The base price is lower, the features seem comparable, and on paper, the decision feels straightforward. But over time, the gaps start to show. Workflows don’t quite match how schools actually operate. Billing structures need adjustments. Reporting requirements evolve. What initially looked like a complete solution starts to require small changes - one after another.

And those changes rarely come for free. Customisations, additional modules, ongoing support requests - these costs tend to accumulate quietly in the background. More importantly, they slow teams down. Instead of having a system that works with them, teams end up working around the system.

That’s where the total cost of ownership starts to look very different from the original price. Because ROI isn’t just about what you pay upfront. It’s about how much time, effort, and additional cost is required to make the system actually work for your operations over time.

Take a fairly typical example.

A centre with around 120 students, running monthly billing manually. Between preparing invoices, tracking payments, sending reminders, and reconciling accounts, it’s not unusual for admin staff to spend 6-8 hours a week just keeping things in order.

Over a month, that’s roughly 25-30 hours. Over a year, close to 300 hours.

Even at a conservative estimate, say $12-15 per hour – that’s $3,600 to $4,500 a year spent on work that is largely repetitive. And that’s just time cost. It doesn’t yet account for:

Delayed payments affecting cash flow
Errors that require rework
The mental load of constantly needing to check and follow up

Now flip that.

If even half of that workload is reduced through automation - billing runs automatically, payments are tracked in one place, reminders go out without manual effort - you’re not just saving time. You’re reclaiming capacity. And that starts showing up much faster than most expect, often within the first few months.

You don’t need aggressive assumptions to see the shift. Even modest improvements, saving 5-7 hours per week, improving collection timelines, reducing manual handling - can translate into real, meaningful operational gains.

The problem is, most teams don’t quantify this properly.

So decisions get delayed, or deprioritized, or framed as “nice to have.”

Not because the value isn’t there, but because it’s tedious to piece together. They have to look at hours, workflows, edge cases, small inefficiencies that don’t always get documented.

And once it is, things tend to move quickly. Because then it’s no longer a question of “Is this expensive?” It becomes a much more practical question:

What are we continuing to pay for, every single month - by not fixing this?

That’s the role of a proper ROI view. Not to sell an outcome, but to make the current state clearer. To take what’s usually hidden: time, inefficiency, friction - and translate it into something tangible. Because once you can see it, you can’t really ignore it.

If you want a clearer picture, try mapping your own numbers.

A simple ROI calculator can help quantify: