CRM for a fitness studio: memberships and schedule

"We don't need a CRM, everything's in the group chat and a notebook" — that's how a studio runs while it has thirty clients and one group. Then it starts: someone turns up for a class that isn't on that day, someone's membership pass expired two weeks ago, and the coach remembers it differently. Here's what a CRM for a fitness studio does that a booking log doesn't, and what to look at when choosing one.

What a fitness studio CRM actually is

A CRM (customer relationship management) is software that keeps your clients, their visits and your money in one place. For a studio that means three connected things above all: the class schedule, membership passes and attendance. Connected is the key word. If passes live in a spreadsheet, the schedule lives in a group chat and attendance lives in the coach's head, you don't have a CRM — you have three sources of truth that drift apart by the end of the first month.

"CRM system", "booking software for a gym", "app for booking training sessions" — in search these are different words for the same tool. The difference isn't in the name, it's in whether the system understands group classes and membership passes, or only salon-style slots.

How a studio differs from a beauty salon

Most booking systems are designed around a salon: one client — one specialist — one service — one slot. In a studio almost everything works differently:

• A class is a group event: it has a cap on spots, and a booking is a spot in that group, not a slot in someone's diary.
• The client pays upfront, and not per visit but for a membership pass: what you deduct is visits, not money.
• The schedule repeats week after week — you build it as a grid, not one class at a time.
• A coach runs a group rather than working through a queue: their workload is measured in classes and people on the floor.
• The headline metric isn't the average ticket, it's how full the room is and how much of a pass gets used before it expires.

That's why a salon system where the group is assembled by hand — as a list in the comment field of a booking — falls apart in a studio by month two: the front desk counts the spots, the front desk counts what's left on every pass, and the front desk becomes the only person who knows how any of it works.

Schedule: group classes and one-to-ones

A group class is a time, a coach, a room or branch, and a cap on spots. When booking, the client sees how many spots are left, and that number has to count itself: booked — one spot fewer, cancelled — the spot goes back on sale for the next person. Any manual recount here will sooner or later put two people on one mat.

Personal training runs on different logic: what matters there isn't spots but free windows in the coach's schedule. A system built for studios handles both at once — otherwise one-to-ones end up tracked separately and you're back to two schedules.

Check separately what happens when a whole class is cancelled: the coach is ill, a pipe burst, a public holiday. The system should notify everyone who booked and give them their deducted visits back in one move — not leave the front desk ringing round twenty people and fixing balances by hand.

Build the week as a grid, not class by class

A studio schedule repeats: Monday, Wednesday, Friday at 7pm. Entering that by hand every week is work about nothing, so look for repeating a class on chosen weekdays through to a given date, and for copying a whole week. It saves hours a month, but the bigger win is different: once the schedule is built as a grid, it stops depending on which member of the front desk is in today.

The second question about repeats is what happens to clients who already booked when a class moves. A good system moves the class together with its bookings and notifications. A bad one creates a new class next to the old one and leaves the old one hanging — and half the group turns up at the original time.

Membership passes are the heart of it

The membership pass is the reason studios get a system in the first place. Here's the minimum it has to handle:

• Types: by number of visits, by period (a month, three months) and unlimited for a period.
• Limits by service and class type: a yoga pass shouldn't be deducted for a personal training session.
• Delayed start: bought in December, started coming in January — the clock runs from the first visit, not the sale.
• Automatic deduction on booking and the visit returned on cancellation — with no manual recalculating of balances.
• Freeze with a day limit and clear rules, so you're not negotiating every case over messages.
• Transfer to another person — a legitimate way to close a "give me my money back" argument without giving money back.

And check what the client sees: they should be able to look up their remaining visits and expiry date themselves, in the app or by link. Otherwise the front desk turns into a help desk, and "how many visits have I got left?" becomes the studio's most frequent message.

Waitlist and filling the room

A studio always has both classes with more demand than spots and classes running half empty. The first is solved by a waitlist; the second by finally seeing the numbers by time and class type instead of going on gut feel.

A waitlist works properly when a freed-up spot is offered to the first person in the queue and held for them for a limited time, rather than going to "whoever spots the message in the chat first". Then a cancellation two hours before class doesn't turn into an empty mat, and the client doesn't fall out of their routine.

No-shows, cancellations and rules

A no-show costs a studio more than it looks: the spot was taken, somebody else couldn't have it, and the visit on the pass has to be given back "out of decency". With no rule in place, that gets decided from scratch every time — and every time in the studio's favour, never.

Three things work, and only together: a clear cancellation rule (how many hours ahead cancelling is free), an automatic reminder the day before, and marking attendance after the class. The last one matters most: until attendance is marked, you know neither how full the room really was nor whose pass is expiring without them ever coming in.

Marking it should take seconds and live on the coach's phone — if it means sitting down at the front-desk computer, it won't get done.

Coaches: access, schedule and pay

A coach needs their own login: their own schedule, the list of who's booked for a class, a way to mark who showed up. But not the till and not the entire client base. Roles aren't bureaucracy, they're how you calmly hand access to someone who's been with you three months.

Then there's payroll. Studios usually run one of three schemes: a fixed rate per class, a rate that depends on how many people came, or a percentage of passes sold. All three are calculated from the same data — classes delivered and attendance — so payroll belongs in the same place as the schedule. Working it out in a separate spreadsheet from screenshots of the system is a way to argue with your coaches about numbers every single month.

The one thing payroll must do: every line should show where the figure came from — which class, how many people, which rate applied. Then there's nothing left to argue about.

Where the revenue actually is

The big financial trap in a studio: the money for a pass arrives once, but the service is delivered over three months. Count revenue by sales and a month with a good promotion looks brilliant while the next one looks like a disaster — even though there are more people in the room than before.

So keep pass sales and visits used on those passes as separate lines in your reports. The first is money; the second is the load on your rooms and coaches — and schedule decisions are made on the second.

Online payment saves you less time than it saves you no-shows: people skip a spot they've paid for noticeably less often. Check two things — whose account the money lands in (it should be your own contract with the bank, not "the service's wallet") and what happens to the booking if the payment fails.

What to look at in reports

Systems ship plenty of reports, but six numbers are enough to run a studio:

• How full classes are by day of week and time — what to cut and what to run twice.
• Pass usage: how many visits on an average pass expire unused.
• Renewals: what share of clients buy another pass, and how many days later.
• Lapsed clients: who hasn't been in for longer than their own usual gap.
• Revenue split between group classes and one-to-ones — and across branches if you have more than one room.
• Coach workload: classes, people on the floor, cancellations.

If you can't ask the system for those six numbers without exporting to Excel and assembling them by hand, you won't be running the business on it, however good the dashboard looked in the demo.

Nine questions for the vendor

These cut out almost everything unsuitable while you're still on the demo call:

• Is there a group class with a cap on spots — not "a service for several people", but an actual spot in a group?
• Is a visit deducted from the pass automatically on booking, and returned on cancellation?
• Can a pass be limited to specific class types?
• Are freeze and transfer supported, and can you configure their rules?
• What can the client see for themselves: balance, expiry date, booking and cancelling without ringing the front desk?
• Is there a waitlist, and how exactly is a freed-up spot offered?
• Can a coach mark attendance from their phone without having access to your finances?
• What happens when a whole class is cancelled — notifications and visits returned?
• How do you export your own client base and visit history if you decide to leave?

How to roll it out in a week

Order matters more than speed: start by migrating the client base and you'll migrate it twice. This sequence works:

• Day 1. Class types and classes: names, duration, room capacity.
• Day 2. Two weeks of schedule as a grid, with a coach on every class.
• Day 3. Two or three membership passes — no more. One by visits, one monthly; the exotic ones can wait.
• Day 4. Migrate clients and, crucially, the remaining balances on active passes.
• Day 5. Coach logins and marking attendance on real classes.
• Days 6-7. Online booking: the link in your profile, on your site and in messages to clients.

The most common migration mistake is moving the clients but not the pass balances. A week later the studio is running two systems at once: bookings in the new one, balances in the old spreadsheet. Move the balances the same day as the clients, even if it costs you an evening.

Quick answers

• Does a one-coach studio need a CRM? If you sell membership passes — yes, otherwise you're tracking balances in your head. If it's only one-off personal training, a calendar with reminders will do.
• How is a CRM different from a booking app? The app is the client's way in. The CRM is what stands behind it: the client base, passes, attendance, money.
• Do we have to have our own mobile app? No. Online booking by link solves the same problem; an app makes sense when clients come regularly and check their balance all the time.
• What about clients who book by DM? Book them in yourself, but do it in the system — otherwise spots and balances drift apart again. DMs stay a channel for talking, not for record-keeping.
• How long does switching take? The schedule and passes take a day or two; the team's habits take two to three weeks. One thing speeds it up: agreeing that a booking that isn't in the system doesn't exist.
• Can we run several rooms in one system? Yes, if it supports branches: each gets its own schedule and its own revenue, while the client base stays shared.

SetNow puts all of this in one loop: group classes with a cap on spots and a waitlist, membership passes with automatic deduction, freeze and transfer, attendance marked from the coach's phone, roles and branches, statistics on revenue, time utilisation and peak hours. Clients book themselves and check their own remaining visits — and the studio stops keeping its records in three places at once.