SaaS vs Custom

A 12-teacher music school in Australia (800+ active students, 500+ lessons/month, 60% aged under 18, 30% exam candidates, 10% NDIS-funded) pays $19-29/teacher/month on MyMusicStaff (2.7-4.2k/yr licensing) or $30-45/month on Tutorbird Music (4.3-6.5k/yr). Parent request: "How is Emma doing at piano? Is she ready for AMEB Grade 3?" Teacher scrolls email history (60+ emails from parent from past 8 months), checks practice diary that Emma's parent scribbled (legible notes are sparse), recalls "Emma had trouble with hand position week 4, improved week 7, did well on scales last lesson"). Parent wants specific feedback, not vague memory. Student AMEB prep: 12 piano students are Grade exam candidates (Grade 1-5 across the student base). School admin tracks 8 students in a spreadsheet (Grade 1: 3 students, exam dates noted by hand, syllabus links emailed to parents). Other 4 students tracked in a different spreadsheet by a different teacher (data is fragmented). Exam date is next week for one Grade 3 student, but school admin forgot to email syllabus materials to parent (only realised 2 days before exam). Recital scheduling: school does 4 recitals/year (autumn showcase, winter concert, spring recital, end-of-year celebration). Booking students into recitals is done via email: admin sends email "Who wants to perform in June recital?" Teachers reply (some do, some don't). Admin manually lists 30 students, asks each teacher "Is your student ready?" Rehearsal scheduling requires 10+ follow-up emails (who's the guest pianist? what day is dress rehearsal? who needs to bring instrument case? who's sitting where on stage?). Instrument rental: 20 school violins are available to rent ($20/month). Parent asks "Can Emma rent a violin?" Admin checks manual spreadsheet (violin serial SN-042 is available, SN-043 is out with student who owes $40 for broken bridge). Admin forgets to charge parent the $20 rental fee this month (revenue leaks). End of year, 2 violins are unaccounted for (rental agreements aren't tracked, one student moved away and took the violin, another was returned but damaged and nobody logged it). Lesson notes: teacher writes notes in their own notebook or emails themselves. One teacher uses Evernote, another uses a Word doc. Parent wants to know "What should Emma practice?" Teacher has to open email, find note "Emma needs to work on scales and Prelude 2." Parent gets feedback only when teacher remembers to email. AMEB tracking: 3 students preparing for exams, but school has no centralized record. One teacher has a spreadsheet with exam dates + syllabus. Another teacher has exam dates in her calendar only. School admin doesn't know if students are on-track until 1 week before exam (too late to catch gaps). Student doesn't know they need to memorize a scale they haven't practiced. Compliance: staff includes teachers with Working with Children Check (WWCC) clearance. School keeps WWCC dates on a spreadsheet (expiry dates aren't flagged until 1 week before, risk of expired checks). One NDIS-funded lesson is weekly (NDIS agreement requires progress notes every 3 sessions), but school doesn't auto-flag this. Teacher forgets to submit progress note to NDIS by deadline (compliance issue). Custom booking platform: lesson booking is live (parent/student can book via app, available slots show in real-time, no email back-and-forth). Parent sees: "Piano with Emma's usual teacher: Mon 4pm, Wed 6pm, Fri 3:30pm available this week." Parent books Wed 6pm. Confirmation SMS sent: "Lesson confirmed: Piano, Wed 6pm with Sarah. Bring music book 3." Teacher sees: "Wed 6pm: Piano, Emma, focus on scales + Prelude 2 (per last lesson notes)." Lesson notes are per-instrument, per-student: teacher opens Emma's Piano Lesson Notes (private journal), writes: "14 June: Emma played scales well, hand position improving. Prelude 2: tempo is rushing, practiced with metronome, improve next week. Homework: scales 3x/day, Prelude 2 with metronome, watch Imogen Heap version for inspiration." Notes auto-sync to parent portal: parent reads "Emma's Progress: Scales progressing, Prelude focus this week, keep practicing with metronome!" (teacher summary is auto-generated, private notes stay private). AMEB tracking: admin creates "Grade 3 Exam Cohort" (3 students: Emma, Lucas, Sophie). Sets exam date 15 Sep, links to official AMEB syllabus (platform auto-loads Piano Grade 3 requirement: memorize 3 contrasting pieces, scales, aural). Admin assigns teacher: "Sarah: Emma, Lucas. Michael: Sophie." System auto-sends email to each teacher: "Your AMEB Grade 3 students exam is 15 Sep. Syllabus: [link]. Due today—confirm each student's 3 chosen pieces." Sarah replies: "Emma: Prelude 1, Sonata 2, Nocturne. Lucas: Sonatina, Etude 4, Minuet." System logs choices, creates progress tracker: "Emma — Prelude 1 (started, 40% learned), Sonata 2 (not started), Nocturne (started, 20% learned), Scales (practiced, 60% learned), Aural (not started)." Weekly, teacher updates progress: "Prelude 1: 60% learned. Sonata 2: started, 20%. Nocturne: 40%. Scales: 80%. Aural: 40%." Admin sees: "Grade 3 Cohort: 2 on-track (Emma, Lucas), 1 behind (Sophie — Scales only 50%, Aural not started, 6 weeks to exam)." Flags Sophie's teacher: "Sophie is behind exam targets. Recommend 2 lessons/week instead of 1 starting next week?" Recital scheduling: admin creates "June Recital 2026" event. Teachers invited (system shows list: "12 teachers"). Admin sets: "Performance slots: 30 (each student = 4 min performance, spacing for transitions). Rehearsal: Sat 1 June, 10am-2pm. Dress rehearsal: Sat 8 June, 2-5pm. Performance: Sun 9 June, 2-7pm." Teachers claim students: Sarah marks "Emma (Piano, Prelude 1, 4 min)." Michael marks "Lucas, Sophie." System auto-builds schedule: "Sun 9 June: Performance Order: [1] Emma Piano 2:00-2:04, [2] Lucas Violin 2:05-2:09, [3] Sophie Cello 2:10-2:14, ... [30] ...3:56-4:00 (5 min buffer between slots). Rehearsal rotations: Piano group Sat 1 June 10am-11am, Strings group 11am-12pm..." Admin sends email to parents: "June Recital Schedule: Emma performs Sun 2pm. Rehearsal Sat 1 June 10am (Piano). Bring music. Arrive 15 min early. Guest pianist: [Name], thank you note: send to [email]." All in one auto-generated email (no email chains, no confusion). Instrument rental: admin sets up rental pool: "Violin SN-042: $20/month, insured $500 (maintenance cap $100/yr). Violin SN-043: $20/month, insured $500. Cello SN-001: $35/month, insured $1000." Parent requests: "Emma wants to rent Violin SN-042." Admin checks app: "Available this week: Violin SN-042 (Thu - Sun available, then out from Mon-Wed). Violin SN-043 (fully available). Suggest SN-043? [Yes/No]." Parent chooses SN-043. System auto-generates rental agreement: "Violin Rental: [Student name]. Instrument: SN-043. Monthly fee: $20. Insurance: covered for $500 loss + $100 damage. Rental period: 3 months (renew or return end Aug). Terms: returned in playable condition. Late fees: $10/week." Agreement is signed digitally. Charge: $20 is auto-billed to parent account every month (no manual invoicing). Damage report: 1 month in, student drops cello case (oops), string is broken. Parent emails: "Strings broke, need repair." System prompts: "Report damage to Cello SN-001. Cost estimate: $50 (2 strings + labor). Covered under rental insurance? [Yes, charge $50 to parent]. [No, refund $20 this month to parent, offer repair discount 10% → $45]." Insurance log is built: "Cello SN-001, $50 damage claim, paid by parent insurance pool." End of year, school tallies: "4 violins rented avg 8 months/yr × $20 × 4 = $2.56k. Cello 2 rented avg 6 months/yr × $35 × 2 = $4.2k. Total rental revenue: $6.76k. Damage claims: 3 × avg $50 = $150 (minor). Unaccounted-for equipment: $0 (all logged)." Lesson progress archival: at end of year, teacher exports "Emma's Piano Lessons — 2026" (40 lessons, all notes, progress photos, practice videos uploaded by student). Archive is sent to parent as PDF (portfolio record, useful if Emma changes teachers or schools). WWCC compliance: admin adds staff member "Sarah" (teacher, WWCC expiry: 12 July 2026). System flags: 1 week before expiry date ("Sarah's WWCC expires in 7 days. Renewal must be submitted by 12 July to avoid breaks in service"). Sarah uploads renewed certificate, system updates ("WWCC: valid until 12 July 2029"). Audit trail is built: "Sarah: active 12 July 2023 — 12 July 2026 (clear), renewed 10 July 2026, active 12 July 2026 — 12 July 2029 (clear)." NDIS module: 2 lessons/week for student Lucas are NDIS-funded. Admin marks: "Lucas — Cello lessons: 2 lessons/week, NDIS-funded, report required every 3 sessions (9 lessons = 1 report due)." System tracks: "Lessons 1-3: submitted report 15 June ✓. Lessons 4-6: submitted report 29 June ✓. Lessons 7-9: report due 13 July (7 days remaining)." Teacher is auto-flagged 7 days before deadline: "Lucas NDIS report due in 7 days. Generate progress report: [link to form]." Teacher fills: "Lucas made strong progress in bow control, learned 2 new pieces, aural skills improving, goal is Grade 2 by end of year." Report is submitted, auto-archived. Compliance record is perfect (no missed deadlines, audit trail shows all submissions). Build cost: $60-100k. Year 1: $60-100k. Year 2: $2.5k hosting + $5k teacher app support = $7.5k. Break-even month 16-20, then pure savings ($2.7-6.5k licensing + $15k/yr from lesson note automation + $10k from exam prep efficiency + $5k from recital scheduling efficiency + $6.76k rental revenue improvement + $2k NDIS compliance improvement) = $41.96k/yr net positive.

Why MyMusicStaff & Tutorbird Music Fall Short for Schools with Exam-Heavy, Diverse-Instrument Cohorts

MyMusicStaff ($19-29/teacher/month, popular in AU): offers lesson booking, basic student progress notes, parent portal, but lacks: (1) Instrument-specific lesson tracking—system has a generic "notes" field, but doesn't separate "Piano notes" from "Violin notes" from "Voice notes." School with 10+ instruments (piano, violin, cello, flute, voice, drums, ukulele, guitar, clarinet, saxophone) has teachers writing notes in different formats, no consistency. If Emma studies piano with Sarah and cello with Michael, her progress isn't instrument-separated. Sarah writes "Scales went well," Michael writes "Intonation improving." Parent reads both notes but can't tell which instrument is which (confusing). Custom system: Emma Piano folder (separate from Emma Cello). Sarah's notes: "Piano: scales 4/5, Prelude 2 rushing, homework: metronome practice." Michael's notes: "Cello: bow control, posture, new piece next week." Clear separation, no confusion. (2) AMEB exam-grade tracking—MyMusicStaff doesn't have AMEB syllabus integration. School tracks exam prep in spreadsheet or email (scattered). Tutorbird Music has basic progress tracking but not exam-specific (no AMEB Grade 1-8, no memorization vs. sight-reading breakdown, no aural requirements). Custom system: "Grade 3 Exam" is a cohort type. System auto-loads: "Piano Grade 3: memorize 3 contrasting pieces (Baroque, Classical, Romantic), scales 3 octaves, aural test (intervals, chord progressions, simple dictation, modulations)." Syllabus is built-in. Teacher tracks: "Emma: Prelude (Baroque) 40% learned, Sonata (Classical) 20%, Nocturne (Romantic) 50%, Scales 70%, Aural 30%." No manual spreadsheet hunting. (3) Recital coordination is clunky—MyMusicStaff has "Events," but doesn't auto-schedule performance slots, rehearsals, or generate combined parent emails. School admin does this manually (10+ emails, easy to miss someone). Custom system: Recital event is created once ("June Recital, Sun 9 June, 30 slots, Sat rehearsal"). Teachers claim students. System auto-generates: schedule PDF (performance order, times, transitions), rehearsal schedule (group rotations), parent email (one per parent, includes all relevant info: performance time, rehearsal date, what to bring). Admin sends once, everyone knows. (4) Instrument rental billing is missing—MyMusicStaff doesn't track rental inventory or auto-bill monthly. School tracks rentals in spreadsheet (prone to errors, manual invoicing). Custom system: rental pool is live (each instrument has monthly fee, insurance, availability). Parent books rental, agreement is auto-generated + signed digitally, monthly billing is automatic (no manual invoices, no forgotten charges). (5) Lesson progress archival by student is weak—MyMusicStaff stores notes, but exporting a year of lessons (all instruments, all teachers) is manual. Custom system: end-of-year archive is one-click ("Emma's 2026 lesson record: 40 piano lessons, 30 cello lessons, all notes + photos + recordings"). PDF is generated, sent to parent as portfolio (useful when changing schools or teachers). (6) Compliance tracking (WWCC, NDIS) is not built—MyMusicStaff doesn't flag expiring background checks or NDIS reporting deadlines. Custom system: staff member WWCC date is flagged 7 days before expiry (renewal is urgent). NDIS lesson tracking auto-counts sessions (every 3 lessons = 1 report due), admin is auto-reminded (reports are submitted on-time, zero compliance risk). Tutorbird Music ($30-45/teacher/month) is more feature-rich, but: still doesn't separate lesson notes by instrument, still doesn't have AMEB integration, recital scheduling is still manual, rental billing is not supported, NDIS compliance is not automatic. Both platforms are designed for general music education, not Australian exam-heavy, multi-instrument, rental-inclusive schools. Neither is worth the licensing + ongoing gaps.

What Custom Replaces: Six Features Music Schools Need

1. Instrument-Specific Lesson Notes + Parent Progress Portal

Emma is a violin + cello dual student (different teachers, different repertoires). Lesson with violin teacher Sarah (Wed 4pm): Sarah writes notes in Emma's Violin folder: "14 June: bow control improving, Seitz Concerto No. 5 — playing through Mov 1 + 2, intonation sharp on high notes, practice scales 3x/day, listen to Hilary Hahn recording." Notes auto-summarize for parent view: "This week: learned Mov 2, working on bow transitions, focus on high-note intonation. Keep practicing scales! 🎻" (friendly, non-technical parent language). Lesson with cello teacher Michael (Thu 5pm): Michael writes notes in Emma's Cello folder: "14 June: posture has relaxed (good!), Bach Suite 1 Prelude — running through in sections, tone is mellower than last week, homework: full run-through, then slow-practice middle section." Parent sees separate portal update: "This week: working on full Bach Prelude, tone improving. Practice section-by-section, then full run-through. 🎻" Parent views Emma's dashboard: "Piano: idle (no lesson this week). Violin: on-track (Seitz Concerto, scales practice), next lesson Wed. Cello: on-track (Bach Prelude), next lesson Thu." Parent doesn't mix up instruments. Emma knows exactly what to practice for each (separate homework, separate instrument). Sarah doesn't have to write two different updates for one student (one for notes, one for parent summary). System auto-generates parent language from teacher notes. Easy, clear, zero confusion.

2. AMEB Exam-Grade Tracking + Syllabus Auto-Population

School has 12 Grade 3 candidates (piano, violin, cello, flute across 8 students, some students doing 2 instruments). Admin creates "AMEB Exam Cohort: Grade 3, 2026" (click "Grade 3 Piano" + select 5 piano students, "Grade 3 Violin" + select 3 violin students, etc.). System auto-loads syllabus: "Grade 3 Piano: memorize 3 contrasting pieces (Baroque, Classical, Romantic, each 4-8 bars minimum), scales (3 octaves, all major scales), aural (intervals, simple chords, dictation)." Each student gets a progress card: "Emma — Piano Grade 3: Baroque piece (Prelude, 40% learned), Classical piece (Sonatina, 20% learned), Romantic piece (Nocturne, not started), Scales (60% learned), Aural (50% completed)." Teacher updates progress in-app: "Baroque: 40% → 60% (Emma played through successfully this week)." Aural: 50% → 70% (interval recognition improving)." Admin sees cohort progress: "Grade 3 Piano cohort (5 students): 80% on-track (Scales 65%, Pieces 45%, Aural 55%), 20% behind (Emma: behind on Romantic piece, recommend extra lesson)." 12 weeks to exam: admin flags "Sophie's violin is only 40% learned. Recommend 2 lessons/week for next 6 weeks?" Teacher confirms. System auto-adjusts Sophie's timetable (finds second available slot). Sophie gets extra support, passes exam (without system tracking, Sophie would've fallen behind unnoticed). System also tracks: "Exam date: 15 Sep. Days remaining: 84. Days until final exam run-through: 21 (all pieces + scales + aural must be polished). Recommend dress rehearsal in full 2 weeks before exam." Email reminder: "Grade 3 Piano: Exam in 10 weeks. Final pieces must be memorized in 5 weeks (allows 5 weeks for polishing). Current pieces progress: [list]. Adjust lesson frequency? Intensive prep suggested for Sophie." Teachers respond. System generates exam prep timeline automatically (no manual spreadsheet coordination).

3. Recital Scheduling + Automated Parent Coordination

School runs "June Recital 2026" (30 student performances, 4-min each, Sat rehearsal, Sun performance). Admin creates event: "June Recital: Sun 9 June, 2-7pm (25 slots), Sat 1 June 10am-2pm rehearsal (group rotations), Dress rehearsal: Sat 8 June 2-5pm." Teachers self-service ("Claim your students"): Sarah marks "Emma — Piano, 4 min, Prelude 1". Michael marks "Lucas — Violin, 4 min, Concerto". Ukulele group marks "3 students — Ukulele ensemble, 5 min." System auto-builds performance schedule: "Sun 9 June: [2:00-2:04] Emma Piano, [2:05-2:09] Lucas Violin, [2:10-2:15] Ukulele group (3 students), ... [3:56-4:00] Final performer. Transitions: 1 min between soloists, 2 min between groups. Total time: exactly 60 min (on schedule)." Rehearsal schedule: "Sat 1 June: [10:00-10:40] Piano group (4 students, 10 min each), [10:45-11:25] Strings group (violin/cello, 5 students), [11:30am-12:10pm] Winds + ukulele group." Dress rehearsal Saturday: "Sat 8 June: [2:00-2:30] Piano, [2:35-3:05] Strings, [3:10-3:40] Winds, [3:45-4:15] Ukulele, [4:20-5:00] Full dress rehearsal (all performers, practice stage entrance/exit)." Admin sends one email to all parents: "[Emma's parent + Lucas's parent + others] June Recital Info: Your child performs Sun 2pm. Rehearsal: Sat 1 June 10am (Piano group). Dress rehearsal: Sat 8 June 2pm (all performers). What to bring: music (even if memorized, have backup), water, dark outfit (if required by school). Arrive 30 min early. Performance running order: [attached PDF, shows all 30 performers, Emma is slot 1, so arrive by 1:45pm]. Guest pianist: [Name, email for thank-you note]. Any questions? Reply to [admin email]." One email, all info included, parents don't get lost. Emma knows she performs at 2pm (specific time, not guessing). Teachers know dress rehearsal is Sat 8 so they can prepare students. No back-and-forth emails, no missed slots, no chaos. Admin time: 30 min to build schedule + send one email. Manual system: 20+ emails, 3+ hours admin time.

4. Instrument Rental Pool Management + Auto-Billing

School owns 8 rental violins, 4 rental cellos, 2 rental flutes. Setup: admin enters "Violin SN-042: $20/month, insured $500 loss/$100 damage. Cello SN-001: $35/month, insured $1k loss/$150 damage." Inventory is live: "Violin SN-042: available (next 2 weeks free). Violin SN-043: out with Student A (rented til 30 July). Violin SN-044: available." Parent requests: "Emma wants to rent a violin starting next week (Tue 18 June)." System shows: "Available for Tue 18 June: Violin SN-042 (available indefinitely), Violin SN-044 (available until 30 July, then booked)." Parent chooses SN-042. Rental agreement auto-generates: "Violin Rental Agreement: Student Emma. Instrument: Violin SN-042. Monthly fee: $20. Rental period: 3 months (18 June — 18 Sep). Insurance coverage: $500 loss, $100 damage. Monthly billing: auto-charged to parent account. Late fees: $10/week if not returned by end date. Terms: student is responsible for normal wear/tear, but damage from misuse (dropping, water damage, extreme neglect) is charged to parent. Return inspection: staff checks instrument, tuning, bow, case. If damage noted, parent is charged repair cost (capped at insurance limit)." Agreement is signed digitally (e-signature). Monthly billing is automatic ($20 charged to parent account on 18 June, 18 July, 18 Aug — no manual invoicing, no "forgot to charge" errors). 1 month in, Emma drops the case (student's accident). Bow hair is damaged ($40 repair). Parent receives email: "Damage reported to Violin SN-042. Bow repair: $40. Covered by rental insurance? Yes. You are liable for $40 (covered by insurance policy). This charge will be added to your next billing on 18 July." Transparent, parent understands (signed agreement said damages are insured-covered). Repair is made, bow is replaced. End of rental (18 Sep): Emma returns violin. Staff inspects: "Violin SN-042: returned in good condition, tuning peg stiff (minor, normal wear), bridge is properly placed, bow is functional." Return form is checked off. Parent receives email: "Rental returned successfully. Final charge: $20 (Sep month). Total rental cost 2026 (3 months): $60. Invoice attached. Rental agreement closed. Thank you!" End of year admin review: "Violin rentals: 8 violins, avg rental 8 months/yr, $20/month = $12.8k revenue. Damage claims: 4 × avg $50 = $200 (minor). Equipment loss: $0 (all tracked). ROI: $12.6k net. Manual system (spreadsheet): rentals were $8k (some months forgotten), damage claims $1.5k (disputed by parents). Equipment loss: 1 violin unaccounted for = $200 loss. ROI: $6.3k net. Custom system ROI improvement: $6.3k/yr extra (accounting, automation, zero loss).

5. AMEB Exam Compliance Reporting + Teacher Auto-Reminders

State education requirements: AMEB exam candidates must have documented lesson history (schools need proof that student received adequate instruction hours before taking exam). School admin marks: "Emma — Grade 3 Piano, exam 15 Sep 2026, requires 20 hrs minimum instruction by 15 Aug." System auto-tracks: "Emma's Piano lessons: Lesson 1 (6 June, 1hr), Lesson 2 (13 June, 1hr), Lesson 3 (20 June, 1hr), ... Lesson 15 (4 Aug, 1hr). Total: 15/20 hrs completed. Target date to reach 20 hrs: 18 Aug (4 weeks remaining, 1 lesson/week = 4 hrs, need 1 extra lesson to hit 20 hrs)." System recommends: "Emma needs 5 more hrs by 15 Aug. Current schedule: 1 lesson/week = 4 hrs. Add 1 extra lesson in Aug (e.g., second lesson on Thu instead of Wed weekly)?" Admin confirms, second lesson is added. Compliance is tracked automatically (no manual counting, no risk of student being entered into exam unprepared). AMEB report deadline (10 days before exam): "Emma's Grade 3 Piano exam: 15 Sep. Report due: 5 Sep. Teachers: confirm lesson attendance, student readiness, any concerns." Sarah replies: "Emma: attended 16/16 lessons, well-prepared, pieces are polished, scales are strong, aural is ready. Recommend 'Ready to sit exam.'" Report is submitted to AMEB automatically (school provides proof that Emma had adequate instruction). Exam day: Emma sits exam, passes (system helped her get there on-time, with proof of instruction).

6. WWCC Background Check Compliance + NDIS Reporting Automation

Staff member Sarah (piano teacher): WWCC (Working with Children Check) is renewed every 5 years (NSW law). Admin enters: "Sarah, WWCC expiry: 12 July 2026." System flags: "Sarah's WWCC expires in 30 days (12 July 2026)." Reminder email: "Sarah, renew WWCC by 12 July to avoid suspension. Renewal info: [link to NSW WWCC portal]. Once renewed, upload certificate here [link]." Sarah renews, uploads certificate. System updates: "Sarah, WWCC: valid 12 July 2023 — 12 July 2029 (renewed 10 July 2026). Cleared." Audit trail: "WWCC history: Valid 2018-2023 ✓, Valid 2023-2029 ✓. No gaps." Compliance is solid (no accidental expired checks, no liability risk). NDIS lesson tracking: student Lucas receives 2 NDIS-funded cello lessons/week (NDIS agreement requires progress report every 10 lessons paid). Admin marks: "Lucas, Cello lessons: 2/week, NDIS-funded, reporting required every 10 lessons." System counts: "Lessons 1-10: submitted report 15 June ✓. Lessons 11-20: report due 30 June (5 days remaining). Teacher: prepare progress report." Teacher receives reminder: "Lucas NDIS report due in 5 days. Complete form: [link]. Include: skills learned, goals achieved, practice at home, progress toward diploma, any concerns." Teacher fills form: "Lucas: improved bow control significantly, learned 4 new pieces, practicing at home 30 min/day, is on-track for Grade 2 by year-end, no concerns." Report is submitted, auto-archived. NDIS agreement is satisfied (no missed deadlines, compliance record is perfect). At year-end, audit trail shows: "Lucas, NDIS lessons 2026: 104 lessons delivered, 10 progress reports submitted on-time, 100% compliance." School can prove to NDIS (and regulators) that services were delivered and reported correctly. Manual system (spreadsheet): 1 report missed (teacher forgot deadline), NDIS queries school, admin scrambles to backdate report (looks bad, compliance risk). Custom system: zero missed deadlines, zero regulator queries.

Australian Music School Context & Growth Model

Australian music education market: ~8,000 independent music schools + conservatoriums, 40,000+ working music teachers, $800M+ annual market. School models: private tutor owner-operator ($40-80k/yr profit), 3-8 teacher cooperative studio ($150-300k/yr revenue, 50% profit margin), 15+ teacher academy (higher rent, more class offerings, community reputation). Revenue mix: 65-70% private lesson fees (one-to-one tuition, $25-60/hr), 20-25% ensemble/group classes ($15-30/student/week), 5-10% rental income (instruments, practice rooms). Student mix: 40% hobby students (once/week, low exam interest), 30% Grade-track candidates (aiming for AMEB Grade 1-8, 2-3 lessons/week), 20% pre-diploma students (Grade 8+, serious players, 2-3 lessons/week), 10% NDIS-funded (disability support, funded lessons). Exam season is critical (Aug-Nov is peak exam time, school must track 20+ candidates simultaneously). Recitals are major revenue drivers (parent attendance, guest musicians, program sales, teacher performance opportunities). Instrument rentals are high-margin (20-30% margin on monthly fees, zero inventory loss risk if tracked properly). Teacher retention is high (unlike tattoo artists, music teachers often stay 3-5 years+), but documentation burden is increasing (AMEB requires proof, NDIS requires reporting, WWCC is mandatory). Opportunity: Australian music schools are severely underserved by booking software. MyMusicStaff is generic (no exam tracking, no instrument-specific notes). Tutorbird Music is better but still doesn't have AMEB, NDIS, recital automation. No platform offers rental billing. Schools are using spreadsheets + email (chaos, missed compliance deadlines). Custom platform would immediately: (1) centralize AMEB exam tracking (no spreadsheets), (2) automate parent progress communication (separates instruments, reduces email), (3) handle recital coordination (30+ students, no manual email chains), (4) manage rental income (zero lost fees, zero lost inventory), (5) flag compliance deadlines (WWCC, NDIS reporting), (6) archive lesson records (useful for student portfolios, school audit trails).

Six FAQs

Can we integrate with AMEB's system instead of building custom?

AMEB doesn't offer school management software (they run the exam system, not lesson tracking). Schools manually keep exam prep records (spreadsheets, email). MyMusicStaff / Tutorbird Music don't integrate with AMEB (you'd have to track AMEB prep separately). Custom system: AMEB syllabus is built-in (system auto-loads "Grade 3 Piano requirements: 3 pieces, scales, aural"). Exam-prep tracking is native (no integration headache, no third-party API dependency). You own the data (portable, can export if needed).

What if a student changes instruments mid-year?

Emma was piano-only (12 lessons in). Now she wants to add cello (starting lesson 13). System splits her record: "Piano (12 lessons completed, no exam planned), Cello (new, starting lesson 1, no exam planned)." Each instrument has separate notes, separate teacher assignment, separate progress. If Emma later drops cello (lesson 8 of cello), her piano record stays intact (cello just archives to "inactive"). Clean separation, no data loss or confusion.

How do we handle makeup lessons?

Emma is sick Wed 18 June (missed piano lesson). She makes it up Fri 20 June (different time slot). Teacher books makeup lesson: "Emma, Makeup for 18 June lesson. 1 hour, Fri 20 June 4pm. Note: makeup for missed lesson (sickness)." System tracks: "Emma's Piano: [18 June lesson MISSED—makeup scheduled], [20 June lesson: makeup, same hour]." When billing, parent is not charged twice (one missed lesson, one makeup = one payment). If makeup is taken, the original missed lesson is marked [MADE UP]. If makeup is not taken, missed lesson is marked [FORFEITED] (parent is charged, student lost the slot).

What about ensemble lessons (group classes)?

School runs "Beginner Strings Ensemble: Wed 5pm, 4 students (violin, cello, viola). Intermediate Piano Group: Sat 10am, 6 students." Ensemble lessons are booked differently: admin creates "Strings Ensemble group, 4 students, Wed 5pm weekly." Attendance is tracked per student (Emma attended week 1, 2, absent week 3, attended week 4). Notes are group-focused ("Reviewed bow transitions, practiced Canon in D, strong ensemble cohesion this week") but students can have individual notes too ("Emma: intonation sharp, work on E string"). Billing is per-student per-week ($15 per student, if attended). If Emma skipped week 3, she's not charged that week (but she forfeited the learning opportunity).

How do parents see their student's progress without logging in?

Every lesson, teacher writes notes. Parent-facing summary is auto-generated: "This week: Emma worked on scales and Prelude 1. Scales are solid, Prelude needs more practice on the second section. Keep practicing 20 min/day! 🎵" Summary is emailed to parent after each lesson (no parent login needed, gets email notification). Parent can reply ("Any tips for practicing at home?"), which goes to teacher. Full lesson history is available in parent portal if they log in (but email is the main channel). Parent portal is optional (nice-to-have for annual progress archive, not required for day-to-day communication).

What if an exam candidate doesn't pass the AMEB exam?

Emma sits Grade 3 Piano exam, result is "Unsuccessful." AMEB publishes result (she can re-sit in the next exam session, typically 3-6 months later). Admin marks Emma's exam record: "Grade 3 Piano: Exam date 15 Sep 2026, Result: [Unsuccessful]. Re-examination scheduled: [leave blank if student decides not to retry, or mark 15 Dec 2026 if retrying]." If Emma retries, system auto-creates a new exam cohort ("Emma — Grade 3 Piano, Re-sit 15 Dec 2026"). Progress tracking starts fresh for the retry (exam prep is redone). If Emma doesn't retry, the exam record stays archived ("Grade 3 Piano: Unsuccessful, not retaken"). System is flexible—supports both outcomes without penalty.

The Bottom Line

MyMusicStaff or Tutorbird Music: $19-45/teacher/month × 12 teachers = $2.7-6.5k/yr licensing. Plus exam-prep overhead (spreadsheet tracking, manual reminders, missed deadlines: 5 hrs/month × $50/hr = $3k/yr labor). Plus recital coordination chaos (20+ emails, 8 hrs/year = $400/yr). Plus rental billing errors ($500-1k/yr leaked revenue from forgotten charges). Plus WWCC/NDIS compliance risk (1 missed deadline = potential fines $1-5k, reputation damage). Plus parent communication overhead (teacher writes custom emails every lesson, 5 min × 500 lessons/yr = 42 hrs/yr = $2k labor). Total annual cost: $6.5k licensing + $3k exam labor + $400 recital labor + $0.75k rental loss + $2k parent communication = $12.75k/yr in friction. Custom platform: $60-100k upfront, $2.5k/yr hosting. Year 1: $60-100k. Year 2: $2.5k + labor reclaimed. Break-even month 18-24, then pure savings ($6.5k licensing + $3k exam labor + $0.4k recital labor + $0.75k rental improvement + $2k parent communication + $1k NDIS compliance savings) = $13.65k/yr net positive. By year 3, cumulative savings: –$80k (build) + $0 (year 1) + $13.65k (year 2) + $13.65k (year 3) = –$52.7k (breakeven year 4). Year 5+: $13.65k/yr pure profit. 12 teachers, 500 lessons/month, 30% exam candidates, 10% NDIS-funded = $150-200k/yr revenue. 5% efficiency gain from custom platform (fewer no-shows, better scheduling, zero compliance risk) = $7.5-10k/yr extra profit. Build custom. Own your exam tracking (every candidate on-time, zero spreadsheet errors). Own your parent communication (auto-generated summaries, reduced parent email burden). Own your recital coordination (30+ students scheduled automatically, zero chaos). Own your rental billing (zero lost revenue, automated monthly charges). Own your compliance (WWCC flagged before expiry, NDIS reports submitted automatically). Own your student archives (years of lesson history, portable for parent records or school transfer).

Ready to build a custom music school platform? Check Aidxn's custom software packages, or book a call to discuss your school (how many teachers?, how many students?, how many AMEB candidates/year?, NDIS-funded lessons?, how many recitals/year?, current booking system?, exam-prep tracking method?, parent communication frequency?, rental program scope?, compliance gaps?), licensing costs, and growth targets (expand to second location?, add online theory classes?, add digital practice-session recording?, build teacher performance profiles for marketing?).