Childcare apps

// The problem

A group of childcare centres sends updates by paper notes and email, parents call to ask about naps and meals, and fees are paid by cheque and e-transfer with no record in one place.

// What we would build

An iOS and Android app for parents and a matching app for educators: daily updates and photos with parents' consent, secure messages with the room, sign-in and sign-out, and fees and statements in one place.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• Stripe
• AWS

// The problem

A nonprofit with four centres keeps its waitlist in a spreadsheet, families call every month to ask where they stand, and enrolment paperwork is filled in on paper.

// What we would build

A portal designed for busy parents: join the waitlist for one or more centres, see where you stand, accept a space when it opens, and complete enrolment forms online, with a priority list the director manages.

// What is in it

// Stack

• Next.js
• PostgreSQL
• DigitalOcean

// The problem

Educators count children and staff in each room by hand through the day, and the director only knows a room was over ratio when someone writes it down.

// What we would build

An Android tablet app in each room and a web view for the director: children and educators signed in and out, live counts for each room against the ratios you set, and an alert when a room is close to its limit.

// What is in it

// Stack

• Next.js
• React Native (Android)
• PostgreSQL
• AWS

// The problem

The director of a group of centres sees enrolment, attendance, fees and staffing in separate spreadsheets, each kept a little differently by each centre.

// What we would build

A dashboard that reads enrolment, attendance, fees and staff hours into one model, so the director sees occupancy, waitlist length, fees owed and staff hours by centre and room, measured the same way everywhere.

// What is in it

// Stack

• Next.js
• PostgreSQL
• dbt
• AWS

// The problem

A childcare centre's office copies fees into accounting, staff hours into payroll and subsidy amounts into statements, by hand, every month.

// What we would build

An integration hub between the childcare app, payroll and accounting, so fees, payments, subsidy amounts and staff hours reach the right system once, with a log of every message.

// What is in it

// Stack

• Node.js
• PostgreSQL
• OpenAPI
• Payroll and accounting interfaces
• AWS

// The problem

Centres receiving public childcare funding send monthly attendance reports to the funder, and every audit means matching sign-in sheets, spreadsheets and claims line by line.

// What we would build

Each day's attendance totals recorded on a private permissioned ledger the centres and the funder run nodes of, so subsidy claims are checked against one record nobody can rewrite. Most centres are better served by a database and a good report, and we will say so; the ledger earns its cost only when several operators and a funder want a record none of them controls.

// What is in it

// Stack

• Next.js
• PostgreSQL
• Hyperledger Besu (private, permissioned)
• AWS

// The problem

A childcare centre's director answers the same questions about hours, closures, illness policy and what to pack, by email, in several languages, often in the evening.

// What we would build

A help centre written from the centre's own handbook and policies, and an assistant that answers parents from it in their language and passes anything about a particular child to staff. It uses a frontier model through its API: the handbook is not private and traffic is low.

// What is in it

// Stack

• Frontier model API
• Next.js
• PostgreSQL with pgvector
• DigitalOcean