How Pirouette came about
It started in a real studio — on software that fought the people running it.
Pirouette wasn't dreamed up in a strategy deck. It started with one independent dance studio stuck on Dance Studio Pro — paying many times the headline price for a portal parents avoided and billing that read backwards — and a simple refusal to accept that the software a studio runs on should make the work harder.
The software a studio runs on shouldn't fight the studio.
For over a decade the dance-studio category has been served by a handful of platforms built before anyone took the front desk seriously. They show your balance as a negative number. They hide the work behind opaque mega-menus. They take a percent of every tuition payment, add a line item for texts, and charge again for a branded app. The teaching is great — the experience around it is where studios quietly lose families, and money.
Switching usually means trading one set of those problems for another. So instead of shopping for software, this studio did something different: it wrote down exactly how it works.
How it was built
Domain truth first. Then the build.
Not a feature wishlist — a real specification. The four people who touch the studio every week (the front desk, the owner, the parent, the teacher), the everyday flows, and the billing math nobody else gets right: tuition spread as 34 classes across a 10-month year, sibling discounts, comp-fee escrow that has to stay separate, and the edge cases of custody and mid-year transfers. Written from the studio's real operations — not copied from the old software's screens.
That spec went to a software developer who builds multi-tenant software for people who run real operations — the kind where one wrong assumption in the data model costs a studio a season. The rule for the project was simple: the studio's domain truths stay exactly as described; the architecture decides everything else. Where the spec asked a question, he answered it. Where it leaned on the old software, he replaced it — and said why.
That's the whole of it. Pirouette is built by a studio owner and a software developer. One lives these problems every day; one sweats every login, every payment, and every line of code. There's no third party between you and the people who made the thing.
Built around the person with her hand on the studio.
The most-designed surface in the whole product is the front desk's home screen — because the front desk is doing the actual work: the rush-hour check-ins, the payment that has to clear before the next family walks in, the parent question that should have been self-serve in the portal.
The owner dashboard puts past-due 30 / 60 / 90 at the top of the phone. The parent portal is built mom-first, with the balance right where she looks. The teacher's app is built for the studio floor, not a desk after hours. Same studio, four people, one platform that respects how each of them actually works.
Why "Pirouette."
The word does the work on its own — implied motion, the spotting eye a dancer fixes on through the turn, the apex held for a beat. No ballet shoes, no dancer silhouettes, no purple gradients. Warm, editorial, grounded — on purpose. The studio aesthetic, not a SaaS dashboard.
How we talk about it
We talk about the workflow. Past-due 30 / 60 / 90. End-of-day cash-out in one tap. Sub coverage that doesn't make the front desk chase three people. We don't say streamline, empower, transform, or unlock. Every other platform talks like that. We don't need to.
We're bringing studios on now.
The first studio is going live on Pirouette. Join the waitlist and we'll bring yours on with guided onboarding.