Home About Case Studies Hire Me Contact
Currently available for select engagements

Hire SaaS Developer for Childcare
Senior, direct, no layers

Hire a SaaS Developer for Childcare: a multi-site platform for rooms, staffing and billing if you run more than one setting. Senior-only delivery, a fixed scope agreed before build, and direct communication throughout.

Direct
Senior-only delivery
Fixed
Scope agreed first
Documented
Handover included
One owner
No layers
Childcare — SaaS Developer

A saas developer for childcare

Most childcare settings lose hours every week to administration that has nothing to do with looking after children: enquiries answered twice, waitlists kept in three places, paper registers copied into billing, and parent messages scattered across email, text and noticeboards. At the same time parents expect quick answers about places, fees and settling in, and they judge a setting partly on how easy it is to deal with.

The work also carries real responsibility. Attendance, authorised pickup, allergies, medication and safeguarding notes must be accurate and available to the right staff at the right time, while children's photos and records need careful handling. A system that is hard to use gets worked around, and workarounds are where mistakes happen.

For childcare providers, nurseries and preschools, a saas developer is useful in a specific way: a multi-site platform for rooms, staffing and billing if you run more than one setting. That is the work this engagement is built around — not a generic brief with an industry name swapped in, but the job as it actually runs in this sector, where a typical day runs on attendance at drop-off, room ratios, meals, sleep and learning observations, pickup authorisation, parent messages, and fee billing at month end.

Book a free discovery call and we will test the fit before any scope is agreed.

What you get

What this engagement covers for childcare

  • Tenant nurseries, kept apart — Each nursery gets its own tenant: its children, parents, rooms, staff and attendance visible only to its own team. A group can hold several tenants without one nursery's children or pickup rules leaking into another's lists.
  • Plans priced by children and rooms — Tiers follow how nurseries buy: by enrolled children, by rooms, or by staff seats, with trials that cover a real nursery week rather than an empty demo.
  • Signup a nursery manager can finish alone — A new nursery creates its account, adds its rooms and age groups, sets its pickup rules and parent messaging and invites its staff, with guided first steps that match a real first nursery day.
  • Attendance, pickup and parent messaging — Each day carries its attendance, authorised pickup list and parent messages in order, so a handover at pickup is checked against the record, not against memory.
  • Child records with role-limited access — Child records, medical notes and development notes sit inside their tenant with access limited by role, so room staff, managers and parents each see what their work needs and nothing else.
  • An admin view for the product owner — The business sees tenants, trials, failed payments and support requests in one place, and can pause a tenant or help with a stuck attendance list without touching its children or any other nursery's data.
Systems this sector runs

Built to fit the tools childcare already use

The build starts with the tenant boundary at child level, because one nursery seeing another's children or pickup permissions ends the product. Children, parents, rooms, staff and attendance are modelled per tenant from the first table, and tests deliberately try to read across tenants, including through siblings at two nurseries and shared staff.

Launch is proven on a real nursery week, not a demo list. A small group of real nurseries runs live attendance, pickup and parent messaging on subscription through a full week, and billing, room setup and support are fixed from what those nurseries actually hit before the product opens wider. Code, billing setup and hosting stay in the business's own accounts.

  • Brightwheel — enrolment, billing, attendance and parent messaging in one place.
  • Procare Solutions — childcare management covering attendance, billing and family accounts.
  • Famly — learning journals, observations and parent communication.
  • Kangarootime — enrolment, billing and reporting across one or several sites.
How it works

From kickoff to delivery for childcare

  1. Map the paying nursery and its first nursery week

    The buyer, the subscription and the first-week journey are defined, and scope is cut to the smallest system a nursery would keep paying for after its first safe, complete week.

  2. Build the tenant boundary before any feature

    Children, parents and rooms are modelled per tenant first, with cross-tenant reading attempts tested before attendance features are layered on top.

  3. Wire billing to children and add attendance

    Plans, trials and payments are connected, and attendance, pickup rules and parent portals are built and tested with real nursery days.

  4. Pilot with real nurseries through a nursery week

    A small group of real nurseries runs live attendance and pickup on subscription, and billing, onboarding and support are fixed from their experience before wider launch.

Why Omer

Why hire Omer

  • Nursery-day thinking, not feature lists: Scope follows a real day: attendance, pickup, parent messages and handover, so the first release covers a cycle a nursery manager recognises.
  • Tenant tests that try to break isolation: Isolation is attacked in testing, through siblings at two nurseries and shared staff, because a child-record leak between nurseries cannot be repaired with an apology.
  • Pickup checked against the record: Authorised pickup lists sit on the day's attendance, so a handover is verified, not remembered.
  • Billing matched to how nurseries buy: Tiers follow children, rooms or seats, and trials cover a real nursery week, so pricing reads as fair to the buyer.
  • Handover the business actually owns: Code, billing and hosting belong to the business, documented for the team that grows the product.
Outcomes

What changes for childcare

For a nursery manager, the product earns its keep at pickup: attendance, authorised pickup lists and parent messages sit on the day's record in order, so a handover is checked against the record instead of against memory, and child records stay visible only to the room staff, managers and parents whose work needs them. A new nursery can sign up, add its rooms and age groups, set its pickup rules and parent messaging and run its first nursery week without a developer setting it up, while each nursery's children and pickup permissions stay inside its own tenant. Growth comes nursery by nursery, with billing and support handled from one admin view.

FAQ

Questions, answered

When does a nursery group need SaaS instead of software for its own use?
When it intends to sell the childcare system to other nurseries. Software for its own nurseries needs a single-business system; a system sold to many nurseries needs tenants, billing and signup machinery, and that machinery is only worth building when subscriptions are the plan.
How do you stop one nursery seeing another nursery's children and pickup lists?
By modelling every child, parent, room, staff and attendance record under a tenant from the start, and testing cross-tenant access deliberately, including siblings at two nurseries and shared staff. A nursery's data is never filtered at display time only.
How does billing work when a nursery's enrolment changes through the year?
Plans are built around nursery buying patterns, such as children, rooms or seats, with changes that take effect cleanly at the next period. Failed payments trigger reminders and a clear grace path agreed before launch, so a nursery is not cut off mid-week without warning.
Can a nursery manager set the system up without training?
That is the design goal. Signup, room and age-group setup, pickup-rule setup and staff invites are tested with people who have never seen the product, and the points where they stall are redesigned until most nurseries get through unaided.
Who owns the childcare product, its data and its billing?
The business does: code, billing setup, hosting and documentation. Each nursery tenant owns its own child records inside the product, and the product can be grown by any competent team from the handover.
Currently available for select engagements

Ready to get started?

The best way to explore working together is a quick conversation. Reach out through your preferred channel and let us discuss your project.