Your nurseries already
produce the data.
This layer tells you
what to do with it.
Nursery Intelligence is an intelligence layer for nursery operations: occupancy, enquiries, staffing risk, revenue and compliance in one view, with AI recommendations that turn into assigned actions and measured outcomes. This proposal defines the MVP, the delivery plan and the commercial terms.
Questions as you read? Use the assistant in the corner, or .
Two product environments. One intelligence engine.
Owners, nursery managers, finance and board. Brief, dashboards, recommendations, actions.
Sites, users, imports, business rules, AI monitoring, audit and platform health.
Nurseries are rich in data and poor in interpretation.
How it works today
- Data sits inside KinderSoft/Famly reports
- Occupancy reviewed manually, room by room
- Enquiries chased from memory and inboxes
- Ratio risk discovered on the morning it happens
- Aged debt spotted late
- Ofsted preparation as a static checklist
- No record of which management decisions worked
With Nursery Intelligence
- One daily brief: critical, opportunity, watch, positive
- Occupancy gaps quantified in children and revenue
- Enquiry pipeline with follow-up and staleness alerts
- Staffing and qualification risk flagged in advance
- Revenue against target and aged debt in view
- Compliance themes with evidence and improvement actions
- Every action closed out with a recorded outcome
What the first release must prove.
Give owners a consolidated picture of two to three nursery settings, with room and period filters.
Surface the handful of items that genuinely require management attention today.
Quantify unused capacity, the children needed to hit target and the revenue attached to it.
Improve enquiry follow-up, showarounds and conversion with a nursery-specific pipeline.
Highlight upcoming ratio, absence and qualification risks while there is still time to act.
Turn recommendations into assigned actions and record the occupancy, revenue or risk outcome.
Two product environments on one intelligence engine.
Management Portal
Confirmed MVPThe daily operating view for nursery leadership: what needs attention, why, and what to do about it.
- Today's Brief
- Executive Dashboard
- Occupancy Intelligence
- Enquiry & Conversion CRM
- Staffing Risk
- Revenue Intelligence
- Compliance readiness
- Recommendations, Actions & Outcomes
Super Admin Console
Confirmed MVPThe control plane: configuration, data feeds, business rules and oversight of the intelligence layer.
- Organisations & sites
- Users & permissions
- Data imports & error logs
- Business rules & thresholds
- AI monitoring & feedback
- Audit trail
- Platform health
Shared Intelligence Engine
Confirmed MVPDeterministic metrics, signal detection and AI orchestration shared by both environments.
- Metrics engine
- Signal detection
- AI orchestration
- Permissions
- Notifications
- Audit & traceability
Data Foundation
Confirmed MVPCanonical nursery entities fed by scheduled imports from the operational nursery system.
- Sites, rooms, capacity
- Bookings & attendance
- Enquiries
- Staff & qualifications
- Revenue & balances
- Targets
- Import validation
Five layers. Click any layer to explore.
React/Next-style frontend, a Node-equivalent API layer, PostgreSQL and an approved LLM provider are the current recommendation, with separate development and production environments, secure object storage, monitoring and automated backups. Final technology choices are confirmed during Phase 1 technical discovery.
Every module, by role, with MVP status.
Owner intelligence
The third-party services that make the pilot possible.
Source of rooms, capacity, bookings, staff and financial data during the pilot.
- Vendor status
- Current operational system; export format to be agreed
- Dependency
- Feeds occupancy, staffing and finance intelligence
- Manual fallback
- Scheduled CSV/Excel export handled by the nursery team
- Third-party cost
- No third-party fee expected
Alternative system of record if adopted by the nursery organisation.
- Vendor status
- API/export options assessed during discovery
- Dependency
- Replaces KinderSoft as the primary feed if adopted
- Manual fallback
- Structured export import
- Third-party cost
- Subject to Famly's own plan
Reliable scheduled feed of the agreed management datasets.
- Vendor status
- Built by Keza Studio
- Dependency
- Underpins every metric in the platform
- Manual fallback
- Manual upload with validation and error reporting
- Third-party cost
- Included
Map source columns to canonical entities and reject bad rows visibly.
- Vendor status
- Built by Keza Studio
- Dependency
- Data trust
- Manual fallback
- Admin-corrected re-import
- Third-party cost
- Included
Explanation, prioritisation, summarisation and suggested actions over deterministic metrics.
- Vendor status
- Provider confirmed during discovery
- Dependency
- Powers recommendations and the reader assistant
- Manual fallback
- Rule-based recommendation text without narrative
- Third-party cost
- Usage-based provider fee
User invitations, password resets, follow-up and action reminders.
- Vendor status
- Selection during discovery
- Dependency
- Account access and reminders
- Manual fallback
- In-app notifications only
- Third-party cost
- Usage-based fee
Compliance evidence and document uploads.
- Vendor status
- Managed cloud provider
- Dependency
- Compliance module
- Manual fallback
- N/A
- Third-party cost
- Consumption-based
Platform health, logs and error investigation.
- Vendor status
- Selection during discovery
- Dependency
- Operational confidence
- Manual fallback
- Cloud-native tooling
- Third-party cost
- Subscription
Scheduled backups of the platform database and documents.
- Vendor status
- Managed cloud provider
- Dependency
- Resilience
- Manual fallback
- N/A
- Third-party cost
- Consumption-based
Automated financial synchronisation beyond the agreed metrics.
- Vendor status
- Not in MVP unless expressly agreed
- Dependency
- Deeper finance reporting
- Manual fallback
- Agreed financial fields via import
- Third-party cost
- Scoped separately
Nursery Intelligence is designed to work alongside an operational nursery-management system during the pilot. A reliable scheduled data feed is preferable to delaying the product solely to achieve fully real-time integration. Where an integration is unavailable, an auditable manual or scheduled fallback will be used for the first release.
What's in, what's out, and what's parked.
Scope Boundaries & Deferred FeaturesBeing clear about scope is how the pilot ships. Everything below is decided, not undecided.
Everything scoped in Sections 04 to 07: the three product surfaces and the shared platform systems required to run the pilot workflow end-to-end.
- Full parent messaging system
- Complete Parent App
- Complete Practitioner App
- Full learning journal
- Full EYFS observation system
- Complete attendance / sign-in system
- Medication management
- Accident and incident management
- Full staff HR system
- Full rota management
- Full nursery billing ledger
- Payment processing
- Funding administration
- Tax-Free Childcare processing
- Full historical KinderSoft migration
- Payroll
- Native iOS application
- Native Android application
- Advanced predictive AI models
- Automated accounting integrations beyond those agreed
Parked products
Full parent application, learning journal and parent messaging.
- Excluded
- Messaging, daily care feeds, observations, media sharing, parent billing views.
- Why parked
- Already served by the existing nursery system; adds no evidence to the intelligence proposition.
- Prototype
- Architecture preserves a future parent role and permission path.
Practitioner application, full EYFS observation and attendance sign-in system.
- Excluded
- Observations, learning journals, medication, accident and incident management.
- Why parked
- System-of-record functionality; revisited once intelligence value is proven.
- Prototype
- Practitioner role reserved in the permission model.
Full nursery billing ledger, payment processing and funding administration.
- Excluded
- Invoicing, payment capture, Tax-Free Childcare, funding claims, payroll.
- Why parked
- The MVP provides financial intelligence, not a finance system of record.
- Prototype
- Revenue, target and aged-debt metrics are in scope for the MVP.
Training: a focused compliance module, not an LMS
MVP training is a focused embedded learning and compliance module. It is not a full LMS.
- · Nursery sites, rooms and capacity
- · Staff records and relevant qualifications
- · Children or aggregate occupancy information
- · Bookings and expected attendance
- · Enquiries
- · Financial fields required for the agreed metrics
- · Business targets
- · Large-scale migration of all historic nursery records
- · Safeguarding-critical records
- · Full child records
- · Historical observations and learning journals
- · Financial ledgers
- · Media libraries
Data → insight → recommendation → action → outcome.
Seven delivery phases, run iteratively.
Confirm the MVP, review existing prototypes, validate data sources and agree the architecture.
- Consolidate PRD & user stories
- Prototype review
- Data source validation
- Sprint backlog
- Acceptance criteria
Turn current product thinking into role-specific, production-ready interface design.
- Information architecture
- Role-specific navigation
- Wireframes
- High-fidelity UI
- Design system
- Clickable flows
Frontend, backend, database, authentication, roles and the organisation/site model.
- Frontend setup
- Backend setup
- Database
- Auth & MFA
- Roles & permissions
- Multi-site model
Today's Brief, Executive Dashboard, occupancy, enquiries, staffing, finance, recommendations and actions.
- Today's Brief
- Executive Dashboard
- Occupancy
- Enquiry CRM
- Staffing risk
- Finance
- Recommendations
- Actions
Import mechanisms, source mapping, calculations and data validation.
- Import mechanisms
- Source mapping
- Metric calculations
- Data validation
- Integration testing
Functional, role, browser, responsive, data-integrity and recommendation testing.
- Functional testing
- Role testing
- Responsive testing
- Data integrity
- Recommendation testing
- Bug fixing
Production deployment, data and user setup, administrator walkthrough and launch support.
- Production deployment
- Data setup
- User setup
- Admin walkthrough
- Launch support
- Early monitoring
Children's data means security is a feature, not an afterthought.
Data Protection
TLS across every client, service and integration boundary.
Managed database encryption and secure object storage for evidence documents.
Signed, time-limited URLs for compliance evidence, with no public buckets.
The MVP holds the management data required for intelligence, not full child records.
Access
Hashed credentials, password reset, invitations, activation and deactivation.
Implemented for Super Admin and privileged administrative roles where agreed in discovery.
Owner, Nursery Manager, Finance/Admin, Board Viewer and Super Admin with site-level scoping.
Restricted module access and protected application routes by default.
Central secret store; no credentials in code or logs.
Operations
Structured audit activity for important administrative and permission actions.
Schema-validated inputs across the API and import pipelines.
Application error reporting and platform health visibility in the Super Admin console.
Maintained dependencies with automated scanning in CI.
Resilience
Scheduled backups with a documented restore approach.
Distinct development and production configuration and data.
Intelligence
Business-critical figures are calculated in code; AI explains rather than generates them.
Readers can mark a recommendation incorrect; feedback is reviewable in the console.
Prompts receive only the data the requesting role and site are permitted to see.
Regulatory
Architecture designed with UK GDPR considerations across nursery, staff, parent and child-related data.
Structures that support agreed retention and deletion decisions.
Safeguarding-critical records are out of MVP scope and require separate validation.
Keza Studio implements the agreed technical requirements. Formal legal interpretation, privacy policies, retention decisions and regulatory sign-off remain the responsibility of the client and its appointed advisers.
Cadence, roles and change control.
| Cadence | Attendees | Focus |
|---|---|---|
| Weekly | Abiola + Keza Studio | Progress update, decisions required, blockers |
| Regular | Keza Studio + nursery managers | Working demonstrations of delivered functionality |
| Review points | Abiola + nominated stakeholders | Design and business-rule sign-off in one consolidated pass |
| As required | Finance / administration | Revenue, target and debt data definitions |
Six to eight weeks to a controlled nursery pilot.
Estimated delivery is six to eight weeks and assumes timely client decisions, prompt consolidated feedback, access to nursery data and operational stakeholders, and no material change to the agreed MVP. Workstreams may run in parallel.
What we need from your side to land on time.
Assumptions & Client ResponsibilitiesDelivery is a two-team sport. The commitments below are the client-side inputs the timeline depends on.
KinderSoft/Famly exports or API access covering rooms, capacity, bookings, staff, enquiries and the agreed financial fields.
Occupancy targets, revenue targets, required ratios, follow-up windows and qualifying rules for connector commission.
A nominated decision maker able to approve the MVP backlog, designs and business rules within the agreed review points.
Time with owners, nursery managers and finance/administration so the workflows reflect real operations.
Confirmation of whether KinderSoft or Famly remains the operational system during the pilot.
One agreed set of feedback per review point rather than rolling individual changes.
Client-supplied privacy notices, retention decisions and any compliance content shown in the product.
Three months included, then two clear ways to continue.
Warranty & Ongoing CareWarranty covers reproducible defects in the agreed functionality. Anything new, changed or externally caused sits outside, with a separate optional maintenance path.
Reproducible defects within the delivered scope: software bugs, stability issues, performance issues caused by delivered code, deployment defects and reasonable technical support on delivered functionality.
- New features, modules or integrations
- New business requirements
- Major design or UX changes
- Third-party provider outages or API changes
- Regulatory changes after project acceptance
- Major data-migration work
Care options after month three
The included post-launch warranty period, giving the nursery team confidence during early live use.
- Reproducible defect resolution within delivered scope
- Bug, stability and performance fixes
- Security corrections to delivered code
- Reasonable deployment support
- Early-life platform monitoring
- Support investigating issues in normal use
- New features or modules
- New integrations
- Material workflow changes
- Major UX redesign
- Major data-migration work
Keeps the live platform stable, secure and properly maintained after the warranty period.
- Ongoing bug fixing
- Security patches
- Dependency and package maintenance
- Infrastructure, error and performance monitoring
- Backup oversight
- Deployment support and platform health oversight
- New features or modules
- Major product changes
- New third-party integrations
- Major UX/UI redesign
- Architecture changes
Ongoing access to a technical partner who already knows the product, architecture, data strategy and SaaS ambition.
- Product changes and small enhancements
- Dashboard and reporting improvements
- AI recommendation improvements
- Technical planning and architecture review
- Integration support and data-flow improvements
- Roadmap input as the product moves towards SaaS
- Major new features
- New product environments
- Significant architectural change
- Large new workflows
- Substantial data migration
Two payment options, one fixed scope.
What the platform could return, at your scale
Model the impact for your operation
Tune the assumptions to your data. Numbers update live.
What Nursery Intelligence unlocks
Assumes a conservative 3 percentage-point occupancy gain from acting on quantified gaps and stale enquiries, 51 billable weeks per place, half of management reporting time reclaimed at a £28 blended hourly rate, and the £7,000 build cost. Indicative only. We will model against your actuals in discovery.
100% payable before project commencement. Lowest overall investment and development resource committed immediately.
- Before project commencement£7,000
Two equal payments across the engagement, covering the same agreed MVP scope.
- Project commencement£3,932
- Development completion, prior to production launch£3,932
- Both options cover exactly the same agreed MVP scope.
- Included: discovery, UX/UI, management portal, Super Admin console, frontend, backend, database, auth, permissions, multi-site structure and the full intelligence feature set.
- Included: agreed data import/integration work, testing, QA, deployment, administrator walkthrough, launch support and three months' warranty.
- Excluded: infrastructure, LLM provider usage and other third-party service costs.
- Large-scale historical migration and functionality outside the agreed MVP backlog are treated as change requests.
How we deliver, and why this is the right team.
We work beyond individual screens and map complete journeys, actions and outcomes.
The value comes from understanding the underlying operational data, not bolting a chatbot onto a CRM.
Owners, managers, finance, administrators, connectors, with permission architecture designed from the outset.
Modern tooling with human review, architecture, QA, security and clear accountability.
A focused MVP that avoids rebuilding Famly or KinderSoft, with change control in writing.
Built to be proven, refined from real evidence and grown into a commercial nursery technology business.
What becomes possible the day the pilot goes live.
Nursery Intelligence can become the layer that tells nursery leaders what to do next.
The first release is a proving ground. It takes the data your nurseries already generate and turns it into daily decisions with recorded outcomes, across two to three settings first, and designed from day one for the commercial nursery technology business you intend to build.