We built the system so you can look at the kids, not the paperwork around them.
Bloomffy didn’t start from a feature list. It started from watching an actual crèche day — a shared tablet passed between staff, a sleep-check every ten minutes, a rota that never quite matched who was really in the room — and asking what software would need to get right to actually replace the paper.
Why it exists
Irish crèches run on paper that was never built for the job: attendance registers, learning journals, accident books, and spreadsheets that all describe the same day from different angles — and none of them can produce, on demand, what a Tusla inspector could plausibly ask for.
Bloomffy started from two real staff interviews and a hands-on review of an actual admin app — not a generic “childcare CRM” brief. What shipped is shaped by that: device battery visibility so a dead tablet doesn’t stall a room, a sleep-check cadence that matches the real ten-minute rule, and a hard requirement that any routine logging action take the fewest taps possible, because the people using it are mid-task, not sitting at a desk.
It’s a young, independent product — built to be its own ownable brand from the start, not tied to any single crèche’s identity, and honest about being early: no inflated customer list, no borrowed logos, just what the system actually does today.
Not built as a tech-savvy tool
The one usability rule that overrides aesthetic preference whenever the two conflict: staff using the room tablet day-to-day are not tech-savvy. Concretely — an icon never appears without a short label, touch targets stay large throughout, and any routine logging action gets simplified until it takes the minimum possible taps. The sleep room’s dark mode exists for the same reason: a bright screen at nap-check time disturbs sleeping children, so the screen most likely to be used in the dark is designed to be used in the dark.
Five rules the build doesn’t bend on
These aren’t brand values on a poster — they’re architectural decisions that shape what Bloomffy will and won’t do, even when it would be easier not to.
No black-box model deciding your compliance status. Ratios, thresholds, and ECCE/NCS rules are rule-based, checkable, and explainable — the way anything an inspector reads should be.
A ratio breach or a missed check surfaces immediately but never blocks the person doing their job. The resolution gets logged too — the log itself is the evidence, not a tidied-up rota.
Ratios, space requirements, and payment-scheme rate bands are dated, verifiable data — not constants quietly baked into code that drift out of date with the regulation.
Corrections happen as an addendum, never by editing the original. That history is what makes a record trustworthy to someone reading it after the fact.
Bloomffy shows what staff actually logged. It never computes or asserts a correlation on their behalf — the person looking draws their own conclusion.