At a glance
Osaka Ballet is a tenant on Pepperoni Booking. The studio is operated independently of the platform — different owner, different operations — but came onto Pepperoni through the founder's network. We disclose this because the connection is real, even if the operating relationship is not.
First — full disclosure
Osaka Ballet is operated independently of Pepperoni Booking. The studio's founder is not the platform's founder. They chose Pepperoni because of the founder's relationship with the studio — a referral, not a cold competitive evaluation.
We publish this case study because Osaka Ballet is the platform's first non-founder-operated tenant. That's a meaningful milestone, but it's not the same as a studio choosing Pepperoni from a list of alternatives. The honest framing is: friendly third-party tenant.
What you can take from this: a studio operated by someone other than the platform's founder uses Pepperoni daily and finds it sufficient for their operations. What you cannot take from this: that they shopped competitors and picked us. We don't have that case study yet — and we say so on Larry's case study too. The founding cohort program is how we get there.
Read Larry's case study →
The studio
- Name
- Osaka Ballet
- Location
- Osaka, Japan
- Locations
- TBD — founder to confirm
- Studio owner
- TBD — founder to confirm (operator is not Daishin Murooka)
- Specialties
- Ballet
- Active clients
- TBD — founder to confirm
- Time on platform
- TBD — founder to confirm
- Plan tier
- Booking
“A quote from the studio owner is being collected. The case study is published in this interim form because the friendly-tenant disclosure is the load-bearing trust signal, not the polish — same posture as the founder's own case study.”
How Osaka Ballet came to Pepperoni
TBD — founder to confirm. The honest version: a referral through the founder's network, not a cold sales process or competitive evaluation. The studio evaluated the platform, decided it covered their core operations, and migrated. What they used before Pepperoni and what specifically prompted the switch is the narrative we want to fill in here.
Specific tools they used before, the operational changes that mattered most, and the exact go-live timeline are pending founder-of-studio confirmation.
What changed at Osaka Ballet
Same operational pains, observed from a different studio. TBD — founder of Osaka Ballet to confirm whether these specific scenarios match their experience.
Before Pepperoni
Phone Rings Mid-Class
A prospective student wants to book. Miss the call mid-teaching, lose the booking.
After Pepperoni
Bookings Come Through The Platform
Class is taught uninterrupted. Confirmation goes out automatically — the studio never sees it happen.
Before Pepperoni
Capacity Mismatch
What the schedule said and what the room could hold weren't always the same number. Students arrived to a full studio.
After Pepperoni
Capacity Is Enforced
Limits are honored. Waitlist activates automatically. Overbooking becomes impossible.
What features Osaka Ballet uses
These are features available to every Booking-tier customer — same set Larry's uses.
- Bookings — student-facing booking flow, capacity rules, no-show tracking
- Classes — recurring schedule, weekly enrollment, per-session notes
- Teachers — instructor profiles, per-instructor scheduling
- Students — client database, trial → member conversion
- Notifications — booking confirmations, reminders, cancellation flows
- Calendar feeds — personal iCal feed for the studio owner
- Support chat — direct line to platform support
What this case study cannot tell you
Direct, honest list:
- Whether Osaka Ballet would have chosen Pepperoni from a list of competitors. They came through a referral, not a sales cycle. The relationship influenced the decision.
- Whether the platform is what an unrelated studio would want it to be. Osaka Ballet trusted the platform partly because of a relationship; a cold prospect would have to trust it on its own merits.
- Whether the metrics will generalize. Osaka Ballet is one studio in one city with one specialty. A different studio in a different market with different demand patterns may need things this case study doesn't surface.
What this case study can tell you
- A studio operated by someone other than the platform's founder has used Pepperoni in production daily for long enough to develop a real opinion.
- The platform's Booking-tier features cover an external studio's core operations without bespoke modification.
- When the founder's own studio (Larry's) is removed from the population, there is still a non-empty set of tenants on the platform.
Why this case study is short for now
The deeper story — exact pre-Pepperoni operating state, the operational changes that mattered most, the founder-of-studio's perspective in their own voice — is being collected. The case study is published in this honest interim form because the friendly-tenant disclosure is the trust signal, not the polish. When the studio-owner narrative is added, this section is replaced.
This case study, like Larry's, is published to set the standard for what honest tenant case studies look like at Pepperoni Booking. The next one we want to write — and recruit for — is about a studio that chose us cold.
Explore further