I built a studio platform for one studio. Here's what happened.
I have a friend who runs a small dance studio. About two years ago she texted me. A regular client had paid for a class pack months earlier, the credits weren't showing up in her booking system, and she'd been on hold with the vendor for forty minutes trying to get a fix. Class started in ten. She comped the spot and ate the cost.
That wasn't the day I started building. It was the day I started counting how often that happened.
What she was paying for#
Her stack at the time:
- Mindbody Core: $129/month
- A separate email tool for class announcements: roughly $30/month
- A spreadsheet that tracked who got comped, who needed refunds, and who owed what to instructors
- An end-of-quarter ritual where she reconciled all three so she could pay her teachers
About $1,900 a year in software, plus the hours.
The software wasn't the expensive part. The hours were. Five to eight a week, depending on the season, copying things between systems, re-sending schedule changes by hand, hunting for the comp she'd issued last Tuesday because someone's card got declined.
This isn't a story about Mindbody being bad. Mindbody works for studios with an office manager and the headcount to absorb that kind of friction. She's one person.
Why she switched#
Not because she did a vendor evaluation. Not because she compared feature matrices. She switched because the person who builds the software has her phone number.
That sounds like a joke. It isn't.
The actual mechanism: when a class-change email goes out wrong, she texts me. The fix lands the same day. When she wanted guest checkout because her Sunday class kept turning away walk-ins who didn't want to make an account, that shipped in a week. When the refund flow lost a charge in a race condition, I fixed it that night.
Mindbody can't offer this. It's not a price problem or a feature problem. It's that I built the product next to one studio owner. The product knows what she does because I watched her do it.
What changed#
Workflows that used to exist and don't anymore:
- Re-entering walk-in registrations from a paper sign-in sheet
- Mailchimp blasts every time the schedule shifted
- A separate spreadsheet for tracking comps
- A quarterly reconciliation to pay instructors
- Hunting for refunds across Stripe, the old booking system, and her notes
Time back: she estimates five to eight hours a week. I think it's more, but she's conservative about claims like that, and so am I.
Software cost: about $1,900 a year down to the platform processing fee on bookings. Some months she pays less than she used to spend on email alone.
The dollar number isn't the headline. The headline is that she stopped being the person who keeps the system running.
What we still don't do#
Mindbody integrates with ClassPass. We don't, and we don't plan to. Studios that depend on ClassPass for fill rate won't be happy with us. The premise of the platform is that the studio owns the client relationship. ClassPass is the opposite of that. If your business runs on ClassPass, this isn't the product.
Mindbody has brand recognition. A new client searching "yoga near me" finds Mindbody studios first. We don't have that. Studios that lean on Mindbody's discovery surface should know what they'd be giving up.
What's next#
She's one studio. The platform now runs more, but the design language is hers. Other studio owners pick it up faster than I expected. It turns out the workflows that fit one specific dance studio fit a lot of dance studios.
I'm skeptical of case studies that don't name a tradeoff. This one names a few. If you run a small studio and you don't have an office manager to absorb the friction your software creates, you can reach me at bryan@studiobase.org.
— Bryan, founder