SaaS vs Custom

Family Day Care (FDC) scheme: coordinator manages network of 60+ educators (each running care from their own home), ~180 children total, fortnightly billing, no single software handles it well. Picture: Coordinator Rachel manages educators across Brisbane suburbs (Paddington, Fortitude Valley, Kangaroo Point, Woolloongabba), each educator independent contractor, each caring for 4–6 kids max per home. Current chaos: educator vetting scattered (Working With Children Check from myWWCC portal, state police check, TB test result, insurance document = 5 files per educator, spreadsheet tracking who's current), child enrolment manual (parent fills paper form, Rachel enters into spreadsheet, assigns to educator, duplicates everywhere), CCS claims are brutal (monthly Child Care Subsidy claims submitted manually, Rachel collates attendance per child per educator, submits 180 separate claims to DET, 40% of them incorrect formatting, resubmitted 3 weeks later), carers-to-child ratios untracked (FDC Regulation 2018 requires: 1 carer + 1 assistant care for max 7 children; Rachel doesn't know if educator Sarah (home with 6 kids, assistant Joyce left, assistant never hired) is operating over-ratio, liability exposure), fortnightly invoicing chaotic ($180/week per family × 180 families = $32.4k revenue, Rachel manually sends 180 invoices via email, 30% late payments, zero automation), emergency contact tracking fragmented (parent lists emergency contact on paper form, Rachel types into spreadsheet, educator's copy lost, incident scenario: child injured, educator needs parent contact, checks paper note from 2 years ago, parent phone number changed, can't reach anyone, incident escalates).

Six Features Custom FDC Platform Delivers

1. Educator Vetting + Compliance Dashboard — WWCC, Insurance, Training, Expiry Alerts

Custom system: [Educator Registry]. Coordinator Rachel logs in, sees: "60 educators, 52 fully approved (WWCC valid, insurance current, training current), 8 pending renewal." Click educator Sarah: "Working With Children Check: Expires 30 Sep 2026 (104 days). Insurance: Professional Indemnity ($2M cover), expires 28 Feb 2027. TB test: Current (expires 30 Jun 2027). Approved to care: yes. Ratio: max 7 kids. Current enrolments: 5 kids. Ratio status: compliant." System auto-alerts Rachel: "60 days before WWCC expiry (Sarah's), send alert email." Rachel emails Sarah: "WWCC renewal reminder—expires 30 Sep 2026. Renew via myWWCC (free, takes 15 mins). Reply confirmation when done." Sarah renews, uploads new WWCC document, system auto-verifies (document scanned, WWCC number matched to state register via API integration), system updates: "WWCC renewed, valid until 30 Sep 2031." Rachel's dashboard: "100% compliance: 52/52 educators WWCC valid, 52/52 insurance current, 52/52 training current. Last audit: today. Next alert: educator Emma's insurance expires 45 days." System prevents: employing non-compliant educator. Rachel tries to assign new child to educator Tom (WWCC expired, red flag), system blocks: "Tom's WWCC expired 10 Aug 2026. Cannot enrol children until renewed. Contact Tom." Compliance = operate without regulatory interruption. Value: vetting automation saved 3 hrs/week (calling educators, chasing documents, spreadsheet updates) × $25/hr × 48 weeks = $3.6k labour, plus prevented compliance breach (regulatory fine $5k–20k) = $3.6k–20k avoided.

2. Child Enrolment + Educator Assignment — Online Forms, Parent Self-Service, Zero Paper

Custom system: [Enrolment Portal]. Parent Michael logs in, sees: "Enrol your child for Family Day Care. Choose educator & start date." Michael selects: daughter Amelia, 3 years old, start date 1 Jul 2026. System shows: "Available educators: Sarah (Paddington, 5 kids enrolled, max 7, 2 spots open), Emma (Fortitude Valley, 4 kids, 3 spots open), Joyce (Kangaroo Point, 6 kids, 1 spot open). Choose educator or request nearest match." Michael picks Sarah (Paddington, close to home), confirms: "Amelia enrolled with Sarah, 1 Jul 2026. Fortnightly fee: $360 ($180/week × 2). Start date: 1 Jul. Payment: auto-charged fortnightly to card ending 4532." System sends: confirmation to Michael (enrolment summary, terms), confirmation to Sarah (new child Amelia arriving 1 Jul, profile, allergies, emergency contacts), confirmation to Rachel (enrolment processed, Amelia linked to Sarah, 1 child added to FDC scheme). Rachel's dashboard updated instantly: "Total children: 180 (was 179). Sarah's enrolments: 6 (was 5). Revenue: $32.4k/fortnight (was $32.28k)." Zero paper, zero re-entry, zero duplicates. System prevents: assigning child to over-ratio educator (Michael tries to enrol second child with Sarah who now has 6, system blocks "Sarah at max capacity"). System handles: flexible start dates (mid-week, mid-fortnight billing prorated). Value: enrolment processing saved 1.5 hrs per family × 180 families = 270 hrs/yr = 270 ÷ 48 weeks ÷ 5 days = ~1 hr/week × $25 = $1.2k labour saved.

3. Child Care Subsidy (CCS) Submission — Attendance Per Educator, Bulk Claims, DET Portal Integration

Custom system: [CCS Portal]. Australia's Department of Education pays subsidy to FDC coordinator (not educator directly) per session attended, capped max 100 days/year per child. System tracks: daily attendance (Amelia attended Sarah's care Mon 1 Jul 2026, full day, counts as 1 day toward CCS entitlement). Monthly, system auto-generates: CCS claim form per child per educator (180 children × up to 60 educators = 1,080 potential claim lines). Rachel logs in, sees: "CCS claims ready for submission. July 2026: 172 families eligible, 580 sessions attended, est. subsidy $13.9k (50% × $27.8k fees). Review & submit." System displays: per-family breakdown (Michael's family: Amelia attended 20 days July, eligible for $180 subsidy if family income under threshold; claim submitted). Rachel reviews, clicks submit, system auto-uploads all 1,080 claim lines to DET via secure API (zero manual entry, zero form PDF filling). System tracks: submission status ("submitted 1 Aug, confirmed 8 Aug, $13.9k subsidy received 15 Aug"). DET audit: system stores all sessions, attendance records, educator assignments, invoices for 7 years (compliance). FDC Regulation requires: attendance records auditable, subsidy claims reconciled annually. System generates: "Annual CCS reconciliation: 2025–26 FY. Total subsidy claimed: $166.8k (52 weeks × $3.2k/week). Total subsidy received: $166.1k (99.6% accuracy). Variance: $700 (educator leave 1 week, no sessions, system flagged zero claims). Audit ready." Value: CCS claim processing automated (manual: Rachel spending 4 hrs/week × 48 weeks = 192 hrs/yr at $30/hr = $5.76k labour; custom reduces to 1 hr/week = $1.44k, save $4.32k) + subsidy claim accuracy (manual submission loses 5–10% to formatting errors = $8.3k–16.6k recovery via correct claims) = $12.6k+/yr value.

4. Carer-to-Child Ratios + Educator Assistant Tracking — Real-Time Compliance, Alerts, Audit Trail

Custom system: [Educator Capacity Dashboard]. Rachel sees: "Ratio compliance (FDC Regulation 2018: 1 carer + 1 assistant per 7 kids max). Sarah (Paddington): 6 kids enrolled, 1 assistant (Joyce), ratio 6:1 = compliant. Emma (Fortitude Valley): 3 kids enrolled, 0 assistants, ratio 3:1 = compliant. Joyce (Kangaroo Point): 6 kids enrolled, assistant not assigned yet, ratio 6:1 (at max, no more enrolments until assistant hired). System alert: Joyce needs assistant urgently (next child assigned would breach ratio)." System prevents: over-ratio breach. New parent David tries to enrol son Kai with Joyce (currently 6 kids), system blocks: "Joyce at max capacity (6 kids, no assistant). Kai wait-listed (1 spot). Joyce must hire assistant to accept next child. Or choose different educator: Sarah (2 spots), Emma (3 spots)." Educator lifecycle: Sarah hires assistant Joyce (replacing her daughter who left), Rachel updates system: "Sarah's assistant: Joyce, WWCC valid, insurance current, training verified. Ratio updated 6:2 = compliant. Enrol next child." System tracks: per-day ratio (some educators run part-time; Sarah open Mon-Wed only, Rachel notes "Sarah's sessions: Mon 7am–6pm, Tue 7am–6pm, Wed 7am–6pm, closed Thu-Fri. 6 kids enrolled, attendance varies, Mon: 6 kids (6:1 at max), Tue: 4 kids (4:1), Wed: 5 kids (5:1). All days compliant"). Regulatory audit: system provides: "1 Jul–30 Sep 2026: 65 working days. Ratio compliance: 100% (zero over-ratio days, all educators 1:7 or better). Educator roster attached (each day, which educators, which assistants, which kids, all in compliance). Audit ready." Value: ratio tracking prevented potential breach (regulator closure risk $50k+ revenue loss, reputation damage) + zero compliance anxiety (Rachel knows in real-time she's safe) = priceless for peace of mind + insurance might reduce premiums if automated tracking documented = $2k–5k/yr.

5. Fortnightly Billing + Payment Recovery — Auto-Invoice, Recurring Payments, Late-Fee Enforcement

Custom system: [Billing Portal]. 180 families, $360 fortnightly per family (average) = $64.8k revenue every 2 weeks. System auto-generates invoices: fortnightly on Thursday (for following Mon–Sun care). Michael's invoice: "Amelia with Sarah, 1–14 Jul, 10 session days (Mon, Tue, Wed, Thu, Fri × 2 weeks), $360. Due: 14 Jul. Paid via recurring card on file ending 4532: 11 Jul, $360. Status: paid." System sends: invoice PDF to Michael's email on Thu, payment processed Fri (48-hour advance, reduces weekend cash flow stress), payment confirmation Mon. System tracks: payment status. Out of 180 families, typically 95% pay on-time (Friday auto-charge). Remaining 5% (9 families) miss payment: system auto-sends reminder: "Invoice $360 due 14 Jul, payment not yet received. Pay now (link) or call 07 3000 1234. Overdue payment incurs $15 late fee after 5 days." Defaulters David & Kai (late by 1 week, $15 late fee applied), Rachel calls David: "Kai's care invoice is overdue 1 week. Unpaid: $375 ($360 + $15 late fee). Can you pay today?" David: "Card expired, updating now." System re-attempts charge, succeeds. Revenue recovered. Serious defaulter: educator James's 4 families (~$1.4k/fortnight), 3 don't pay for 4 weeks (owed $2.8k), Rachel suspends care: "Care suspended until arrears cleared. Pay $2.8k to resume." 1 family pays, care resumes. 2 families pay week later (late fee $30 each added). System tracks: "Fortnight 1 Jul–14 Jul: invoiced $64.8k, paid $61.5k on-time (94.9%), 9 families late (average 5 days late), $135 late fees collected, 1 family pay-plan (split $360 over 3 weeks starting week 2, system auto-charges $120 × 3). Net collection: $61.635k (95% cash realized, zero debt older than 30 days). Annual: $1.6m revenue, $1.52m collected (95% + late fees = net positive $7.5k from enforcement)." Value: billing automation (manual: Rachel 2 hrs/week sending invoices, chasing payments = $2.4k labour; custom reduces to 0.5 hrs/week = $0.6k, save $1.8k) + payment recovery (late-fee enforcement collected $7.5k annually) + working capital (payments in Friday vs Monday, $64.8k floats only 3 days vs 10 days manually = $17.28k improved cash float = finance cost savings @ 5% = ~$864/yr) = $10.2k/yr total benefit.

6. Emergency Contact + Medical Profile Tracking — Centralized Registry, Incident Response, GDPR Privacy

Custom system: [Child Profile Registry]. Amelia's profile: "Emergency contacts: Michael Wood (0412 567 890, father), Sarah Wood (0487 123 456, mother), Grandpa Robert (0400 111 222, backup). Medical: allergies (peanuts—severe, EpiPen required), asthma (reliever inhaler, blue puffer at carer's home), immunization (up-to-date, booster 15 Dec 2025). Dietary: vegetarian (no meat). Special needs: none. Language: English (first language), Mandarin (grandmother speaks)." Sarah (educator) logs into mobile app, sees: Amelia's profile on-screen (allergies, medical, emergency contacts, photo). Scenario: Amelia has minor allergic reaction (rash), Sarah checks app: "Peanut allergy—mild rash expected, monitor. Severe reaction = EpiPen. Contact Michael immediately if worsening." Sarah gives Amelia antihistamine (parent approved, pre-stock in carer's home), rash subsides. Sarah texts Michael: "Minor reaction today, managed at home, all good now." Michael informed, picks Amelia up, no incident escalation. Serious scenario: Amelia has anaphylactic reaction at Sarah's home (cross-contamination from peanut-free muesli bar). Sarah scans app: "Amelia: peanut allergy (SEVERE), EpiPen location: kitchen top drawer (labelled 'Amelia's EpiPen'). Emergency contact: Michael 0412 567 890." Sarah gives EpiPen (self-injector), calls ambulance (000), ambulance arrives 4 mins later. Paramedics receive: system-generated printout (Amelia's name, age 3, allergies, EpiPen administered, medical history, parents' contact). Hospital discharge: all documented. System records: "Incident 15 Sep 2:45pm, anaphylaxis, EpiPen administered by Sarah (carer) at 2:46pm, ambulance arrived 2:50pm, transported to hospital, discharged same-day." Rachel (coordinator) receives incident notification (system alerts), reviews: "Incident response: Sarah followed protocol (EpiPen administered, ambulance called, parents notified). Amelia safe. System audit trail confirms duty of care." Insurance claim: system provides full documentation (allergies documented, EpiPen procedure, incident timeline, staff trained). Insurance accepts, zero dispute. Regulatory audit (ACECQA): inspector asks "Allergies tracked?" Rachel shows system: "Amelia's allergies documented, incident log, response protocol followed, zero liability. System generates NQS-compliant incident report on demand." Data privacy: system APPs-compliant (no third-party access, photos encrypted, parent consent required, zero data shared externally). Value: emergency contact system prevented serious incident escalation (hospital cost $2k–5k if EpiPen delayed, lawsuit risk $50k+ if allergies were missed, custom system proves duty of care) = $50k risk avoided + insurance premium negotiable (automated compliance = lower risk profile = $500–2k/yr premium reduction) = $500–2k annual saving.

FDC Network ROI: 60-Educator Scheme, Year 1 Break-Even, Year 2+ $45k/yr Profit

Build cost: $72k (educator registry + enrolment portal + CCS automation + ratio tracking + billing system + emergency contacts + mobile app for carers). Year 1 ops: $5k/yr (hosting, payments, support). Total Year 1 investment: $77k. Value captured: (1) Manual labour elimination (Rachel 3 hrs/week educator admin + 4 hrs CCS processing + 2 hrs billing + 1 hr compliance = 10 hrs/week × $30/hr × 48 weeks = $14.4k; custom reduces to 2 hrs/week = $2.88k, save $11.52k). (2) Payment recovery (late fees + compliance = $7.5k/yr from enforcement + working capital float improvement = $864 = $8.36k). (3) CCS accuracy (prevent 5–10% claim losses = $8.3k–16.6k recovery, conservatively $12.5k). (4) Compliance + ratio safety (prevent regulatory breach $5k–20k risk, insurance premium reduction $500–2k, conservatively $5k). (5) Educator retention (system transparency = educators trust coordinator, no manual chaos = reduced turnover; educator replacement cost ~$3k onboarding + recruiting, avoid 2 replacements = $6k). Year 1 total value: $11.52k + $8.36k + $12.5k + $5k + $6k = $43.38k. Year 1 net: $43.38k - $77k = -$33.62k (build cost). Year 2: value repeats ($43.38k) minus build, net $38.38k profit. Year 3+: $38k+/yr pure. Break-even: 22–26 months. Growth upside: scale from 60 to 120 educators (double network, same platform, zero new build cost), Year 2+ profit $75k+/yr. Conservative scenario (60 educators, static): Year 3 onwards, $38k/yr pure profit on $1.6m annual revenue = 2.4% margin improvement (significant for non-profit schemes). Want ROI modelled for your educator count? Check platform pricing or book a call—we'll handle educator vetting, child enrolment, CCS claims, carer ratios, fortnightly billing, emergency contacts, FDC Regulation compliance, and ACECQA National Quality Standard audit readiness.

Six FAQs

What is Family Day Care (FDC) and how does it differ from centre-based childcare?

Family Day Care is home-based care: single educator (or educator + assistant) cares for max 7 children (FDC Regulation 2018) in their own home (not a formal centre). Model: FDC scheme coordinator manages network of educators (60–100 across a region), educators are independent contractors (employed by coordinator or self-employed, varies by scheme). Families access care flexibly (part-time, full-time, casuals). Coordinator handles: recruitment, vetting (WWCC, police check, TB test, insurance), invoicing families, paying educators, CCS claims, regulatory compliance. Differs from centre-based (e.g. long day care): FDC is intimate, home environment (children see same educator daily, fewer transitions, often sibling-like grouping); centre-based is institutional (40–80 kids across multiple rooms, high staff turnover, regulation heavier). FDC is cheaper for families ($180/week vs $250+/week centre), educators like autonomy (own home, own pace), coordinators like low overhead (no building rent, shared educators across families). Regulatory: both ACECQA-assessed, both need NQS compliance, FDC slightly lighter (no physical environment audit as strict, but carer background checks equally strict). Australia: ~40k FDC children (~8% of childcare market), 5k+ FDC schemes nationwide.

What does ACECQA registration mean and why must FDC coordinators be compliant?

ACECQA (Australasian Children's Education Care & Quality Authority) is the national regulator for early childhood education + care (ECEC), including FDC. Registration: FDC coordinator must be registered (applies once, fee ~$350, lasts indefinitely with annual compliance). Registration requirements: approved provider (coordinator identified, responsible person declared), NQS assessment (10 quality standards, unannounced audits every 2–5 years), working with children checks (all educators WWCC valid), incident reporting (serious incidents reported to ACECQA within 24 hrs), quality improvement plan (coordinator demonstrates continuous improvement). Non-compliance: first breach = regulatory notice (0–3 months to fix), second breach = unannounced audit, failure = suspension or cancellation (no care operation allowed). FDC risk: if regulator finds educator was non-compliant (expired WWCC, no insurance, unvetted assistant) and child incident occurred, coordinator liable (not just educator). Custom system ensures: WWCC tracking, expiry alerts, insurance verification, audit readiness (system generates compliance report on demand). Compliance = operate without interruption, reputation intact, insurance accepted, zero liability gap.

How does Child Care Subsidy (CCS) work for FDC and how much revenue is available?

CCS: Australian government subsidizes eligible families up to 50% of verified fees (capped ~$7.96/hr per child, max $12.6k/yr per child under current rules). FDC-specific: subsidy paid to FDC coordinator (not educator), coordinator passes payments through to families or retains as administrative fee. System captures: daily attendance (Amelia attended Sarah's care 1 Jul 2026, full day = 1 day toward CCS entitlement). Maximum: 100 days/year per child (school holidays + term care). Monthly, coordinator claims per child per educator (e.g. Amelia attended Sarah 20 days in July, eligible for subsidy if family income under $256k/yr threshold, subsidy = 50% × verified hourly rate × hours attended). 180 kids × 240 days/yr average (accounting for holidays, absences, part-time) = 43,200 day-sessions/yr. At 50% subsidy = $166.8k/yr potential CCS (if all families eligible at max rate). Manual coordinator loses $50k+/yr in missed claims (delayed enrollment, incorrect formatting, resubmission delays). Custom system: auto-claims per attendance record, DET portal integration, zero manual entry. System also ensures: family eligibility checked upfront (system integrates CCS gateway for income verification), claims match attendance (zero false claims), audit trail perfect (7-year archive). Verdict: coordinator not claiming CCS regularly is leaving $166k on the table; custom system captures it all.

Can the system handle educators with varying availability (part-time, casual backup, multi-scheme)?

Yes. Educator Sarah: "Available Mon–Wed 7am–6pm (full-time, 3 kids enrolled). Closed Thu-Fri (personal days)." System schedules: Sarah's sessions M-W only, parents can't book Thu-Fri with Sarah, system shows "Sarah closed." Educator Emma: "Available Mon-Fri 8am–4pm (part-time, max 3 kids, 2 enrolled)." System schedules: Emma's sessions M-F 8–4, backup availability: "Can accept casuals Sat-Sun if needed (weekend program)." Educator James: "Multi-scheme: mornings with Coordinator Rachel's FDC (Fortitude Valley), afternoons with Coordinator Lisa's FDC (Kangaroo Point, separate system)." System: Rachel's platform tracks James's morning availability (morning kids), Lisa's platform (separate FDC scheme) tracks afternoon availability. Separation enforced (no cross-scheme double-booking). Billing: Rachel invoices families for James's morning care, Lisa invoices hers separately. Payment recovery: both coordinators independently track James's kids. CCS claims: both claim separately (James's care split per coordinator). Advantage: James flexible income (both schemes pay fortnightly, combined income stable). System handles: educator switching schemes (James stops with Rachel, resumes 6 months later, re-vetting not required if WWCC still valid, system re-activates profile). Casuals: educator David available "as-needed backup" (zero kids enrolled normally, paid per session when called in). System: Rachel texts David "Need backup Tue 2–5pm?" David confirms, system books, tracks attendance (David attended, 3 hrs, paid casual rate $35/hr = $105). Invoices David after session, system auto-pays. Value: flexible educator scheduling = network can absorb demand spikes without hiring permanent (cost control) + educators appreciate autonomy (retention improves).

What happens in a serious incident (injury, allergic reaction) and how does the system protect coordinator liability?

Incident scenario: child Kai (age 4) has allergic reaction (peanut cross-contamination). Educator Emma (Kangaroo Point) scans system: "Kai: peanut allergy (SEVERE), EpiPen required. Emergency contact: David (father) 0412 567 890." Emma gives EpiPen (self-inject, pre-positioned in home), calls ambulance (000), ambulance arrives 5 mins. Kai transported to hospital, discharged same-day with observation note. System records: incident report (timestamp 2:45pm, location Emma's home, incident type: allergic reaction, action taken: EpiPen administered, ambulance called, parents notified, outcome: hospitalized, discharged). Coordinator Rachel notified (system alert). Rachel logs in: "Incident involving Kai, Emma's care. Kai safe. System audit trail: allergies documented (dated entry), EpiPen procedure on-file, Emma's training verified, incident response recorded." Rachel sends incident summary to David: "We're sorry Kai had a reaction. Emma responded immediately (EpiPen given, ambulance called). Kai discharged, no ongoing concerns. We've reviewed Kai's food preparations to prevent recurrence. Any questions, call me." David: "Thanks, understood, Kai's fine." No complaint. Insurance claim: Rachel submits (system documentation): "Kai's allergies documented, EpiPen procedure, Emma trained, response within protocol, incident resolved appropriately." Insurance accepts. ACECQA audit (regulator): inspector asks "How do you manage allergies?" Rachel shows system: "All allergies documented, incident log, response protocol, zero incidents unresolved, duty of care documented. Audit ready." Regulator: "Excellent, no action needed." Liability protection: system proves coordinator exercised due diligence (documented allergies, trained educators, incident response followed protocol). If lawsuit filed (unlikely if Kai's safe), system documents coordinator's care, zero negligence. Conversely, manual coordinator (spreadsheet allergies, incident not logged): regulator sees gaps, liability exposure massive. Custom system = regulatory-grade incident defense.

Can the system scale to multiple FDC schemes or transition to centre-based care?

Yes to multiple schemes (limited). Scenario: Rachel manages FDC scheme 1 (60 educators, 180 kids), Lisa manages FDC scheme 2 (80 educators, 240 kids). Two separate custom platforms (system per coordinator, independent databases, zero shared data). Rachel's system: 60 educators, 180 kids, $1.6m/yr revenue. Lisa's system: 80 educators, 240 kids, $2.1m/yr revenue. No cross-coordination (Rachel doesn't see Lisa's data, vice versa). Benefits: isolated operations (liability walled off per scheme), separate CCS submissions (DET tracks per provider), independent compliance (each scheme audited separately). Scaling: Rachel expands to 120 educators (double network), same platform (zero new build), ops cost stays $5k/yr (mostly hosting = scales linearly, cheap). Alternative: Rachel & Lisa merge schemes (combine into 140-educator mega-FDC), consolidate to single platform (one system, one budget $5k/yr, combined $3.7m revenue). Data migration: educator profiles, child enrolments, billing history all migrate, zero loss. Centre-based transition: Rachel decides to open a formal long day care centre (50 kids, single location, staff employees, not independent contractors). System doesn't fit (FDC = distributed homes, centre = single building). Coordinator switches to OSH/centre-based SaaS (Xplor, Governess, Kinderloop). New platform required (re-implementation cost ~$40k). But: if Rachel keeps FDC + opens centre, two separate platforms (FDC for home educators, centre SaaS for building care). Revenue synergy: FDC graduates to centre's before-school program (same families, same platform potential if custom system spans both). Verdict: custom FDC system ideal for pure FDC, scales horizontally (more educators, same platform), but not designed for centre transition (different regulatory model, different architecture).

What's the difference between FDC software and generic childcare bookings platforms like Eventbrite/Care.com?

Eventbrite/Care.com: designed for one-off services (event tickets, babysitter marketplace). Per-transaction fee 3–5%, zero recurring features, no compliance. FDC is recurring (fortnightly term-based), high-volume (180 kids, 60 educators), regulatory (ACECQA compliance, NQS standards, CCS claims, educator vetting, ratio enforcement). Generic platforms can't: vet educators (no WWCC tracking, no police check integration), manage CCS claims (Australia-specific subsidy, complex DET submission), enforce carer-to-child ratios (FDC Regulation requirement), track emergency contacts + allergens reliably (incident prevention critical), generate NQS audit reports (compliance). Eventbrite for 180 kids × 52 weeks = 9,360 bookings/yr @ 3% transaction fee = $280.8k × 3% = $8.4k in fees (vs custom $5k ops = $3.4k save annually, but zero FDC-specific features). Care.com: babysitter marketplace (matches sitters to families, zero FDC scheme coordination). FDC coordinator Rachel needs: educator vetting (WWCC, insurance, training), network oversight (60 educators, 180 kids under one brand, Rachel responsible), CCS claims (Rebecca submits en-masse, auditable). Care.com doesn't do any of this (designed for one-off sitter hires, not recurring scheme management). Custom FDC platform: all-in pricing ($5k/yr ops), term enrolment (predictable, not transactional chaos), educator vetting (compliance automated), CCS automation (recovery $12.5k/yr), ratio enforcement (liability protection), billing (fortnightly recurring, payment recovery built-in). Verdict: if you're running FDC scheme, custom is 8–10× cheaper + regulatory-proof + makes you money. Generic booking platforms are cost centers for transactional overhead; FDC custom is profit engine for growing schemes.