Studio software that doesn't lose track of the money.

Why we started

Studios don't leave their software because they love it. They stay because the data move looks terrifying, getting every card back on file sounds like a month of phone calls, and nobody wants to be the person who broke tuition in September.

So the first thing we built properly wasn't a prettier calendar. It was the ledger: append-only by database rule, integer cents throughout, with lines written in plain English and discounts posted as their own visible credits. If you can read a family's history aloud to them on the phone, most billing arguments end in a minute.

The second thing was the way in and out. There are guided imports from seven named systems and any CSV, a card request that texts and emails every family a link to add a card and keeps reminding them until they do, a cutover checklist that holds your first billing run until you approve it, and a full data export available to the account owner at any time. Your data being portable is not a feature we charge for.

What we believe about this market

• One studio, one set of facts. A scheduler, a payment processor, a mailing list and a website that disagree with each other is the actual problem. Live data is why the schedule on your website can't be last term's.
• Say the quiet part. Every risk score shows which rules produced it. Campaign results show the registrations that actually followed, not just the clicks. Software that can't explain itself can't be trusted with your enrollment.
• Your money is yours. You are your own merchant of record on Stripe, and we take no application fee on what your families pay you.
• One core, not seven forks. Dance, gymnastics, cheer, camps, theater, swim and music differ in words and defaults more than in mechanics. Those live in a configuration pack, not in branching code, which is why a fix for one discipline is a fix for all of them.

What we haven't built

We'd rather you find this out here than in month two. There is no payroll or time clock, no skills or belt progression tracking, no door access control, no full point-of-sale with inventory, no Zapier or outbound webhooks, no calendar feed subscriptions, no saved custom report builder, no competition-team management, no private lesson booking, no multi-location under one account, no native mobile app, and no public API.

Some of those are coming. Some we've decided against: the parent portal installs to a phone home screen and takes push notifications, which is why there's no app store build to wait on. If something on that list is a dealbreaker for your studio, tell us: that's how the order changes.

Where we are

Early, and building with studios rather than at them. There are no customer logos on this site yet because we don't put names up without permission, and no testimonials because we'd rather have an empty section than an invented one.