Two paths into a studio account — what parents actually do at signup

When you watch parents try to sign up for a dance class for the first time, two very different things are happening, and the software you use either knows that or it doesn't.

The first kind of parent is decided. They know what class they want their kid in (because a friend recommended it, or they saw it on Instagram, or last year's recital sold them). They want to enroll. They want a portal account because they need a portal account to enroll. The account is friction on the way to the thing they actually want.

The second kind of parent is browsing. They've heard of the studio, they're not committed yet, they want to look at the schedule, see if anything fits, and maybe also sign up for emails so they don't lose the studio's name in their tabs. They don't want to fill out a registration form. They want to look.

Most studio software has one online-registration form. Both kinds of parents are dumped into it, and the second kind quietly closes the tab.

What "one big form" costs you

We watched our own registration flow for a while and noticed something uncomfortable: the bounce rate on step 1 was high. Step 1 was: first name, last name, email, phone, address, city, state, zip, password, confirm password, reCAPTCHA, and then a "Continue" button that took you to step 2 (students), then step 3 (classes), then step 4 (payment), then a confirmation screen.

If you're the first kind of parent — decided, ready to enroll — you'll grind through it. Annoyed, but you'll grind. If you're the second kind, you won't. You came to look at classes and you got hit with a wall.

A few specific things were going wrong:

The form was asking for things we didn't need yet. Why does a parent need to type an address before they've seen the schedule? They don't. The address is for invoices and receipts. It can come later.

The password was a real barrier. Parents don't want another password. They want to do the thing, then come back to the thing. We had a meaningful number of forgot-password resets two weeks after registration.

The "claim an account" path didn't exist. Parents who wanted to set up an account but weren't ready to enroll had no option. The form assumed enrollment.

The model that actually fits

Once we admitted the two kinds of parents needed different on-ramps, the design got simpler instead of more complicated.

Path A: browse the schedule. Pick a class. Drop your email. The parent lands on the studio's public schedule (which doesn't require an account at all), clicks "Enroll" on a class, and a small modal asks for their email — nothing else. We send them a one-click sign-in link. They click it, land in the wizard with the class already in their cart and step 1 already done, fill in the student's info, and check out.

Path B: just create an account. The parent clicks "Create an account" from the family portal sign-in page. The form asks for name + email. Password is optional. They get into the portal. The portal nudges them with a checklist — add a student, add a payment method, enroll — but doesn't make them do any of it before they can look around. They can come back next week when they're ready.

Both paths converge on the same family record. The studio sees one family, regardless of how they got in. But the parent's first interaction with the studio matches what they were trying to do.

The "no password" decision

This is the part of the rework that felt risky and ended up being the easiest. Passwords are friction. Magic links — a one-time-use email link — are not.

For the kind of software a parent logs into 2–3 times per season, magic links are strictly better. The parent doesn't have to remember anything. They don't have to write anything down. They don't have to do a password reset. When they want in, they go to the portal, click "Email me a sign-in link," and they're in within a minute.

We still let parents set a password if they want one — some do. But it's an option in the account page, not a required setup step. Most parents never bother, which is fine.

We also use magic links when the studio creates a family by hand at the front desk. Instead of inventing a password and having to remember to tell the parent what it is (or sending a "set your password" email that they ignore), the studio sends a welcome email with a sign-in link. One click, the parent's in the portal. No password setup, no forgotten link, no manual handoff.

What "browse first, enroll second" looks like in practice

The interesting thing about the browse path is that it doesn't feel like a registration flow at all. The parent looks at the schedule like any catalog page. When they click "Enroll" on a class, the only thing they're committing to in that moment is dropping an email. They don't have to know their student's birthday, their address, whether they want autopay. They just say "yes, this one."

The work of registration gets distributed across the funnel:

• Email at the schedule (browse → drop email).
• Student details when they finally enroll (after the magic link).
• Address at checkout (if they pay) or in the portal account page (if they don't pay right now).
• Payment method at the moment a charge actually happens.

Each ask happens at the moment it makes sense to a parent, not in a blob at the start.

The bit I didn't expect to matter

When we shipped Path A and watched real parents use it, the thing that surprised me was how often it solved a problem that wasn't on my list: parents who never finish registering still have a useful trace. The cart row is on file. The email is on file. The studio can re-engage that family without doing anything heroic.

In the old single-form world, an incomplete registration was usually nothing — the parent gave up on step 1, the form data was thrown away, the studio never even knew they tried. In the new world, an incomplete registration is a stub family with one or two classes in their cart and a magic link that's still valid for a week. We send a friendly reminder 2 hours, 24 hours, and 48 hours later. A real percentage of those families come back and finish.

The takeaway, if you're shopping for software

When you're evaluating studio software, look at the registration flow itself, not just the marketing copy about it. Specifically:

1. Can a parent see the schedule without an account? If no, you're losing the browsers.
2. Can a parent enroll in a class from the schedule, before they have an account? If no, you're forcing the form on people who weren't ready for it.
3. Does the registration form ask for an address before showing them any classes? If yes, the form is built around the database, not the parent.
4. Is the password required, or is there a magic-link option? Required passwords cost you families. Magic links don't.
5. What happens to a parent who starts and bails on step 1? If the answer is "nothing," the studio is losing the silent middle of the funnel.

None of this is rocket science. But almost every studio software product I've looked at gets it wrong, because the registration flow was designed by an engineer looking at a database, not by an operator watching parents try to sign up their kid for ballet.

If you're a studio owner who's lost track of how your own registration page works because nobody on staff ever signs up — go through your own form, as if you were a brand new parent. Fill it out. Time yourself. Watch what it asks for. The result is usually instructive.