← Back to all posts

Trial classes without losing the thread

August 11, 2026 · 7 min read · by James, half-owner of a dance studio

Almost every studio I've talked to offers trial classes. Almost none of them have a system for it. The parent DMs you on Instagram, or calls, or fills out a form that goes into an inbox nobody checks on weekends. Someone writes the trial down on a sticky note. The trial happens. Then the family goes silent and nobody at the studio knows whether they came, whether they liked it, or whether anyone ever followed up.

Trials are the top of the funnel for a studio. The most important five minutes of a family's relationship with you happens before they've signed anything. If you're running that on sticky notes, you're leaking families.

Why trials are hard operationally

Enrollments are simple: the family fills a form, picks classes, pays, they're in your system. Everything after that is a matter of teaching and billing.

Trials are the opposite. They're a request for something you might not want to give. The family may not fit the class. The class may be full. The instructor may need to say yes or no. There's usually a charge, which you may or may not want to collect up front. Waivers still have to be signed because it's still a kid on your studio floor. And after all that, the trial might not convert, and you've done a lot of coordination for one visit.

Most software doesn't ship a first-class "trial" concept, so studios build workarounds:

  • A Google Form that emails the front desk.
  • A "trial" tag applied to enrollments after the fact.
  • A DM inbox with an unread badge nobody looks at.
  • A recurring "did we follow up with the trial families?" question at staff meetings.

All of these have the same shape: the family's ask sits in one system, the studio's action lives in another, and the two only get reconciled when someone remembers to check. That's how leads die.

What a trial system actually needs to do

Working backwards from "we want more trial requests to convert into enrollments," a real trial system needs to answer five questions cleanly:

  1. Which classes are trialable, and when? Not every class should accept trials year-round. Studios often want a back-to-dance push in August, an open-house pass in January, and nothing in between.
  2. Who can request one? Existing families browsing their portal, prospective families finding your public schedule, or both.
  3. Do you charge for it? A free trial converts more but attracts more no-shows. A paid trial ($15–25 is typical) filters for genuine interest. Both are legitimate.
  4. Does the studio approve every request, or is it automatic? Auto-approve is efficient. Manual review lets you catch obvious mismatches (a 4-year-old asking for advanced pointe) before they show up.
  5. What limits do you impose? One trial per family per class is standard — otherwise families game the system to get free classes. A total cap (three trials all-time, say) prevents the "I'll try everything before I commit" pattern.

A good trial workflow answers all five in the setup, then gets out of the way.

The public-schedule funnel

Most studios I talk to have a public class schedule on their website — it's how prospective families see what's offered. That schedule usually has an "Enroll" button somewhere, which drops them into a full-account signup wizard. That's the wrong ask at the wrong time.

A family visiting your schedule for the first time is not ready to sign up. They're trying to figure out if you have a class that fits their kid. Asking them to create an account, add a payment method, and commit to a season before they've ever met your instructor is a lot. It's the reason enrollment forms have such high abandonment rates.

A trial-request form is a much smaller ask. Parent name, email, phone, kid's name and age, which class they want to try. That's it. No password, no address, no autopay setup. If they come to the trial and love it, you have all the trust you need to walk them through the full registration. If they don't come, you haven't lost anything except one email.

The compounding effect matters: a low-friction trial ask converts a much larger fraction of your public-schedule visitors into some kind of studio contact. Most of those turn into enrollments. A few don't. Either way you have more shots on goal than you did with the enroll-or-nothing form.

Where the follow-up usually breaks

Even studios that do book trials well tend to drop the ball on what happens after. The most common failure modes:

1. The request comes in and nobody knows. A form fills out, an email lands in the front-desk inbox, but nobody's watching it in real time. By the time someone checks Monday morning, the family has already asked another studio too. Fix: bell-notify every admin the moment a request lands, so it can't sit unread.

2. The trial gets scheduled but the family never gets a confirmation. Someone at the studio approves it internally. The family's email inbox is silent. They show up Wednesday and hope. Fix: send an automated confirmation email the moment the admin approves, with the date, time, class, and instructor.

3. The trial happens and there's no next step. Nobody follows up. The family is warm for maybe 48 hours after their trial, then cools. Fix: a defined follow-up. Day of the trial: "hope you had a great time, here's how to enroll." A week later: "we'd love to have you back." A month later: "wanted to check in." After that, mark them inactive.

4. The waiver situation is a mess. Kids can't be on your floor without signed liability. A trial that shows up without waivers signed puts the studio in an uncomfortable position — do you turn them away, do you have them sign at the door, do you just take the risk? Fix: the trial-request flow should collect the same waivers the enrollment flow does, or a subset the studio explicitly configures. Signed before they arrive, not signed at the desk.

The charge question

Free vs paid trials is one of the older debates in the studio world. The honest answer is that both work, and the right answer depends on your local market and your current problem.

Free trials maximize top-of-funnel. Every prospective family that finds your website is one click from being in your class. You'll get more sign-ups. You'll also get more no-shows, more families who "try everything" without committing, and more slots blocked from paying students. If your problem is "not enough leads," free is right.

Paid trials filter. $15–25 is enough to make someone think twice before submitting, without being enough to genuinely deter anyone who's serious. You'll get fewer sign-ups, but the ones you get will show up. If your problem is "we get lots of trial requests but half of them ghost us," paid is right.

The workflow question that matters more than free-vs-paid: when does the family pay? Charging at signup means capturing card details for someone who doesn't have an account yet, which is a lot of surface to build. The simpler model is: the trial request creates a pending charge on their (soon-to-exist) family ledger, and when the admin approves the trial, the charge posts. The family pays through the same portal they'd use for real tuition. If the trial is declined, no charge posts.

This has a nice second-order effect: it forces the family to create a portal account either way, which pre-warms them for enrollment. By the time they show up for the trial, they've already logged in, signed waivers, and seen your studio's actual portal. Enrolling for the season is a much shorter mental leap.

Trials are a marketing surface, not just a workflow

Here's the reframe that changes how a studio treats trials: a trial-request page is the piece of your studio the most cold prospects will see. Not your Instagram, not your homepage, not your class list. The single moment a prospect decides "yes, I want to try this" is when they hit the trial-request button.

Which means:

  • The form should be as short as you can possibly make it. Every field you add is a percentage of families you lose.
  • The email they get after submitting should sound like a person, not a receipt. Something a parent would want to forward to their spouse.
  • The confirmation-of-approval email should include a "reply to this email" line so parents feel like they can ask a real question, not fill out another form.
  • The class they trial into should be an actual good fit — the studio should still filter for age, room, and instructor capacity. A 6-year-old who trials into a 12-year-old advanced ballet class is not going to convert.

What we shipped

Presently now has a first-class trial workflow. The shape:

Admins configure one trial program: which classes are trialable, in which date windows, at what price, whether trials auto-approve or require review, how many trials one family can book, and whether the public schedule accepts guest requests.

Existing families see a Trials link in their portal. Pick a student at the top of the page and the list narrows to classes the student fits age-wise and isn't already enrolled in. Click Request Trial, pick from a dropdown of dates the class actually meets, submit.

Public visitors hitting your public schedule see a Trial Class button on eligible classes. A short form (parent + student + date) creates a family shell in your system and a pending trial request. The family doesn't have to make an account first — you decide whether to accept, and if you do, they get a magic-link email that lets them finish setting up their account without a password.

Admins get a bell notification the moment a request comes in. The Trial Requests page shows pending / approved / declined tabs. Approve with one click and any configured charge posts to the family's ledger. Decline with an optional reason that goes into the family's email.

Waivers integrate. Any waiver marked "required for trial" has to be signed before the request can go through — for portal families using the same waiver-signing flow they'd use for enrollment; for public shell families as part of their post-approval portal setup. A waiver signed once counts for future trials automatically.

Emails are transactional and short. Confirmation on submit, confirmation on approval (or notice on decline), no extra ceremony. Auto-approve trials skip the "we got your request" email because it would be misleading — the family already saw the confirmation.

That's the whole feature. It's not a marketing campaign, an ad platform, or a CRM. It's a small, clean loop that turns "kid wants to try dance" into "kid is on the class roster next Tuesday" with as little friction as possible in between.


James runs a dance studio with his wife and built Presently because nothing else fit the way studios actually work. Presently now includes a full trial-signup workflow with per-class configuration, public-schedule integration, and admin approval flow. See more features or start a free trial.

Studio software, built by a studio owner.

I'm James, half-owner of a dance studio. My wife and I built Presently because the incumbents weren't designed for how studios actually work. 30-day free trial, no credit card.