Running an early years setting in the UK means holding a lot of moving parts together: attendance registers, child and family records, observations against the EYFS, funded-hours claims, fee invoicing, staff ratios and the audit trail Ofsted will want to see. Most off-the-shelf childcare software makes you bend your routines to fit how the software thinks a nursery should work. We do it the other way round. At ByteGears we build nursery management systems around the way your setting already runs.
There are no monthly per-child fees and no features locked behind a higher tier. You own the software, and you work directly with our UK-based team to shape it. As your setting grows, adds rooms or takes on new sites, the system grows with it.
To be clear about where this fits: if you run a single nursery with a fairly standard fee structure, a product like Famly, Tapestry or Cheqdin will usually do the job, and we’ll tell you so. A custom build pays off when standard tools start working against you, which is what the rest of this page is about.
Where off-the-shelf nursery software falls short
The established childcare platforms are competent products. The trouble is the things they all struggle with tend to be the things that matter most once a setting becomes anything other than simple:
- Billing that can’t model your fees. Per-child pricing and standard invoice templates don’t reflect part-time and full-time sessions, age-banded rates, sibling discounts, or 15 and 30 hours funded childcare with the variation each local authority adds. Settings end up exporting invoices and fixing them in a spreadsheet.
- Ofsted and safeguarding gaps. EYFS frameworks are supported, but inspectors still ask questions the software can’t answer cleanly: who accessed a record and when, whether observations are granular enough, whether DBS and training expiry dates were flagged in time.
- Per-child and per-user pricing that climbs. The cost rises as you enrol more children, and some platforms charge per staff member, so giving every educator proper access becomes a budget decision rather than an obvious one.
- Rigid workflows. Custom approval steps, extended-care charges after 6pm, drop-in attendance or a Montessori observation method rarely fit the standard templates.
- Integrations that aren’t really integrations. “Xero integration” often means a CSV export you import by hand, with payments that don’t reconcile against invoices and payroll that doesn’t pull hours from attendance.
- Slow customisation and vendor lock-in. Tier-2 changes get routed to professional services billed by the hour, proprietary data formats make leaving expensive, and price rises land whether you like them or not.
The result is wasted manager and finance hours, parallel paper records staff secretly trust more, and money spent on features nobody uses. A bespoke build starts from what your setting needs rather than what a vendor decided to ship.
When a custom build is the right call
Bespoke isn’t for every setting. It earns its place when:
- You run a group of five or more sites with billing or workflows that differ between them, and consolidated reporting has become a manual job.
- Your fee model is genuinely complex: age-banded rates, sliding-scale subsidies, funded-hours variance by local authority, custom discount and add-on rules.
- Compliance is non-negotiable in a way standard tools don’t cover, such as detailed funding-audit trails or unusual safeguarding requirements.
- You need real two-way integration with Xero, Sage or a back-office system, not CSV exports.
- You’re growing fast or acquiring settings and need one platform instead of inherited legacy systems.
- You want to own your data model and stop worrying about vendor price rises and lock-in.
If none of that sounds like you, off-the-shelf is probably the better value, and an honest first conversation will tell you which side of the line you’re on.
What working with ByteGears looks like
When a custom build does make sense, here is how we approach it:
We map your routines first. Before any code gets written, we document how your setting actually runs: room structure, session types, fee rules, observation methods and the points where the current process breaks. The software supports those routines rather than breaking them.
You pay once. Instead of a per-child subscription that grows with you, you get software you own. The trade is an upfront cost against years of recurring fees, setup charges and paid support escalations.
It connects properly to your other tools. We build real integrations with accounting (Xero, Sage, QuickBooks), payment collection (GoCardless, Stripe), payroll, and SMS or email for parent messaging, so invoices and payments reconcile automatically.
UK rules are part of the build. EYFS observation tracking, Ofsted-ready audit trails, staff-to-child ratio monitoring and UK GDPR handling are designed in from the start, not bolted on later.
It grows in stages. We launch a working core early, then add modules such as learning journals, online payments, occupancy forecasting or staff certification tracking as you need them.
Support comes from the UK. When you need help, you reach the team that built your system, during UK business hours. No overseas call centres, no waiting for a timezone to wake up.
Features we build into nursery systems
We start with a core that every setting needs and add the rest to suit yours:
Child and family records holding date of birth, allergies, medical and dietary notes, emergency contacts and consent flags for photos, observation sharing and funding, all in one place.
Attendance and check-in with contemporaneous, real-time registers that can’t be backdated, ready for funding claims and inspection.
A billing engine built for your fees that handles age bands, part-time and drop-in sessions, sibling discounts, extended-care charges, meal and nappy add-ons, and 15 and 30 hours funded childcare with local authority variance, then reconciles funded hours against invoices.
Learning journals and observations linked to EYFS areas of learning, with photos, parent sharing and the statutory progress checks at age two and at five.
Staff management covering rotas, room assignment, qualification and DBS records, training-expiry alerts and payroll export.
Real-time ratio monitoring that flags when staff-to-child ratios slip below the legal thresholds for under-twos, two to three year-olds and over-threes.
Safeguarding and incident logging with accident, medication and consent records, and a tamper-evident audit trail showing who accessed what and when.
Parent communication through secure messaging, daily updates, fee reminders and digital permission slips.
Occupancy and finance dashboards showing room capacity, forecast occupancy, invoice ageing and funding reconciliation.
Mobile and tablet access designed for room leaders working with a tablet while supervising children, not an office desk.
Custom reports for local authority funding submissions, Ofsted inspections and your own management reviews.
For a multi-site group, a central dashboard sits on top, giving head office a real-time view of occupancy, billing and staffing across every setting with the ability to drill into any one of them.
How a project runs
We work in four phases:
1. Discovery and planning (2-4 weeks). Workshops with managers, room leaders and your finance person to document how you work now, your fee and funding rules, where the pain points are, and what the first release has to cover.
2. Development (8-16 weeks). Our UK developers build it, with regular working demos so you see progress and steer it. We deliberately ship a usable core before adding the rest.
3. Testing and rollout (2-4 weeks). Thorough testing, data migration and staff training before go-live. For multi-site groups we pilot at one site, refine, then roll out to the others.
4. Training and support. Room leaders trained on attendance and observations, managers on billing, reporting and compliance, with written and video guides and three months of support included.
A focused first release for a single setting usually runs around 8 to 12 weeks. A multi-site group with funded-hours billing, Xero integration and full EYFS observations is more often 12 to 16 weeks or longer. Two things are worth planning for: cleaning up messy data before migration, and bringing staff and parents along gradually rather than switching everything off overnight. Most failed rollouts trace back to one of those, so we build the plan around them.
What it costs
A custom build is an upfront cost rather than a recurring one, so the honest comparison is total cost of ownership over several years, not month one against month one.
- You pay once and own it, instead of a per-child subscription that climbs as you enrol more children and add sites.
- SaaS quotes rarely tell the whole story. Setup and onboarding, data migration, paid integrations and tier-2 support charged by the hour all sit on top, and annual price rises compound.
- For a single nursery, a focused first release is usually in the low tens of thousands. A multi-site system with flexible billing, funding handling and EYFS observations costs more, scaling with the number of sites and the complexity of your fees.
- Software shaped around how your team actually works gets used. Generic tools often end up running alongside the spreadsheets they were meant to replace.
We give you a fixed scope and a clear price once we understand what you need. We won’t pretend bespoke is cheaper for every setting, and if an off-the-shelf product is genuinely the better value for you, we’ll say so. The first consultation is free and is mostly about working out whether a custom build is the right call at all.
Who we build these for
Nursery chains and groups. Five or more sites usually means fragmented operations, billing that drifts between settings and a slow, manual job to prove compliance across the group. A central dashboard with consolidated reporting, drill-down to any site and a shared data model is where bespoke earns its keep.
Integrated early education providers running nursery, pre-school and after-school under one roof, juggling several age groups, flexible session types and a funding mix of government, private and subsidised places that standard billing struggles to model.
Settings with genuinely complex fees. If you invoice fifty children on thirty different rates, with funded hours, sibling discounts and add-ons, a billing engine built around your model removes the spreadsheet step that off-the-shelf tools force on you.
Montessori, Reggio and Waldorf-inspired settings whose observation methodology doesn’t fit generic EYFS templates and want a portfolio and observation framework that reflects how they actually assess children.
Groups growing through acquisition that have inherited a mix of legacy systems and need one platform fast, rather than re-implementing per setting.
Local authority and council-run provision with their own reporting lines and funding processes that don’t match a commercial vendor’s template.
For a single site with a fairly standard fee structure, an established product is often the better fit. Each bespoke build keeps the same compliant core and adds whatever your particular setting needs on top.
Common Questions About Custom Nursery Management Systems
Is a custom system worth it, or should we just use Famly or Connect Childcare?
For a single site with a standard fee structure, an off-the-shelf product like Famly, Tapestry or Cheqdin is often the sensible choice, and we'll say so. A custom build earns its keep when standard tools start to fight you: multi-site groups with different billing across sites, age-banded and funded-hour pricing the software can't model, audit trails that don't satisfy Ofsted, or integrations you keep doing by hand. If that's you, this is worth a conversation.
How does the cost compare to a SaaS subscription?
Per-child SaaS pricing is cheap for a small setting but climbs as you grow and as sites are added, before you count setup, data migration, paid integrations and tier-2 support charged by the hour. A custom build is an upfront cost instead of a recurring one. For a single nursery a focused first version is usually in the low tens of thousands; multi-site systems with flexible billing and funding handling cost more. We give you a fixed scope and price after the first conversation.
What's the typical development timeline?
A focused first release for a single setting usually takes around 8 to 12 weeks. A multi-site group with Xero integration, funded-hours billing and EYFS observations is more often 12 to 16 weeks or longer. We launch a working core early and add modules in stages rather than going live with everything at once.
Can you handle funded hours and complex fee structures?
Yes, and this is usually the main reason settings come to us. We build the billing engine around your actual model: 15 and 30 hours funded childcare, age-banded fees, part-time and drop-in sessions, sibling discounts, extended-care charges and add-ons like meals or nappies. Funding rules vary by local authority, so the system is built to reconcile claims rather than force everything into a generic template.
Can you integrate with our existing systems?
Yes. Common integrations are accounting (Xero, Sage, QuickBooks), payment collection (GoCardless, Stripe), payroll, and SMS or email for parent messaging. We build proper two-way connections where it matters, so invoices and payments reconcile automatically instead of moving through manual CSV exports.
How do you handle EYFS, Ofsted and data protection?
The system is built around the EYFS framework, with observations linked to areas of learning and progress checks at age two and at five. Safeguarding and incident logging, staff DBS and training expiry alerts, and real-time staff-to-child ratio monitoring are designed in, with a tamper-evident audit trail for inspections. Data handling follows UK GDPR and ICO guidance, with UK-hosted options and consent management for photos and record sharing.
Do you provide training and support after launch?
Yes. We train room leaders on attendance and observations and managers on billing, reporting and compliance, with written and video guides. Three months of support is included after go-live, then a maintenance plan if you want one. Because you own the system, you decide when it changes rather than having updates pushed on you.