Zatrovo vs Punchpass: Which Fits a Growing Class Studio?

Punchpass wins on price and speed for a class-only timetable, and its entry plan is the cheapest way to run one according to its published pricing page. An all-in-one platform wins once appointments, percentage-paid instructors and more than ten automations enter the picture. The Four-Gate Test below tells you which side of that line you sit on.

Disclosure: Zatrovo publishes this blog and is one option discussed below. We have represented every competitor as fairly as we can. Pricing is sourced from vendor websites as of 2026-08-25 and linked below.

Most comparison posts stop at a feature grid. Feature grids do not tell you what happens at 5:45pm on a Tuesday when a client wants a private session, the 6pm class is full, and your instructor is paid on a revenue share. That is where these two tools genuinely diverge.

What does Punchpass actually cost?

Three plans, flat monthly pricing, no per-member tier jumps. The cost decision is which feature sits behind which plan, not the headline number.

At the time of writing, Punchpass lists three tiers, Grow, Flow and Pro, at roughly $59, $99 and $149 per month, with a discount for annual billing. Confirm the current numbers on that page before you budget, because vendor pricing moves without notice. All three tiers include unlimited classes, passes and instructors.

The number that matters is the membership gate. Recurring memberships sit on Flow, not Grow. If you sell a monthly unlimited, your entry price is the Flow number, not the Grow one. That single line is worth more to your budget than any feature-grid row.

Processing sits outside the subscription. Punchpass states that the subscription is the only fee it charges, and that Stripe charges its own fee per successful card payment.

Where does the automation cap bite first?

Punchpass tiers automations by plan, from a handful on the entry plan to around ten mid-tier and uncapped at the top. A studio running a proper intro offer burns through ten faster than owners expect.

Write down the automations a class studio actually needs. Intro-offer welcome on day one. A day-five nudge to book visit two. A day-twelve "three classes left" message. A day-twenty-one expiry warning. A first-visit-no-return trigger at ten days. Card decline dunning at day one, day three and day seven, which is three separate rules in most systems. A birthday message. A waitlist promotion notice. An eight-week lapsed win-back.

That is eleven before you have built anything clever. The counterintuitive part is that owners burn their entry-plan slots on receipts and class reminders, which are usually built in and do not need an automation slot at all. Audit that before you upgrade a tier.

Dunning is the one that pays for itself. One recovered monthly membership covers the Grow to Flow difference for roughly three months. If you are not sure where your leaks are, start with spotting at-risk members before they cancel and recovering abandoned checkouts.

How do you decide with the Four-Gate Test?

Four yes-or-no questions about your operation, not your size. One failed gate means stay. Two or more means the cheaper tool is costing you hours.

Gate one, revenue mix. Does more than 15 percent of revenue come from something other than group classes? Privates, workshops, retail, memberships with guest passes.

Gate two, payroll shape. Is any instructor paid per head, on a revenue share, or on a tiered rate that changes above eight attendees? Flat hourly is easy anywhere. Per-head is where you start exporting attendance into a spreadsheet every second Friday. The classification question sits underneath this one, covered in 1099 vs W2 for fitness instructors.

Gate three, automation count. More than ten live rules, per the audit above.

Gate four, reporting cadence. Do you rebuild the same five numbers by hand each month?

Two illustrations. A 180-member reformer Pilates studio with 24 weekly classes, six weekly privates, two per-head instructors and twelve automations fails three gates. A 90-member yoga studio with 18 classes, flat-rate teachers and five automations fails none, and should stay on the cheaper tool.

What breaks when you add appointments to a class schedule?

Booking is not the problem. Punchpass advertises private sessions alongside group classes. Room conflicts and turnover buffers are the problem.

Punchpass's features page describes fast private session creation, waitlist management with alert-all or auto-fill-first behavior, and standing reservations that auto-book regulars into weekly slots. That covers most single-room studios.

Here is the failure mode. You run Studio A and Studio B. Studio B hosts a 60-minute mat class ending at 10am and a 30-minute private starting at 10am. Mats need seven minutes to clear. If the buffer is attached to the instructor rather than the room, the system books it and your desk staff sorts it out in person.

The test is specific. Build one class and one appointment in the same room, back to back, and try to make the software refuse the second booking. If it accepts it, you own that conflict manually forever. Studios adding privates to an existing timetable should also read up on connecting booking through an API before committing.

How should you run waitlists and late cancels?

Waitlists are the highest-return switch on the panel. Vendors report large booking lifts when studios turn them on, so treat the exact multiplier as marketing and judge it against your own fill rate after a month.

The lift is not magic. It is scarcity plus a working promotion rule. The procedure that holds up at a busy desk looks like this.

Set auto-fill-first rather than alert-all for any class inside 12 hours. Alert-all creates a race that annoys four people to please one. Set the promotion cutoff at 90 minutes before start. After that, stop promoting and release the spot publicly, because a client promoted 20 minutes before a 6am class will not see the message.

On late cancels, charge the fee only when the seat goes unfilled. Charging a client whose spot was immediately taken by a waitlisted member is how you lose a member over a $12 fee.

What does a migration actually take, day by day?

Ten working days, run in your quietest month. Name it the 10-Day Cutover and put it on a calendar, because open-ended migrations stall at 60 percent and leave you paying two subscriptions.

Days one to three, export three files. Clients with contact details and marketing consent. Active passes with remaining counts and exact expiry dates. Memberships with next bill date, price and discount.

Day four, ask both vendors in writing whether stored card tokens can be transferred between processor accounts. If the answer is no, your migration is not a data project, it is a re-collection campaign, and you need four weeks of member messaging instead of ten days.

Days five to eight, run both systems in parallel for classes only. Keep billing on the old system. Day nine, freeze schedule changes for 72 hours. Day ten, cut over after the last evening class, then stand at the desk for the first two morning classes yourself.

Across Zatrovo studios, 2026, the step that most often slips is pass expiry dates, because they are the one field nobody checks until a client with three remaining classes is told they have none.

Which five numbers do you need on the first Monday?

Active memberships at month end, net member change, intro-offer conversion by cohort month, occupancy by time slot, and revenue per available seat. Five numbers, not fifty.

Cohort conversion is the one most dashboards get wrong. Reporting "intro offers converted this month" mixes a January cohort with an August cohort and hides a trend. Tag by the month the intro was purchased, then read the number 45 days later.

Occupancy by time slot is where the money is. If the 6:15am Tuesday spin class sits at 61 percent for three consecutive months, the answer is to cut it or move it to 6:30am, not to discount it. Discounting a half-empty class trains your best members to wait for a discount.

Revenue per available seat is occupancy times average revenue per attendee. It is the only figure that lets you compare a full drop-in class against a 70 percent full membership class honestly.

When is switching a mistake?

When your real problem is retention or acquisition. Software changes what you can see and how fast you act. It does not change whether people like your 6:15am class.

The current market data supports being careful here. Athletech News reported on ABC Fitness's mid-year 2026 Wellness Watch that new boutique studio joins fell 5 percent year over year while studio cancellations fell 6 percent and studio check-ins rose 27 percent. Existing clients are showing up more and leaving less. The squeeze is on the front end.

Meanwhile the Health & Fitness Association reported a record 81 million US members in 2025, with 26.1 percent penetration among people aged six and older. The market is growing. If your funnel is not, a new booking screen will not be the reason.

Two other bad times to switch. Inside your peak eight weeks, meaning January and September for most studios. And within 30 days of a price increase, because clients will attribute every glitch to the new price.

How do you run a 14-day trial that actually decides it?

Run a Peak Week Trial. Punchpass advertises 14 days free with no credit card required, so spend it on your busiest week with your real schedule loaded, not a sample one.

Then time five tasks with your phone stopwatch, front desk conditions, client standing there.

1. Create a private session mid-conversation and take payment.
2. Move a client from a canceled class into another slot the same week.
3. Refund a half-used class pass and check what happens to the remaining credits.
4. Calculate pay for one percentage-paid instructor for one week.
5. Pull every pass expiring in the next 14 days as a contactable list.

Anything over 90 seconds is a weekly tax. Multiply it by 52 and compare that to the annual price difference. This same stopwatch method works when evaluating any alternative, including the ones covered in Acuity Scheduling alternatives and Arketa alternatives.

One last note on trials. Do the migration dry run in week two, not week one. Exporting your data and failing to import it cleanly is the single most useful thing a trial can tell you, and it is the thing nobody tests until they have already signed.