04 / Kinderly

Building a multi-sided SaaS product from zero.

From discovery to implementation, I connected nursery operations, teachers, and parents in one bilingual SaaS product.

ROLE

Discovery, product strategy, UX & implementation

CONTEXT

B2B SaaS / EdTech

STAGE

Responsive web SaaS

Kinderly public website, captured September 2026 — Public website · September 2026

parents in product validation: 15
teachers in product validation: 7
nurseries engaged through stakeholders: 5

01 / CONTEXT

The product problem.

I validated the problem with 15 parents and 7 teachers, and engaged stakeholders from 5 nurseries to understand daily operations and communication needs. Those findings shaped a bilingual MVP, from product strategy and UX through implementation, testing, and deployment.

Explore the scope

Child & classroom managementAttendanceDaily activity trackingParent timelineMessagingPhotos & mediaEvents & announcementsIncidentsFood & menusLesson planningReportingActivity logsSubscription administration

02 / PRODUCT DECISIONS

What matters. And why.

Four purpose-built experiences.

Platform Admin, Nursery Admin, Teacher, and Parent experiences reflect different responsibilities instead of sending everyone into one dashboard.

A daily record becomes a shared timeline.

Convert teacher activity capture into a parent-facing daily timeline.

Privacy belongs in the product model.

Multi-tenant nursery isolation. Treat children’s media and personal data as permission-sensitive product areas.

Design for both languages.

A bilingual Arabic / English product experience, including RTL.

PRODUCT CONTEXT

A responsive web SaaS connecting nursery operations, teachers, and parents.

Visit the product

NEXT / 05