Most nursery software looks capable during a demonstration. The screens are clean, the sample data behaves, and every feature gets its own tidy slide. The harder question is what happens on a busy Monday morning, when funded hours, a staff absence, a late payment and three parent messages all land within the same ten minutes.
That’s the gap this article is written to close. Not another feature list, but a way to test whether a system will hold up in your nursery specifically, once the demonstration conditions are gone. By the end, you’ll know what to ask a provider, what to test for yourself, and what a polished screen won’t tell you on its own.
Start with the problems you need to solve
Before you look at a single system, write down the problems you actually want solved. It sounds obvious, and it’s the step most owners skip, because a sales conversation is generally happy to start with features instead of your problems.
Group what you need into three honest categories: essential — things the nursery cannot run properly without, such as accurate invoicing, clear ratio visibility by room, and funding calculations that reflect your local arrangements and the way sessions are delivered; useful — improvements that would genuinely help, though you’ve managed without them before; and attractive but non-essential — features that look impressive in a demonstration but may rarely be used once the account is live.
A single-site nursery and a growing group will sort these differently. If you run one setting, reporting across multiple sites doesn’t belong near the top of your list, however well it’s presented. If you’re planning a second site within the next couple of years, it does.
Build your shortlist around real workflows
Feature lists describe what a system can do in principle. Workflows show you what it’s actually like to use on an ordinary day. Before you shortlist anyone, write down five or six real situations from your own nursery, and test every system against the same ones.
- Adding a child with a mix of funded and privately paid sessions.
- Handling a family on term-time-only or stretched funding.
- Changing a child’s booking pattern partway through the month.
- Recording a staff absence and seeing the effect on ratios straight away.
- Correcting an invoice that’s already gone out.
- Finding a parent’s full account history in under a minute.
- Onboarding a new starter, from contract to first shift.
- Pulling together what you’d need to show an inspector, without much warning.
- Comparing performance across two or more settings, if that applies to you.
You’re not trying to build an exhaustive catalogue of features. You’re trying to see whether the software fits the operation you actually run, not the tidy version a sales demonstration tends to assume.
Make the demonstration work for you
Most demonstrations are built to show a system at its best, which is reasonable enough, but it isn’t the same as showing you what you need to see. You’re entitled to steer at least part of it.
Before the call, send over two or three of your own workflows and ask the provider to complete them live, in front of you. Ask what happens when something goes slightly wrong — an incorrect entry, a late change, a form submitted half-finished — rather than only the clean version of each task. And ask for the person who’ll actually use the system day to day, your manager or administrator, to sit in. What looks straightforward to a salesperson isn’t always straightforward to the person keying it in every morning.
- Can you show me this with a mid-month change to a child’s funded hours?
- What happens if a form is submitted incomplete?
- How many steps does it take to correct an invoice after it’s sent?
- What does a manager see first thing on a Monday morning?
- Who do we call if something doesn’t look right, and how quickly do they usually respond?
A system that only looks good when everything goes to plan won’t tell you much about the mornings that don’t.
Look beyond the feature list
Some of the differences that matter most are the ones a feature list doesn’t capture. Worth checking, in plain terms rather than technical ones:
- Reliability and speed — does it lag when a whole room is checking children in at once?
- Ease of use — could a new starter use it confidently within a week, not only an experienced administrator?
- Permissions — can you control exactly what a room leader sees versus what an owner sees?
- Reporting — can you get the answer to a real question, such as which rooms are under capacity this month, without exporting to a spreadsheet first?
- Mobile and tablet use — does it hold up on the device your staff actually reach for?
- Product development — is the system still visibly improving, or has it looked the same for years?
- Support — when you call with a genuine problem, do you reach someone who understands nurseries, or a general help desk?
Ask a provider to show you, not just tell you, and judge it the way you’d judge anything else in your nursery: by whether it works on an ordinary day, not just a good one.
Examine how switching and onboarding are handled
This is the section owners underestimate most, and it’s often the real difference between software that succeeds and software that quietly gets worked around. A capable system can still struggle in practice if the move to it is left largely to you.
- Who manages the implementation — a named person, or a queue?
- What data is moved for you, and what will your team need to prepare or check beforehand?
- How are opening balances checked, and by whom, before go-live?
- How is your team trained — on your actual routines, or a generic walkthrough?
- Is go-live staged and supported, or a single date with no room either side of it?
- If something in the data turns out incomplete or wrong, who fixes it, and how?
- Realistically, how long should you allow for the whole move?
- Who do you call in the weeks just after launch, when questions come up that training didn’t cover?
A provider who can answer these clearly, and who treats the switch as their job to run rather than yours to get through, is telling you something useful about how they’ll behave once you’re a customer, not only while you’re a prospect. Our own approach to this is set out in full on the switching page, if it’s helpful to compare against.
Understand the true cost
Compare total value, not the headline price on its own. A lower monthly figure can still cost more once you add up what’s missing from it, and a higher one can be entirely fair once you see everything it includes.
Worth asking plainly: what’s included as standard, what’s optional, and what will your nursery still be doing by hand even after you’ve signed up? Factor in implementation charges, switching support, training, any optional modules and transaction fees on payments, alongside the time you’ll save and the errors you’ll stop absorbing. None of that means the cheapest option is poor value, or that the priciest is automatically better. It means the figure on the pricing page is rarely the one that actually matters.
Judge the company behind the software
Nursery software is a relationship, not a one-off purchase. You’re choosing who you’ll be calling in eighteen months, not just whose interface you preferred today.
Look for genuine sector understanding rather than a generic software pitch, a support team that understands the problem, not just the ticket, and a roadmap that’s still visibly moving. Ask what a provider will openly admit their system doesn’t do yet — one willing to say so is usually more trustworthy than one that claims to do everything. Speak to a customer running a setting similar to yours, if you can arrange it.
Nursery in a Box was built by people who ran nurseries themselves, which has shaped the perspective behind this checklist, but the test holds regardless of who you’re evaluating: does the provider understand your day well enough to have built for it, or only well enough to describe it convincingly? Ask hard enough questions and the difference tends to become obvious.
The operator’s checklist
A working version of everything above, organised for procurement rather than reading.
Before shortlisting
- List your essential, useful, and attractive-but-not-essential requirements separately.
- Note anything your growth plans over the next two to three years will genuinely require.
- Write down five or six real workflows from your own nursery to test every system against.
During demonstrations
- Bring your own workflows and ask the provider to complete them live.
- Ask what happens when something goes wrong, not only when it goes right.
- Have the manager or administrator who’ll use it daily sit in on the call.
Before signing
- Confirm what’s included as standard versus optional, and the total cost, not just the headline price.
- Ask who manages implementation, and get a named contact.
- Check permissions, reporting and support in plain terms, not technical ones.
Before switching
- Agree how your existing data will be checked and signed off before go-live.
- Confirm how and when your team will be trained.
- Ask what support looks like in the weeks immediately after launch.
The honest summary
The best choice is rarely the system with the longest feature list. It’s the one that fits the workflows you actually run, that your team can adopt confidently, that handles the complexity particular to your nursery accurately, and that comes with a provider who treats switching as their responsibility, not yours alone to manage.
Once you’ve been through a few demonstrations with your own scenarios in hand, the differences between providers tend to become obvious quickly — usually more quickly than the sales conversations suggest.
“Should we choose software based on the features we need now, or where we expect the nursery to be in three years?”
Neither on its own. Buying for a hypothetical future you can’t yet plan around usually means paying for capability you won’t use for years, if you use it at all. But choosing purely for today can leave you switching again just as you’re growing into a second site or a bigger team. The more useful test is whether a system handles your current workflows properly and has a credible path to the ones you’re likely to need — ask a provider directly what a growing nursery like yours typically adds, and how straightforward that tends to be.
If you’d like to go further on two of the topics that come up most in this decision, our guides to reducing daily admin and getting funded hours right both go into more detail than a checklist can.
One final thought
If two providers seem equally capable once the demonstration ends, the more useful question usually isn’t which system has more features. It’s which company would you rather still be working with in five years.
A useful demonstration should start with your nursery, not our feature list.
Bring your own requirements, your trickiest scenarios and your current frustrations — we’ll show you exactly how they work in Nursery in a Box.
Written by the Nursery in a Box team
Nursery in a Box was shaped by people with first-hand nursery experience. Our guidance reflects the operational pressures owners and managers deal with every day — staffing, funding, compliance and growth.
