Tuition and meals are bundled into one system — so royalty is charged on both.
Daycare Works (DCW) is your system of record: enrolments, programs, family records and Monday billing through Tuition Express. The meal fee sits inside that same balance. That single fact creates the cost.
💰 The money leak — every year
Royalty — including the brand fund — paid away on meal fees alone, on money that simply passes through the school to the caterer. This estimate is based on an average of $25 per child per week. Here’s the maths — and you can adjust the assumptions yourself with the sliders below:
The school saves the amount it was paying on royalty on pass-through cost.
Tuition stays in DCW at new meal-free rates. The meal fee is collected separately via GoCardless every Monday, based on the coming week’s schedule. Two charges, same total, clear purpose for each.
Meal-free rates in DCW, collected as today via Tuition Express.
$6 × days attended that week, per family. Siblings combined under one payer.
Two labelled charges instead of one bundled amount. No new total to explain.
Meal money is a pass-through collection outside DCW — no royalty charged on it.
Net saving — after running costs (estimates)
rising to ~$21,500 / year at full capacity (230)
| Gross royalty avoided on meal fees — $13,520 on $169,000 / yr of meal fees (130 × $25 × 52), at 8% royalty including the brand fund | ≈ +$13,000 |
| Less: GoCardless processing — Standard plan, 0.5% + $0.05 per debit, across ~6,760 debits / yr | − $1,183 / yr |
| Less: Show school’s own name on parents’ bank statements (recommended, $25/mo) | − $300 / yr |
| Less: Failed-payment fees — variable, $5 per failed debit | Small / variable |
| Net recurring saving at current enrolment | ~$12,000 / yr |
At full capacity (230 children, same assumptions): meal volume rises to $299,000 / yr, the leak to $23,920 / yr, and the net saving to roughly $21,500 / yr after processing and the statement-name option. Why GoCardless fits this pattern: many small weekly debits. At 0.5% the percentage is similar to alternatives — the difference is the fixed fee: $0.05 per debit on Standard vs $0.25 elsewhere. That $0.20 gap, multiplied by thousands of weekly debits, is the saving. All figures are estimates based on the adjustable assumptions in Section 01 and will be firmed up once sample reports confirm actual debit counts and exclusions.
Six phases. Each one removes an unknown before money moves.
We don’t price or build on assumptions. Verification comes first, charging comes last — with a test run in between so the first live Monday is boring.
Verify First step
Sample DCW exports settle everything the build depends on.
- Find the DCW reports that give us the children, their parents, and who pays for each child.
- Verify those reports can be scheduled automatically and contain everything needed to bill the payer for meals separately.
Master Data Build Foundation
Create a master file that contains all the details for each child, including the bank information needed for ACH payments.
GoCardless Setup
GoCardless account opened in the school’s name, plan and statement descriptor set up. Master sheet populates customers + bank accounts via API.
Build
We build a small platform that sits in the middle. Each week it receives the charge report from DCW, works out the meal charge for each child, and then instructs GoCardless how much to deduct for each child.
The new meal-free tuition rates are also prepared in DCW at this stage (in bulk, via the DCW Rate Sheet Import), ready for go-live.
Test
A mock run for 2 weeks. The system works out the meal charges exactly as it would live — but without actually charging anyone.
We compare the results against the meal portion inside the current DCW billing, to make sure the system is acting as expected and catch any quirks on real data before go-live.
Go-Live
DCW charges the lower tuition. GoCardless charges the meal fee. Parents see two charges for the same total.
We deliver two reports to the school:
- Daily exception report: Lists every family that needs attention that day — a new family not yet set up, a failed or returned debit, or an amount that doesn’t match — with the reason and what is needed to fix it, so nothing is ever charged incorrectly or silently missed.
- Weekly summary report: One summary for the week — how many children were charged, the total meal fees collected through GoCardless, the processing fees, and the royalty saved that week, with running totals.
What we need to start Phase 0
Sample DCW exports from Stephanie (billing / schedule report + Family Pay Transaction report + last-4 view). That’s all Phase 0 needs to get moving.
The things we should surface now — not discover at go-live.
None of these block the project. Each one is a short conversation or a quick decision between us — and all of them are cheaper to settle early than at go-live.
Point 1 — Confirm the meal rules
A short sit-down to agree exactly how the $6/day fee applies, so the weekly calculation matches the school’s practice:
- Which programs and days the fee covers
- How absences, holidays and school closures are handled
- Any children the fee doesn’t apply to (e.g. infants or part-time schedules)
Point 2 — Sample DCW reports Phase 0
- Get the report names from DCW which contains the data needed for this project
- Scheduled-report criteria freeze once set; a rolling “next week” window isn’t documented
- Sample exports from these reports
Point 3 — Paper forms
The account details for each child in the master sheet need to come from the paper forms. The most optimized way of getting these details into digital form can be discussed.
Bottom line: Everything above is a short conversation or a sample file away. Settling these early is the simplest way to keep the project moving and make the first live Monday uneventful.
What it costs
Simple, predictable pricing — structured around the saving, not around hours.
1 Fixed build price
A single fixed price for the build, quoted after the Phase 0 verification — once the real DCW reports have been seen and there are no unknowns left to price around. No hourly billing.
2 Payback
The pricing is structured so the build pays for itself within the first year from the royalty saved — with the saving recurring every year after.
3 Paid in two milestones
Part on signing, the rest on go-live — so payment follows progress, not promises.
4 Small monthly care fee
Covers running the system day to day: the platform, monitoring, the daily exception report and the weekly summary report.