When Studio plan beats Pay-as-you-earn — the break-even math on a 17-student studio

I get a version of this email about once a week from teachers on the Segnoly waitlist:

"I'm at 14 students, growing toward 20 by September. At what point should I switch from Pay-as-you-earn to Studio?"

The honest answer almost never matches the answer the teacher is hoping for, which is a single sentence with a number in it. The reason is not that the math is hard. The math is the easiest part. The reason is that the break-even point most teachers focus on — the dollar volume where 2% on payments equals $79 a month — is roughly the least interesting variable in the decision.

I want to walk through this with a worked example. Not a generic chart, not a pricing table with a "best for growing studios" sticker on the middle column. One studio, real numbers, the actual decision.

The example studio

Call it the example studio. Seventeen active students. Four 45-minute weekly lessons each per month, billed at $55 a lesson. About 80% of families pay by card; the other 20% pay by Zelle or check, which Segnoly tracks but doesn't take a fee on.

That gives you the monthly numbers I'll use throughout this piece:

• Gross monthly tuition: 17 students × 4 lessons × $55 = $3,740
• Card-paid portion: 80% of $3,740 = $2,992
• Manual-paid portion (Zelle/check): $748

These aren't unusual numbers. They are roughly the median I see described in the public reviews of every billing tool aimed at independent music teachers — somewhere between 12 and 20 students, somewhere between $45 and $65 a lesson, somewhere between two thirds and four fifths of payments running through a card processor. The example studio is sitting right in the middle of that distribution.

The math everyone fixates on

Segnoly's PAYG plan charges a 2% platform fee on card payments — on top of Stripe's own 2.9% + 30¢. Studio is a $79 flat monthly fee with 0% platform fee on top of Stripe's cut. (See lib/entitlements.ts:applicationFeeBps() — the function returns configuredBps for PAYG and 0 for Studio and Academy, no other branches.)

For the example studio at $2,992 in card volume:

• PAYG platform fee: $2,992 × 2% = $59.84/mo
• Studio platform fee: $0/mo
• Studio subscription: $79/mo (or $65.83/mo if paid annually at $790)

So at $2,992/mo of card volume, the example studio is actually a hair short of the strict break-even point. PAYG costs $59.84/mo in platform fees; Studio costs $79/mo flat — a $19.16/mo gap in PAYG's favor on the dollar math alone. The annual plan narrows the gap to roughly $6/mo.

Generalised: the break-even point on monthly billing is $79 ÷ 2% = $3,950 in card volume per month. On the annual plan it drops to $3,292. Below those numbers, PAYG is cheaper on pure platform-fee math. Above them, Studio is cheaper.

So why don't I just tell the teacher in my inbox to switch when they cross $3,950?

Because that's not actually how the decision works in practice, and the teachers who optimise for it tend to make the wrong call by about six months.

What the math leaves out

Here is the counter-default insight. Most independent music teachers stay on a low-monthly-fee plan too long, not because the dollar math says they should, but because they over-weight the visible $79 line item and under-weight the invisible time cost of running a sub-25-student studio without auto-monthly invoices, parent portal, and SMS.

The clearest evidence I have of this is a testimonial on Music Teacher's Helper from a piano teacher named Melody Siemens, in La Crête, Alberta:

"I used to write out all my bills by hand every month, and with 25-30 students this was a huge hassle and would often not get done on time!"

— Melody Siemens, Music Teacher's Helper testimonials page

I want to sit with that line for a second. "a huge hassle and would often not get done on time." That's a teacher describing the actual operational state of a studio at the size where the example studio is sitting today. Not a hypothetical. A teacher who, before software, spent some non-trivial portion of every month hand-writing bills, getting them out late, and absorbing the downstream consequences of late bills (later payments, more reminder emails, harder month-end reconciliation).

I've seen the same pattern phrased differently across most teacher-facing software vendor sites — vendors quote real users to the effect that automation "saves hours every week," that auto-pay is "the biggest time saver," that the invoicing automation lets a teacher manage 40+ students "as an individual teacher." None of those quotes give a hard number that I'd trust to one decimal place. But the directional consensus is consistent: hand-managed billing at a 15-30-student studio takes hours per month, and most of those hours land on the last weekend of the month and the first week of the next one.

The time-saved math, soberly

I'll be conservative. Suppose hand-managed billing at the example studio takes 3 hours a month end-to-end: drafting invoices, sending them, logging payments as they come in, chasing the late ones, reconciling at month end. That's not a heroic estimate. The Music Teacher's Helper testimonial corpus suggests it's an undercount for a 17-student studio that's still doing some part of this manually.

What's an hour of the example studio's time worth? At $55 per 45-minute lesson, the teaching rate is roughly $73 an hour. So 3 hours of hand-managed billing per month is $220 of foregone teaching capacity per month, before you've added a single dollar of platform fee.

Auto-monthly invoices on the Studio plan don't take billing to zero. There's still a few minutes a month spent reviewing the auto-generated invoices, handling exceptions (a missed lesson, a credit, a sibling discount), and confirming the parent portal looks right. But it's the difference between "3 hours" and "30 minutes" — call it 2.5 hours saved per month, or $183 of foregone teaching capacity recovered.

That number is roughly nine times the platform-fee delta between PAYG and Studio for the example studio. It's about 2.3 times the Studio subscription itself. It's the dominant variable in the decision.

The corollary is that the break-even point isn't $3,950 in card volume. It's roughly the moment when the teacher is doing enough monthly billing volume that the time cost of doing it by hand exceeds the price of automating it. For a part-time teacher with a steady 8-student studio, that's never. For a teacher growing through 12, 14, 17 students, it's already happened — usually a few months ago, but they haven't noticed because the $79 line item is more visible than the missing $183 of teaching time.

The features the dollar-math chart doesn't price

Studio plan unlocks four things that PAYG doesn't, and the dollar value of each varies by studio. The list, with the rough mental model I'd use:

• Auto-monthly invoices. This is the time-saved lever I just walked through. For a studio with stable lesson schedules, it's worth somewhere between 1 and 3 hours a month. At $73/hr, that's $73–$220/mo of recovered teaching capacity. (Code path: lib/auto-invoices.ts runs once a month and creates invoices from the student's billing rate × actual scheduled lessons.)
• Parent portal. Parents can see their balance, download past invoices, pay online. The dollar value isn't the parent's convenience — it's the elimination of "I think I paid that already, can you check?" emails, which on most teachers' calendars cost more than the few dollars a month they think they cost. Worth maybe $20–$50/mo on most studios in foregone email time.
• Included SMS, ~200 a month. Reminders, late notices, schedule changes. The intuition most teachers have is that email is enough, but the Capterra testimonial corpus and the forum archives I read while designing Segnoly's reminder cadence are unanimous: a text message at the right moment moves money in a way an email at the same moment doesn't. (PAYG doesn't allow SMS at all — lib/entitlements.ts:smsAllowed() returns false for PAYG.)
• 0% platform fee. Already covered above. At $2,992/mo of card volume, this is worth $59.84/mo. The absolute number scales linearly with card volume; for a studio doing $5,000/mo on cards, it's $100/mo, which on its own more than justifies the Studio subscription.

The naive break-even chart treats only the last bullet as math and the first three as marketing copy. The actual decision flips that ratio.

What changes mid-year

The most common version of the question I get is "I'm at 14 students now, will be at 20 by September, when should I switch?" The honest answer is: probably now, but the cleanest moment is whenever your trial happens to start.

The 30-day trial doesn't require a card and previews the full Academy feature set — the top tier above Studio. (See lib/entitlements.ts:resolvePlan() — if trialEndsAt > now and the stored plan is still the default, the studio gets the Academy feature view regardless of subscriptionStatus. When the trial ends without a real subscription, it falls back to PAYG cleanly; no lockout, the studio just loses the Studio- and Academy-only features.) For most teachers in the email I described, the right play is: start the trial in the last week of a month, run a single full billing cycle with auto-monthly invoices and the parent portal turned on, and then make the call when you have a real comparison instead of a projected one.

The thing I want teachers to track during that trial isn't the $79. It's the question: how many hours did I not spend on billing this month? Multiply by the teaching rate, and the middle column on the pricing page gets a lot more honest.

A note on Academy

If the studio in your inbox isn't a solo operation — if it's 3+ teachers under one brand, or you're hiring your first assistant teacher this fall — none of the math above applies. That's an Academy decision ($149/mo, 5 teacher seats included, $19/seat/mo beyond that, plus a public booking page on your own domain), not a Studio decision. The break-even story for Academy is a different post — the dominant variable there is the per-seat overhead you'd otherwise pay on MyMusicStaff Pro or Duet's per-instructor pricing, not the platform-fee delta. If that's you, skip Studio entirely.

The thing I'm trying not to do

I built Segnoly's PAYG plan because I genuinely believe a small studio shouldn't pay a monthly subscription for software it isn't yet using to its capacity. The 25-active-student cap on PAYG is real — lib/entitlements.ts:canAddStudent() returns a hard refusal at 25 — and it's there because below a certain volume the PAYG math is, for most studios, the right call.

But I don't want to write a pricing page that pushes a teacher to stay on PAYG until the cap forces them off. That's the failure mode of every billing-tool pricing page I've audited: a "starter" plan that's optimised to maximise the moment of forced upgrade, and a "growth" plan that's priced to look bad in a side-by-side dollar comparison until you read the fine print and realise the real value is in the features the dollar comparison doesn't price.

The honest version of this conversation, for the example studio, is: at $2,992/mo of card volume and 17 students, you're a hair short of the dollar break-even, you're already paying a hidden $183/mo in foregone teaching time on hand-managed billing, and the only thing keeping you on PAYG is the visible $79 you've decided is "too much for software." The trial is free for 30 days. Run a real billing cycle. Then look at the middle column.

If the math still says PAYG, stay on PAYG. The plan exists because it's the right answer for some studios. But run the cycle.

---

Building Segnoly — billing and automation for independent music teachers. The example studio in this post is hypothetical, the math is what lib/entitlements.ts actually computes, and the waitlist is open for the first cohort.