Industry solution
Every room's ratio in view, every family informed, every child's record kept with care
Staffing, family messages, learning journeys, tuition and waitlists designed to work as one for childcare and after-school programs.
The problem
The ratio sheet, the staff files, the family messages, the observation notes, the tuition ledger and the waitlist live in different places, and the director holds them together, usually from the floor.
Childcare centers, preschools and after-school programs run on a patchwork: a sign-in tablet or clipboard, a paper ratio sheet, a filing cabinet of staff files, a messaging app for families, a separate billing system, a waitlist spreadsheet and a binder of consent forms. Each holds part of the picture. The director is usually the one holding it together, often while covering a room herself.
The pressures are constant and physical. Every room has to stay in ratio from open to close, through breaks, nap and pickup, and only staff with current clearances and training can be counted. Turnover is a fact of life, and each new hire waits on background checks and training before they can work alone. Margins are thin, tuition and childcare assistance co-pays have to be right every month, and families expect to hear about their child's day, and about any incident, the same day.
Everything touches young children, so the bar for privacy is high. Photos need releases, authorized pickup lists and custody arrangements must be respected, and information about one child should never reach another family. Any tool has to keep people in charge, show each person only what their role needs, and make it easier, not harder, for a center to show a licensing visitor what they came to see.
Owner or operator of a childcare group
Occupancy, tuition collected and staffing across centers, and confidence that every site could show a licensing visitor what they ask for.
Center director
Keeping every room in ratio from open to close, and getting off the floor long enough to actually run the center.
Assistant director and front desk
Family questions, pickup changes, tours and incident follow-up handled the same day, without the phone ringing all afternoon.
Lead and assistant teachers
Time to observe and write about children, fewer paper forms, and clear information about allergies, pickups and photo releases.
Billing and family accounts lead
Tuition that posts correctly, assistance co-pays and claims that match attendance, and fewer awkward past-due talks at pickup.
After-school program coordinator
Knowing which children to expect at dismissal each day, and hearing about absences and pickup changes before the buses arrive.
A day in the life
Adaeze Morrison is Director of Operations at Juniper Row Early Learning, a family-owned group of three centers serving infants through pre-K, plus two after-school programs run inside partner elementary schools. It is the fourth week of the school year. Family conferences are three weeks away, several childcare assistance authorizations are up for renewal, and the infant waitlist is longer than it has ever been. This is her week, and the moments where the systems around her fall short.
Monday, 6:10 am
Adaeze's phone buzzes before she is out of the car. The infant room lead at the Maple Street center has a sick child at home, and a toddler assistant has a flat tire. Doors open at 6:30 and the first babies arrive at 6:35. Lucia, the center director, is texting the two floaters from the parking lot. One says yes, then mentions her pediatric first aid card lapsed last week. The only other adult free is Jordan, who accepted his offer three weeks ago and is still waiting on his fingerprint results. Lucia takes the infant room herself, and the morning's tours, calls and paperwork wait.
How this is solved: Keeping every room in ratio when call-outs hit before openingMonday, 2:00 pm
On the weekly directors' call, staffing takes the whole hour. Maple Street has made four offers since August. One candidate took another job while her background check was pending. Jordan's fingerprints are in their third week. A new assistant at the Cedar Park center finished her online orientation but not the in-person safe sleep training, so she cannot work in the infant room. When Adaeze asks which staff files would pass if a licensing consultant walked in this afternoon, nobody can say without a morning of checking binders.
How this is solved: New hires stuck between offer and cleared to workTuesday, 10:20 am
A toddler in the Caterpillar room is bitten on the arm during free play. The teacher fills in a paper incident report and slides it under the director's door; at pickup, the parent has not been told and asks who did it. That afternoon at the Hillview after-school program, a note that a second grader is going home with a friend's family sits in the general inbox, and staff spend twenty tense minutes confirming where he is. The front desk, meanwhile, answers the same question about Friday's closure fourteen times.
How this is solved: Incident notes, pickup changes and the same question all dayWednesday, 1:15 pm
During nap, Adaeze sits with the pre-K team at Cedar Park. Conferences are three weeks out and each teacher owes a learning summary for twenty children. Their observations are on sticky notes, in a spiral notebook and in photos on personal phones, which the center's own policy does not allow. Before using a group photo, one teacher checks a binder to see which children have no photo release. A father asked yesterday, kindly, what his daughter actually does all day.
How this is solved: Learning journeys written at nap time from sticky notesThursday, 9:00 am
Hye-jin, the family accounts lead, reconciles tuition across three centers and two after-school sites. Two families' assistance authorizations ended last week and nobody noticed, so their co-pays are wrong. Six autopays failed overnight. A sibling discount dropped off when a younger brother moved up to the toddler room. The subsidy claim needs attendance that matches the sign-in records, and one center's sheets are still on a clipboard. By noon Hye-jin has a list of awkward phone calls, and the owner is asking how much is past due at each center.
How this is solved: Tuition, co-pays and subsidy claims that do not line upFriday, 4:30 pm
A couple expecting in February tours Maple Street and asks the question every family asks: when could our baby start? The infant waitlist is a spreadsheet that still lists families who enrolled elsewhere months ago. Lucia knows three toddlers move up to the twos room in January, which would free infant seats, but only if the twos room has a teacher for them. A Tuesday and Thursday preschool spot has sat empty since August. Lucia gives the couple a hopeful guess and promises to call.
How this is solved: Waitlists, move-ups and the empty Tuesday-Thursday spotNone of these moments needs another stand-alone app. Each needs information that already exists, a sign-in, a clearance date, a family's note, a teacher's observation, an authorization end date, to reach the person who can act on it, with children's information seen only by the people who need it. That is the idea behind this solution concept: eight Burdenoff products, each doing one part of the work, on one shared foundation.
Challenges and how they are solved
Each challenge shows the problem as it happens, how the products are designed to hand work to each other, and the concepts that illustrate it. Share any challenge on its own.
Answers are in plain business terms. Choose Technical, or open any technical detail, to see how it works under the hood.
Challenge 1 of 6
It is 6:10 on a Monday. The infant room lead and a toddler assistant have both called out, and the doors open at 6:30. The director has a paper ratio sheet, a group text to the floaters and her own memory of who is qualified for which room. One floater's pediatric first aid card lapsed last week, which she mentions only after saying yes. The newest hire cannot be left alone with children until his fingerprint results come back. The same scramble repeats at lunch breaks, at nap and at close, when rooms combine as children go home. Staff know the ratios by heart; what nobody can see at a glance is who is on the floor, which of them count, and which room will be short at 3:00.
Directors spend the day covering rooms instead of running the center, qualified staff are called in at the last minute, and a gap at break time or at close is easy to miss until someone counts heads.
BuildMyIQ is designed to show how many children each room expects, hour by hour. CrewFoundry sets that against staff on the floor, and a lapsed first aid card or pending clearance means that person is not counted toward ratio. When someone calls out, FluidGrids offers the shift to qualified, cleared floaters and tells the director who accepted, and BigConsole shows the operations director how each gap was covered.
Technical detail
BuildMyIQ is designed to keep each child's daily sign-in and sign-out, room and scheduled days, so the expected headcount for every room by hour is known before anyone arrives. CrewFoundry is designed to set that headcount against the roster and staff clock-ins, applying the ratio and group size each room is configured for and counting only staff who are cleared and qualified for that room. Qualifications are designed to come from BuildMyIQ, where pediatric first aid, CPR and safe sleep training carry expiry dates, so a lapsed card shows on the roster before the person is counted. When a call-out is logged, CrewFoundry is designed to hand the open block to FluidGrids, which offers it to qualified, cleared floaters in order, tells the director who accepted and writes the gap and its cover to a datasink that feeds a BigConsole view for the operations director.
Directors see a gap before the doors open, cover goes to people who can be counted toward ratio, and the operations director sees how every gap was closed.
CrewFoundry
The director's day by room and hour: children signed in, staff required by each room's ratio against staff counted, rooms combining at close, and cleared floaters ranked for an open block.
Works with BuildMyIQ, FluidGrids
BuildMyIQ
The credential expiry board, shown here on staffing placements, lists lapsed and expiring training by person. It is designed to hold the first aid, CPR and safe sleep dates the ratio board checks.
Challenge 2 of 6
Since August, the Maple Street center has made four offers for its toddler rooms. One candidate took another job while her background check was pending. Another has waited three weeks for fingerprint results and can work only under direct supervision, so he cannot be counted alone. A new assistant at the Cedar Park center finished the online orientation but not the in-person safe sleep training its infant room requires. The checks, health statements, references and training certificates sit in a filing cabinet, a shared drive and a director's inbox. Before a licensing visit, a director spends a morning pulling binders to prove each staff file is complete, and nobody can say with confidence which files would pass today.
Positions stay open longer than they need to, cleared staff carry extra shifts, and missing staff file items surface at inspection time instead of weeks before.
CrewFoundry is designed to open a checklist for each new hire the day they accept an offer: background checks, fingerprints, health form, references and training, each with the date it arrived and who checked it. Until every item clears, the person is marked supervised-only and never counted alone. BuildMyIQ assigns the training the role needs, and FluidGrids reminds the new hire and the director about anything still missing.
Technical detail
CrewFoundry runs postings and interviews and is designed to carry each hire through offer, and to open a clearance record for each new hire the moment an offer is accepted: background and registry checks, fingerprint status, health statement, references and each required document, with the date each item arrived and who verified it. Until every item clears, the person carries a supervised-only status that the ratio board respects. BuildMyIQ is designed to assign the pre-service path the role needs, such as orientation, safe sleep, pediatric first aid and mandated reporter training, and to return each completion with its expiry date to the clearance record. FluidGrids is designed to chase what is missing, reminding the new hire about unfinished modules and the director about checks that have been pending too long. Each staff file then reads as one page per person.
New hires move from offer to cleared with nothing forgotten, supervised-only staff are designed never to be counted alone, and every staff file is ready before anyone asks for it.
CrewFoundry
Every new hire from accepted offer to cleared: each check and document with its date and verifier, a supervised-only badge until all clear, and training pulled from BuildMyIQ.
Works with BuildMyIQ, FluidGrids
BuildMyIQ
A clearance roster, shown on a volunteer field day, that checks required training, flags expired or pending items and sends refreshers. It is designed to track a new teacher's pre-service modules and return the cleared list to CrewFoundry.
Challenge 3 of 6
At 10:20 on Tuesday a toddler is bitten during free play. The teacher writes an incident report on paper and slides it under the director's door, and by pickup the parent still has not heard. The family of the child who bit needs to be told too, without naming the other child. At the after-school site, a note that a second grader is going home with a friend's family lands in a general inbox, and staff spend twenty minutes confirming where he is. All day the front desk answers the same questions about Friday's closure, the late-pickup policy and what to pack for the field trip, while room updates go out through paper notes, texts and a newsletter half the families never open.
Families lose trust when they hear late or from another parent, staff lose hours to repeat questions, and notes that affect a child's pickup wait in the same pile as everything else.
Botlit is designed to answer family questions from the center's handbook and calendar, passing anything about a particular child to named staff through FluidGrids. Pickup changes are checked against BuildMyIQ's approved pickup list and confirmed with the child's parent; staff still check ID at pickup. Incident reports from the classroom tablet reach the director for review, then each family privately, and each room gets an invite-only ComradeCircle space for news.
Technical detail
Botlit is designed to answer families on web chat or WhatsApp from the center's own family handbook, closure calendar and policies, showing the source of each answer and saying so when nothing matches. Anything about a specific child, such as a pickup change, an absence or a medication question, is routed to staff rather than answered: Botlit starts a FluidGrids workflow that reaches the room lead and site coordinator with a named owner. A pickup change is designed to be checked against the authorized pickup list in BuildMyIQ and confirmed with an enrolled parent before anyone relies on it; staff still check photo ID at pickup. Incident reports are designed to start from a FluidGrids form on the classroom tablet, go to the director for review, notify each family privately and hold a signature request for pickup. Room news goes to each room's invite-only circle in ComradeCircle, where only that room's families and staff are members.
Families hear about incidents the same day and in private, pickup changes reach the right adult at once, and the front desk keeps its time for the questions only a person can answer.
Botlit
An answer desk, shown on student services, that cites sources, follows handoff rules and starts a FluidGrids workflow for anything personal. It is designed to answer families from the handbook and send pickup changes and absences to staff.
FluidGrids
A workflow run that pauses for a named approver, shown here on a security playbook. It is designed to hold each incident report for the director's review before any family is notified.
ComradeCircle
A circle with its channels, including announcements, shown here on a public founders circle. Each room is designed to get an invite-only circle like this, so updates reach only that room's families and staff.
Challenge 4 of 6
Family conferences are three weeks away and each pre-K teacher owes a learning summary for twenty children. Observations are on sticky notes, in a spiral notebook and in photos on personal phones, which the center's own policy does not allow. Linking a note to the right developmental area means flipping through the early learning standards binder. Before using a group photo, a teacher checks another binder to see which children have no photo release. The only quiet time to write is nap, which is also when breaks happen. Families want to know what their child is learning, and at the end of the year the portfolio goes home as a folder that may not survive the next move.
Teachers write in the evenings or not at all, conference summaries arrive thin and late, and a photo shared without a release is a risk no center wants to take.
BuildMyIQ is designed to let teachers jot a note or snap a photo on the classroom tablet, tag the children and learning areas it shows, and hold back any photo tagged with a child who has no photo release. Each child's learning journey builds over the year, so conference summaries start from evidence, not memory. At year end, families with a private CollabKin space can keep their chosen highlights there.
Technical detail
BuildMyIQ is designed to give teachers an observation journal on the classroom tablet: a short note, a photo or a work sample, tagged to one or more children and to the developmental areas and early learning standards the center uses, which BuildMyIQ holds as its skills framework. Before a photo leaves the journal, BuildMyIQ is designed to check the photo release of every child tagged in it and to hold the photo if any release is missing. Observations build each child's learning journey by area over the year, so a conference summary starts from evidence rather than memory, and families are designed to see the shared entries on their phone. At year end, families who keep a private CollabKin family space are designed to be able to carry the highlights they choose there, so the journey outlasts the folder.
Teachers capture learning in the moment, conference summaries rest on real evidence, photos go out only with releases in place, and families keep the story.
BuildMyIQ
Observations tagged to children and developmental areas, a photo-release check on every tagged child, and a per-child learning journey ready for family conferences.
Works with CollabKin
CollabKin
A private family gallery of photos, recordings and keepsakes. It is designed to be where a family keeps the year's learning highlights after their child moves on.
Challenge 5 of 6
Thursday is billing day. The family accounts lead reconciles tuition for three centers and two after-school programs. Two families' childcare assistance authorizations ended last week, so their co-pays are wrong. Six autopays failed overnight. A sibling discount dropped off when a younger brother moved up to the toddler room. The after-school program bills drop-in days and a school-holiday camp week on top of monthly tuition. The subsidy claim needs attendance that matches the sign-in records, and one center's sheets are still on a clipboard. Meanwhile the owner asks how much tuition is past due at each center, and the answer takes a day to put together.
Cash arrives late, subsidy claims go out late or short, and families hear about billing mistakes after they have happened, often at pickup.
Subscriber Bot is designed to keep each family's rate, discounts, assistance co-pay with its end date, and payment results together, while charging stays with the center's own payment provider. BuildMyIQ supplies attended days for drop-in charges and subsidy claims. When a payment fails or assistance is about to end, FluidGrids reminds the family and tells the accounts lead, and BigConsole shows the owner what is past due at each center.
Technical detail
Subscriber Bot is designed to hold each family's tuition as a recurring relationship: plan and rate, days enrolled, sibling or staff discount, the assistance authorization with its co-pay and end date, the withdrawal notice period and payment status. Charging stays with the center's own payment processor; FluidGrids, whose connectors include Stripe, is designed to bring each payment result back to Subscriber Bot. BuildMyIQ is designed to pass attended and absent days, so drop-in charges and each subsidy claim's attendance totals are prepared from the sign-in record; the center submits the claim through its state's own process. When a payment fails or an authorization is thirty days from ending, Subscriber Bot is designed to hand the case to FluidGrids, which reminds the family, opens a follow-up for the accounts lead and writes the result to a datasink feeding a BigConsole collections console, whose alert rules are designed to warn the owner when past-due tuition crosses a set level.
Co-pays change on time, claims match attendance, a failed payment gets a friendly reminder the same day, and the owner sees what is owed by center without waiting a day for it.
Subscriber Bot
Every family's tuition plan with rate, discounts, assistance authorization, co-pay, end date and the last payment result from the center's processor, with failed payments and expiring authorizations flagged.
Works with BuildMyIQ, FluidGrids, BigConsole
FluidGrids
A workflow ending in a BigConsole datasink node, shown on a revenue example. It is designed to carry each center's tuition, claim and failed-payment results to the owner's console.
BigConsole
Alert rules on a data sink, shown on a hospital example, with severity, channels and throttling. They are designed to warn the owner when past-due tuition at a center crosses a set level.
Challenge 6 of 6
A couple expecting in February tours the Maple Street center and asks when their baby could start. The infant waitlist is a spreadsheet that still lists families who enrolled elsewhere months ago. The director knows three toddlers move up to the twos room in January, which would free infant seats, but only if the twos room has a teacher for them. A Tuesday and Thursday preschool spot has sat empty since August because nobody on the list asked for those days, and a sibling who should have priority is buried on page three. The owner wants to know how full each center really is against its licensed capacity, and whether a second infant room would fill.
Seats sit empty while families wait, priority promises are hard to keep consistently, and growth decisions rest on a spreadsheet nobody trusts.
BuildMyIQ is designed to show each room's open seats week by week, including move-ups, matched to waiting families by age, start date and days wanted. FluidGrids offers each seat in the center's priority order, siblings first for example, moving on after a set time. An accepted offer starts tuition in Subscriber Bot and tells CrewFoundry the room's new staffing need, and BigConsole shows the owner how full each center is.
Technical detail
BuildMyIQ is designed to plan seats room by room: licensed capacity, children enrolled by day pattern, each child's expected move-up date and the open seats that result week by week, with waitlisted families matched on age at start, start date and days wanted. When a seat opens, BuildMyIQ is designed to pass it to FluidGrids, where the center's waitlist priority rules, such as siblings first, then staff children, then date joined, are designed to be kept as a rule set it can test before use. FluidGrids offers the seat to the next family, waits the set time, then moves on. An accepted offer is designed to start the family's tuition plan in Subscriber Bot and send the room's new staffing need to CrewFoundry. Occupancy by center, day and age group flows through a FluidGrids datasink to a BigConsole console, so the owner can compare centers and see where demand is building.
Families get an honest start estimate on the tour, part-time seats find the right family, priority rules apply the same way every time, and growth decisions rest on real demand.
BuildMyIQ
Each room's licensed capacity, enrollment by day pattern and move-up dates laid out week by week, with open seats matched to waitlisted families and offers tracked.
Works with FluidGrids, Subscriber Bot, CrewFoundry
FluidGrids
The rule set editor, shown on a loan decision, with condition blocks and a test panel. It is designed to hold a center's waitlist priority rules and test them on sample families.
BigConsole
A multi-location console, shown on a restaurant portfolio, with filters and a location leaderboard. It is designed to compare occupancy and waitlist demand across centers.
How it fits together
Follow one center through a child's enrollment, an ordinary Tuesday and billing day. Each step is one product doing one job. FluidGrids passing results to BigConsole and Botlit handing requests to FluidGrids are built into those products; the other hand-offs show how the products are designed to work together.
To CrewFoundry: Children expected in each room by hour, including move-ups
To FluidGrids: Call-outs and rooms about to run short, with floaters who can cover
To Subscriber Bot: Families who accepted a seat, ready for billing
To FluidGrids: Pickup changes, absences and medication questions, each with a staff owner
To CollabKin: The year's highlights, if the family chooses to keep them
To BigConsole: What is owed, paid and claimed at each center
Step 1 of 8: Seats and child records
Technical detail
Products in this solution
Child records, seats, staff training and learning journeys
BuildMyIQ keeps enrollment, student records and training certificates. Daily sign-ins, approved pickup lists and photo releases are designed to sit alongside them, so seats, ratios and conferences all start from the same record.
Technical detail
BuildMyIQ's student information system holds enrollment and learner records, skills and certificates; daily sign-in and sign-out, authorized pickup lists and photo releases are designed as an extension of those records.
Hiring, clearances and the ratio roster
CrewFoundry handles job postings, interviews, time and attendance and leave in one record per person. It is designed to add offers, new-hire checklists and shift rosters, so the same place shows who is cleared and which rooms need cover.
Technical detail
CrewFoundry runs job postings, candidates, interviews, time and attendance and leave on one people record, and is designed to add offers, onboarding checklists and shift rosters, which is where clearance status and ratio coverage belong.
Cover offers, incident reports, reminders and priority rules
FluidGrids runs step-by-step routines started from a form or on a schedule, keeps a history of every run, tries again when a step fails and passes results to BigConsole. Here it is designed to run cover offers, incident reports, reminders and waitlist offers.
Technical detail
FluidGrids runs versioned, form-started and scheduled workflows with run history and retries, and its datasinks feed BigConsole consoles.
Family question desk
Botlit is designed to answer families on web chat and WhatsApp from the center's own handbook and calendar, showing where each answer came from. Anything about a particular child is handed to staff through FluidGrids.
Technical detail
Botlit agents are designed to answer on web chat and WhatsApp from the center's own documents and show their sources, and they can trigger FluidGrids workflows for anything staff must handle.
Invite-only room circles for families
ComradeCircle offers invite-only groups with announcements, polls and get-togethers families can RSVP to. Each room is designed to get its own group, with only that room's families and staff as members.
Technical detail
ComradeCircle offers public, private and invite-only circles with announcement channels, polls, events with RSVPs and role-based membership, which fits one invite-only circle per room.
Family tuition and assistance record
Subscriber Bot keeps track of recurring relationships: plans, status, renewal dates and invoices, the same shape as a family's tuition and assistance authorization. The center's own payment provider still handles the charging.
Technical detail
Subscriber Bot is a system of record for recurring relationships, with plans, lifecycle states, renewal dates and invoices, the same shape as a family's tuition and assistance authorization. Charging stays with the center's own payment processor.
Owner's console across centers
BigConsole turns results sent from FluidGrids into shared live boards. It is designed to let one layout roll out to every center, so the owner sees the whole group while each director sees only their own center.
Technical detail
BigConsole turns FluidGrids datasinks into shared consoles and is designed to let one template roll out across locations while each director sees only their own center.
Family keepsake of the learning journey
CollabKin is a private, members-only family space for photos, stories and milestones, with controls over who sees what. It is a natural home for a child's early learning highlights after the child moves on.
Technical detail
CollabKin is a private, members-only family space for photos, stories and milestones with visibility controls, a natural home for a child's early years after they move on.
All eight products run on Burdenoff Workspaces: one sign-in for staff and families, role-based access designed so each person sees only the children's information their role needs, one audit trail across every action, and one bill, so a center adds capabilities without adding another silo.
Concept gallery
15 concepts from 8 products. Each one links to its own page on the product's website, and every view has a link you can share.
CrewFoundry
The director's day by room and hour: children signed in, staff required by each room's ratio against staff counted, rooms combining at close, and cleared floaters ranked for an open block.
Works with BuildMyIQ, FluidGrids
BuildMyIQ
The credential expiry board, shown here on staffing placements, lists lapsed and expiring training by person. It is designed to hold the first aid, CPR and safe sleep dates the ratio board checks.
CrewFoundry
Every new hire from accepted offer to cleared: each check and document with its date and verifier, a supervised-only badge until all clear, and training pulled from BuildMyIQ.
Works with BuildMyIQ, FluidGrids
BuildMyIQ
A clearance roster, shown on a volunteer field day, that checks required training, flags expired or pending items and sends refreshers. It is designed to track a new teacher's pre-service modules and return the cleared list to CrewFoundry.
Botlit
An answer desk, shown on student services, that cites sources, follows handoff rules and starts a FluidGrids workflow for anything personal. It is designed to answer families from the handbook and send pickup changes and absences to staff.
FluidGrids
A workflow run that pauses for a named approver, shown here on a security playbook. It is designed to hold each incident report for the director's review before any family is notified.
ComradeCircle
A circle with its channels, including announcements, shown here on a public founders circle. Each room is designed to get an invite-only circle like this, so updates reach only that room's families and staff.
BuildMyIQ
Observations tagged to children and developmental areas, a photo-release check on every tagged child, and a per-child learning journey ready for family conferences.
Works with CollabKin
CollabKin
A private family gallery of photos, recordings and keepsakes. It is designed to be where a family keeps the year's learning highlights after their child moves on.
Subscriber Bot
Every family's tuition plan with rate, discounts, assistance authorization, co-pay, end date and the last payment result from the center's processor, with failed payments and expiring authorizations flagged.
Works with BuildMyIQ, FluidGrids, BigConsole
FluidGrids
A workflow ending in a BigConsole datasink node, shown on a revenue example. It is designed to carry each center's tuition, claim and failed-payment results to the owner's console.
BigConsole
Alert rules on a data sink, shown on a hospital example, with severity, channels and throttling. They are designed to warn the owner when past-due tuition at a center crosses a set level.
BuildMyIQ
Each room's licensed capacity, enrollment by day pattern and move-up dates laid out week by week, with open seats matched to waitlisted families and offers tracked.
Works with FluidGrids, Subscriber Bot, CrewFoundry
FluidGrids
The rule set editor, shown on a loan decision, with condition blocks and a test panel. It is designed to hold a center's waitlist priority rules and test them on sample families.
BigConsole
A multi-location console, shown on a restaurant portfolio, with filters and a location leaderboard. It is designed to compare occupancy and waitlist demand across centers.
Pitch kit
Your centers already know what matters: which children are signed in, who is cleared to be counted, what a family asked this morning, what a child learned today and whose co-pay changes next month. Burdenoff brings CrewFoundry, BuildMyIQ, FluidGrids, Botlit, ComradeCircle, Subscriber Bot, BigConsole and CollabKin together, designed so each piece reaches the person who can act, with children's information seen only by those who need it.
Questions
Access is designed to follow each person's role: teachers see their room, directors their center, the owner the whole group and families only their own child, with one record of who did what. Photos are checked against each child's photo release before sharing, and each room's ComradeCircle group is invite-only. The products are pre-launch, and none claims third-party certifications.
Technical detail
Every product runs on Burdenoff Workspaces, so access is role-based, and the products are designed so that a teacher sees their room, a director their center, the owner the group, and a family only its own child. Every action lands in one audit trail. BuildMyIQ is designed to hold minors' data to a higher bar, with privacy-by-design handling of consent, retention, access and deletion. Photos are designed to be checked against each tagged child's photo release before they are shared, Botlit is designed to hand questions about a specific child to staff rather than answer them, and each room's ComradeCircle is invite-only. As pre-launch products, none of them claims third-party certifications.
No. No software can guarantee compliance, and your licensing rules and judgment still decide. The products are designed to make gaps visible earlier: ratios you set for each room, only cleared and trained staff counted, and each staff file item shown with its date and who checked it.
Technical detail
No software can guarantee compliance, and nothing here replaces your licensing rules or your own judgment. The design intent is visibility: CrewFoundry is designed to apply the ratios you configure for each room and to count only staff whose clearances and training are current, and the clearance record is designed to show each staff file item with its date and verifier. Your director and licensing consultant still decide; the products are designed to make gaps visible earlier.
No. Each product works on its own and they share one foundation, so a center can start where it hurts most, such as staff cover, family questions or tuition, and add more later without starting over. FluidGrids is designed to connect to tools you already use, so a new piece works alongside them while you decide what to replace.
Technical detail
No. Each product works on its own and they share one foundation, so a center can start where the pain is sharpest, such as the ratio roster in CrewFoundry, the family question desk in Botlit or tuition in Subscriber Bot, and add the rest later without re-platforming. FluidGrids is designed to connect to systems you already run through its connectors, so a new piece can work alongside your current tools while you decide what to replace.
Yes. Rooms, ratios, days and tuition plans are designed to be set per program. An after-school site can expect children at dismissal, bill drop-in days and holiday camp weeks, and send pickup changes straight to the site coordinator, while an infant room tracks safe sleep training and move-up dates.
Technical detail
Yes, by design. Rooms, ratios, day patterns and tuition plans are configured per program, so an after-school site can expect children by dismissal time, bill drop-in days and holiday camp weeks, and route a note about a child going home with someone else straight to the site coordinator, while an infant room tracks safe sleep training and move-up dates.
No. Each product keeps its own name, and we do not rebrand products or build custom versions. You set your own content and rules, such as rooms and ratios, the handbook Botlit answers from, waitlist order and tuition plans, and families see your center's information inside each product.
Technical detail
No. Each product is offered under its own name, and we do not rebrand products or build bespoke versions. What you configure is your content and your rules: rooms and ratios, the family handbook and closure calendar Botlit answers from, the waitlist priority order in FluidGrids and the tuition plans in Subscriber Bot. Families see your center's information inside the product.
AI answers family questions; people decide. Botlit is designed to answer only from the documents you give it, show sources, say when nothing matches and hand anything about a child to staff. Waitlist offers follow your team's order, directors review incident reports before families hear, and teachers write and approve every summary; nothing assesses or diagnoses a child.
Technical detail
AI is designed to answer from your own documents and to suggest; people decide. Botlit is designed to answer only from the handbook, calendar and policies you load, show its sources, say when nothing matches and hand anything about a specific child to staff. Waitlist offers are designed to follow priority rules your team writes and tests in FluidGrids. A director reviews each incident report before a family is notified, and nothing in this solution assesses or diagnoses a child: teachers write and approve every observation and conference summary.
Related domains
Public & SocialChallenges solved
A solution concept that brings eight Burdenoff products together for schools, universities and bootcamps: early alerts, faster feedback, belonging, student services, proof of skill and focus.
Finance & BusinessChallenges solved
A solution concept for HR, staffing and workforce planning: skills-based hiring, bench redeployment, mandatory training, aggregate workload signals and one access-controlled workforce plan.
Consumer & LifestyleChallenges solved
How eight Burdenoff products are designed to help a household run its money, its home, its time, its learning and its family story together.
Tell us about your setup. We will walk you through the products involved and scope a pilot around the challenge that hurts most.
This is a solution concept: it shows how Burdenoff products are designed to work together in this industry. The images are illustrations of the concepts, not screenshots of the actual products, and every name and figure in them is sample data.
