Music School Software: Custom Build or Buy My Music Staff and Opus1

What the off the shelf products actually do well

Nobody starts a music school wanting to think about software, and the good news is that under a certain size you do not have to. A one location school with 200 students, a policy that fits on a page and no group programme is well served by what already exists, and building would be a vanity project you would regret by the second term.

My Music Staff handles lesson calendars, attendance, invoicing and parent communication for independent teachers and small schools. Opus1 is stronger on multi teacher operations and enrolment. Teachworks is flexible around lesson types and billing. Jackrabbit Class comes from the dance and gymnastics world and handles term based enrolment and family accounts properly. All four bill, all four track attendance, all four have parent portals, and all four cost less per month than an hour of your director's time.

Around them, the rest of the stack is mature too. Stripe or Adyen for card on file with proration and dunning, a tokenising gateway so card data never touches your database, QuickBooks Online for the books, Gusto for W2 payroll, Twilio for the messages that drive makeup fill rates.

Buy, and do not call us, if this is you:

• One location, under roughly 250 active students.
• A makeup policy with no exceptions your front desk has to argue about.
• Private lessons only, no term based group cohorts running alongside them.
• Rooms that are genuinely interchangeable.
• One compensation model, or two, rather than five.

Where they stop: the makeup credit ledger and typed rooms

Here is the workflow every product in this category models badly, and it is the same one at every school past 400 students.

A family bills a flat monthly tuition. In March a teacher cancels once, the student is sick once with 26 hours notice, and there is one no show. Under your policy the teacher cancellation is a guaranteed makeup, the 26 hours earns a credit that expires in June, and the no show forfeits. Tuition still bills in full. Somebody has to hold all of that, and none of these products does, because billing runs on a schedule and attendance sits in a log while the rule connecting them lives in your staff handbook. The human becomes the integration layer. When a parent writes to say she is fairly sure two makeups are left, someone counts, argues, and usually grants the credit to end the conversation. In reconciliations we have run, 6 to 9 percent of billed lessons were being given away as unbudgeted goodwill because nobody could prove the ledger.

The fix is structural rather than a feature. Every lesson runs a state machine: scheduled, delivered, cancelled by teacher, cancelled inside notice, cancelled outside notice, no show, made up. Each transition writes a credit row with an issue date, an expiry, a source lesson and a redeeming lesson. Tuition is then computed from the ledger, so proration, mid term instrument changes, sibling discounts and withdrawal notice all fall out of one calculation instead of four spreadsheets. Self serve makeup booking only offers slots that are legal: right instrument, right teacher tier, credit unexpired, room free.

Rooms are the second gap. Room 4 holds the grand piano and cannot take the drum student. Room 7 is the only isolated room. Room 2 shares a wall with the front desk. Room 9 has the digital piano the theory class needs on Tuesdays. None of that fits in a text field labelled resource, so rooms get scheduled on a paper grid and double bookings get discovered by a teacher standing in a doorway at 4:31pm. Worse, you cannot answer the question that decides growth: between 4:30 and 7:30 on Tuesday, how much capacity is left, and for which instrument.

Teacher pay is the third. Fourteen W2 hourly, twenty on 1099, a 60/40 split for the piano lead, per lesson rates that step up after 100 lessons, flat section rates for group instructors, half pay on a student no show, full pay on a delivered makeup without double paying the original. No tool in the stack owns that, so payroll becomes a reconstruction twice a month.

The arithmetic: cost per student versus cost to build

Run this on your own roster before anyone quotes you.

Take your platform's per active student monthly rate. At roughly $2 a student and 900 active students that is about $21,600 a year, and it grows with exactly the number you are trying to grow. Add the payment processing you would pay anyway, then add the things the subscription created rather than removed.

Count the labour honestly. A teacher out sick for a week with 26 students triggers roughly four hours of a $27 an hour manager plus 40 minutes of the director's evening, six or seven times a term, per location. Payroll reconstruction runs 10 to 14 hours a pay period. Room grid maintenance is a Sunday afternoon. Across three locations that pattern costs $30,000 to $60,000 a year in front desk labour before you count the families who quietly leave because a third makeup never got scheduled.

The crossover sits near 500 active students, or the moment you open a second location that shares a teacher with the first, whichever comes sooner. Below it the subscription is a rounding error and the overhead is one person's afternoon. Above it you are paying a per student fee and a full time salary to operate the gap, and only one of those two lines appears in a budget.

What a custom build actually costs

A focused first release runs $60,000 to $130,000 and ships in 12 to 16 weeks. For a school that scope is almost always the same three things plus two apps: the lesson state machine with the makeup credit ledger, tuition billing sitting on top of it, teacher pay calculation, a parent portal and a teacher app. Typed rooms belong in release one as well, because retrofitting the room model later means rewriting the scheduler.

A full platform adding intake automation, retention scoring, group classes and ensembles, recital management, instrument rental inventory, multi location reporting and accounting plus payroll integration runs $150,000 to $400,000 phased across 6 to 12 months.

• Data migration. Budget 10 to 25 percent of build cost. The contact list is trivial. Three years of lesson history and open credit balances maintained by hand are not, because somebody makes a judgement on every ambiguous balance. Plan three to six weeks and a reconciliation session with your front desk lead.
• Year two onward. Budget 15 to 20 percent of build cost annually for support, gateway changes, tax table updates through your payroll provider and the enhancements that arrive once teachers start using the app daily.

The four situations where building wins

Two of these should be true before you commission anything.

• Regulatory fit. You handle minors every day. Student accounts under 13 pull the Children's Online Privacy Protection Act into scope. Recorded practice submissions and recital video bring parental consent, retention limits and media releases. Teacher to student messaging needs parent chaperoned threads by default, and background check records need expiry tracking. Card on file across three payment paths puts you inside PCI DSS scope unless a tokenising gateway keeps card data out entirely. Products treat these as settings. At three locations they are a design.
• Scale economics. Past roughly 500 students the per student fee and the reconciliation salary rise together.
• A workflow that is your competitive advantage. A makeup swap marketplace between families, or a guaranteed slot promise, is your product and cannot be rented. If you intend to franchise your operating model to other schools, you are a software company already and this platform is the thing you will sell.
• Integration sprawl. Count them: the lesson calendar, the card gateway, the clock in tool, payroll, accounting and the messaging platform is six. Once three or more must agree about one lesson that was cancelled inside notice, the reconciliation is the job.

How to decide in a week

Do this instead of watching another demonstration.

• Monday. Pick thirty families and audit their makeup credit balance against the attendance log. Count how many you can prove. The share you cannot prove, multiplied by your average lesson price, is your annual goodwill leak.
• Tuesday. Ask your front desk lead to answer, without counting by hand, how much prime time capacity remains at your busiest location on Tuesday between 4:30 and 7:30, by instrument. Time how long it takes.
• Wednesday. Reconstruct one teacher's last pay period from scratch and compare it against what you paid. Any variance is your error rate.
• Thursday. Get your platform renewal quoted in writing at next year's projected student count, and ask what a full export of lesson history and open credit balances contains.
• Friday. Decide. Two of the four conditions plus a failed Monday or Wednesday means build. Otherwise stay, tighten the policy and spend the money on a second cello teacher.

Then buy discovery before code. A paid discovery phase ends with a signed product requirements document covering the lesson lifecycle, the credit rules, the room model, the compensation rules and the acceptance criteria. You own it and can take it to any firm, which is what makes competing quotes comparable rather than three different guesses.

Digital Heroes writes that specification before writing code, and the client owns the repository, cloud accounts and gateway keys from the first commit. We hold India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law rather than ours. More than fifty specialists, over 2,000 projects, and a named team you meet before signing, verifiable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S. We run our own products, ShopScore, HeroCheckout and Section Vault. We are the wrong firm for a single studio that should be on My Music Staff, and wrong for a director who wants a demonstration next week rather than a written policy first.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.