How to Build an App Like Brightwheel (Childcare Management)

A preschool chain with 15 centers pays Brightwheel $36,000–$72,000 per year. That number compounds every year, and the platform is still not yours. The parent data lives in Brightwheel's database. The billing relationship runs through their system. And when your state licensing agency needs a custom report, you either make it work in their export format or you file it manually.

That is why daycare franchise networks, after-school program operators, and multi-center childcare organizations build their own platforms. Custom breaks even in two to three years. After that, every dollar saved goes straight to the business.

Here is what it takes to build a childcare management system that can replace Brightwheel.

Who Actually Builds This

Not every childcare operator needs a custom platform. A single-location preschool is better served by Brightwheel or HiMama. The economics only make sense at scale.

The organizations that build custom are: preschool and daycare franchise networks operating ten or more locations, after-school program operators running programs across a school district, church-based childcare ministries with multiple campuses, employer-sponsored childcare centers (common in healthcare and corporate campuses), summer camp organizations with seasonal billing complexity, and government-subsidized Head Start programs that need to produce reports for state and federal agencies in specific formats.

What they share: high center count, specific compliance requirements that off-the-shelf tools do not meet cleanly, and a per-seat cost that keeps growing with enrollment.

The Feature Set

Check-In and Check-Out

This is the most critical feature in the entire system, both for safety and for state licensing compliance.

When a parent arrives to drop off their child, they check in using one of three methods: a QR code unique to their family, a PIN, or face recognition. Staff see a real-time roster of who is present in each classroom. The system logs arrival time to the second.

Pickup is where the compliance requirements get specific. Every state requires that childcare centers maintain an authorized pickup list. Only adults named on that list can check out a child. When someone attempts a pickup, the app prompts the staff member to verify the person's identity against the authorized list. If they are not on the list, the system flags it and the child cannot be released.

All of this data, arrival time, departure time, who performed the pickup, must be stored in a format that can be exported for state licensing audits. That means timestamped records, not just a daily count.

Daily Reports

Parents want to know what their child did. This sounds simple, but the implementation takes discipline to get right.

A daily report includes: meals (what was offered, how much was eaten), nap (start time, end time, duration), diapers or potty (times and outcomes), activities (what the class did), mood, and photos or short video clips captured during the day.

The critical design decision is when teachers fill these out. Not at the end of the day. Teachers complete daily reports on a tablet during the day, in short bursts between activities. The UI needs to be fast enough to use with one hand while the other manages a toddler. Large touch targets, quick dropdowns for common entries, and a "add photo" button that goes directly to the camera.

Parents receive a push notification when the report is ready. They open the app and see everything from the day.

Classroom Management and Ratio Alerts

Staff-to-child ratios are set by state law. Common ratios: 1:4 for infants, 1:6 for toddlers, 1:8 for preschool-age children. These vary by state, and a platform serving a multi-state franchise needs to handle different rules per location.

The system tracks which staff members are clocked in and assigned to which classroom at any given moment. It tracks how many children are currently checked in to each classroom. When the ratio is violated, it fires an alert to the center director immediately.

Room assignment is per child per day. A child might move from the infant room to the toddler room as they age up, and the system needs to reflect that move accurately for ratio calculations.

Parent Communication

In-app messaging between teachers and parents keeps all communication documented. This matters for licensing and for liability. A parent's claim that "no one told me about the incident" is easier to address when every message is logged with a timestamp in a system you control.

The communication layer includes three modes: one-to-one messages between a teacher and a specific parent, group announcements from a teacher to all parents in a classroom, and urgent center-wide alerts for events like fire drills, illness outbreaks, or emergency closures.

This is not SMS. SMS takes the conversation outside the platform and into personal phone numbers. Everything should run through the app.

Billing and Subsidy Management

Tuition billing is standard: monthly invoices, automated ACH payments via Stripe, sibling discounts, late payment fees.

Subsidy management is where it gets complex. Government childcare assistance programs like CCAP (Child Care and Development Fund) pay a portion of a family's tuition directly to the center. The parent pays the difference. The system must track the subsidy amount and the parent-owed balance as separate line items, invoice each correctly, and reconcile subsidy payments when they arrive, often on a different schedule than parent payments.

For Head Start and other federally funded programs, there is additional reporting: attendance records that demonstrate the subsidy was used for actual enrolled children, not phantom enrollments. This data needs to be exportable in formats the state or federal agency specifies.

Licensing Compliance Reports

Most states require centers to log specific events and make those logs available for licensing inspections. Common requirements include injury reports (date, time, nature of injury, staff present, parent notification), medication administration logs (what was given, dose, time, who administered), and nap records for infant rooms (which child, how long, staff-to-child ratio at time of nap).

The system generates these reports on demand, formatted for export. The format matters. A licensing inspector is not going to work with a raw CSV. The export needs to match whatever the state agency expects, which means the platform needs a configurable report builder for multi-state franchise operators.

Staff Management

Three things to track for staff: certifications, schedules, and background checks.

Certifications include CPR, first aid, and state-mandated training hours. The system stores the certificate, the expiration date, and sends alerts before expiration. A staff member whose CPR certification lapses cannot be counted toward ratio compliance.

Staff scheduling and attendance tracks who is supposed to be in which classroom and who actually showed up. This feeds directly into the ratio tracking system.

Background check status is a binary: cleared or not. The system should block a staff member from being added to a classroom roster if their background check is not cleared.

Tech Stack

Teacher tablet app: React. Tablets run in kiosk mode in the classroom. The UI is designed for touch, with large buttons and minimal text input.

Parent mobile app: React Native. One codebase for iOS and Android. Parents check in their child, receive daily reports, message teachers, and pay tuition from the same app.

API: Node.js. Handles business logic, ratio calculations, billing events, and notification triggers.

Database: PostgreSQL. Relational structure works well for the compliance reporting requirements. Attendance records, subsidy amounts, and staff certifications all have well-defined schemas.

Billing: Stripe. ACH payments for tuition, subsidy reconciliation handled in the application layer.

Photo and video storage: AWS S3. Daily reports include photos and short videos. S3 handles storage at scale without file size headaches.

Push notifications: Firebase Cloud Messaging. Parents get notified when a daily report is ready, when a message comes in, and when the center issues an urgent alert.

Timeline and Cost

A core platform covering check-in, daily reports, classroom management, parent messaging, billing with subsidy support, licensing compliance reports, and staff management takes 12–14 weeks to build.

That assumes a focused team: one product lead, two to three developers, and a QA engineer. The build follows a two-week discovery sprint to finalize the feature scope and compliance requirements for the specific states the operator serves, followed by ten to twelve weeks of development.

Cost: $120,000–$180,000.

The range depends on how many states the platform needs to serve (each adds compliance report variants), whether face recognition is included in the check-in module, and how complex the subsidy management requirements are for the operator's funding sources.

Brightwheel at $400/month per center across 15 locations costs $72,000 in year one alone. The custom platform pays for itself in less than two and a half years.

What to Get Right Before You Build

The single biggest mistake operators make is skipping the compliance audit before design begins. Every state has different licensing requirements. The ratio rules differ. The required log formats differ. The events that must be documented differ.

Before writing a line of code, map every state your network operates in. Pull the actual licensing regulations. Identify every report the state agency expects to see during an inspection. Build those into the requirements document.

The second mistake is designing the daily report UI for desktop. Teachers use tablets. They are standing up. They have a child in their lap or nearby. Every input that requires typing is a problem. Use dropdowns, presets, and photo capture wherever possible.

If you are running a franchise network or a multi-center childcare operation and the Brightwheel bill is starting to feel like a fixed cost that will never go down, the math for a custom platform works. The key is building the compliance layer right from the start, not as an afterthought three months after launch.