Gym and Studio Billing and Booking Systems: Cost Guide
A guide for gyms, studios and lesson schools to member management, auto-billing and booking systems: cost ranges for SaaS, combined tools, custom builds.
Gyms, yoga and dance studios, and lesson schools run on members who come every month and pay a monthly fee. Member records, bookings, billing and collection, and handling withdrawals and suspensions are the backbone of the business. As member counts grow, spreadsheets plus cash and bank transfers stop keeping up with questions such as who has paid and who is on leave. This article, written for owners without in-house IT staff, covers the options for systemizing member management, automatic monthly payments and booking, typical cost ranges, the operating rules to decide first, and a pre-adoption checklist. All figures are general guidelines; real quotes vary widely with features and member counts.
Why membership and monthly-fee businesses need a system
Most revenue in a monthly-fee business comes from recurring charges, so a missed invoice, an uncollected payment, or a late cancellation goes straight to profit. In the early days, with a few dozen members, staff who know every face can manage. At 100 or 200 members, or with more locations and classes, problems like these surface.
- Matching payments against bank or card statements takes hours every month
- Contact with members whose payment failed is late, and unpaid amounts pile up for months
- Suspension and withdrawal requests arrive by word of mouth or chat, and the member is billed again the next month (leading to refunds)
- Bookings and make-up requests come by phone, chat and paper, causing overbooking and double bookings
- There is no entry record, so card sharing or use after withdrawal cannot be checked
These are easy to postpone when things are busy, but leaving them alone costs both revenue and staff time. The starting point is to decide which of them you actually want to fix.
Three options to consider
There are roughly three ways to systemize member management, monthly payments and booking. Which fits depends on size and how unusual your rules are.
| Option | Typical initial cost | Typical monthly cost | Best for | Strength | Caution |
|---|---|---|---|---|---|
| 1. Packaged SaaS for gyms and schools | Zero to a few hundred thousand yen | A few thousand to tens of thousands of yen (varies with members) | Single to a few locations with dozens to hundreds of members | Member management, booking, billing and entry control in one package | Pricing and features are fixed; unusual rules are limited to what settings allow |
| 2. General booking SaaS plus a payment service | Zero to tens of thousands of yen | A few thousand to tens of thousands of yen (payment fees extra) | Many class types, or owners who want to keep existing tools | Cheap to start; replace only the parts you need | Member records, booking and payment end up separate, leaving double entry and reconciliation |
| 3. Custom development | Several million yen and up | Maintenance extra (often tens of thousands of yen per month) | Unique pricing, multi-location standardization, or required integration with existing systems | Built exactly to your operations | High cost and long lead time; ongoing maintenance is your responsibility |
For single to a few locations, it is usually realistic to start with option 1 or 2 and consider option 3 only once the unmet, specific requirements are clear. Jumping straight into custom development tends to inflate costs while requirements are still vague. For how development costs are built up, see system development cost guide.
Cost guidelines
Cost depends on member count, number of locations, and features such as automatic payments, entry control and apps. The figures below are general guidelines; pricing differs by product, so always compare several quotes.
| Scale | Packaged SaaS (monthly) | General booking SaaS plus payments (monthly plus fees) | Custom development (initial) |
|---|---|---|---|
| 50-100 members (single location) | A few thousand to roughly 10,000-20,000 yen | A few thousand to about 10,000 yen plus payment fees | Several million yen and up (rarely worth it at this size) |
| 200-500 members (1-3 locations) | Roughly 10,000-50,000 yen | About 10,000-30,000 yen plus payment fees | Around 3-8 million yen as one guide |
| 1,000+ members, multiple locations | Tens of thousands of yen and up (quote needed) | Integration effort grows and management gets complex | 8 million yen to tens of millions (depends on requirements) |
Besides the monthly fee, expect payment fees (commonly a few percent of the amount for cards and tens to low hundreds of yen per transaction for bank direct debit), entry-control hardware, and data migration or setup fees. A low monthly price can be overtaken once those are added, so compare total cost over one year. For the booking portion, see reservation system cost guide.
Automatic payments: direct debit versus card subscriptions
The two main ways to collect monthly fees automatically are bank direct debit and recurring card billing. Both remove manual billing and reconciliation, but they behave differently.
| Method | Effort for the member | Typical fee to you | Failure risk | Lead time |
|---|---|---|---|---|
| Bank direct debit | Paper or online account registration at sign-up | Tens to low hundreds of yen per transaction | Some debits fail for insufficient balance | Bank procedures can take several weeks |
| Recurring card billing | Register a card and done | A few percent of the amount | Failures from expired cards or limits | Relatively short (screening applies) |
| Bank transfer or cash | Member pays each month | Little (decide who bears transfer fees) | Forgotten payments are common | None (but checking is manual) |
Suitability depends on your members. If many are younger or pay cashless day to day, card billing is easy and lowers the sign-up barrier. For older members, or schools whose families rarely use cards, direct debit remains in strong demand. Many businesses offer both. As a rule, avoid storing card numbers yourself and choose a setup where the payment provider holds them. For the basics of fees, see cashless payment cost and fees.
Decide how to handle unpaid and failed payments first
Even with automatic payments, failures never reach zero: insufficient balance, expired cards, or exceeded limits will cause some charges to fail each month. Before adopting a system, decide the rules for when this happens.
- When and how to contact the member (email, chat, phone)
- How many retries and at what intervals (for example, retry the next business day, then once or twice within the month)
- Whether to restrict booking or entry until payment is confirmed
- How to treat prolonged non-payment (treating it as withdrawal, steps for ending the contract)
- How to issue invoices and receipts for the unpaid amount
Some systems can send failure notices, retry, and restrict bookings automatically. If yours cannot, you need a person and a routine to review the unpaid list every month. Also check that your terms of use or sign-up form state what happens on non-payment.
Withdrawals, suspensions and plan changes cause the most manual work
In monthly-fee businesses, withdrawals, suspensions and plan changes often generate more manual work than sign-ups. Check these points when choosing a system.
- Can mid-month withdrawals be billed according to your rules (prorated, stopping next month, usable until month end)?
- Can suspensions be handled as free, discounted, or charged a separate suspension fee?
- Can plan changes (once a week to twice a week) and family discounts switch next month's amount automatically?
- Where are withdrawal requests accepted (member page, chat, front desk), and what is the cutoff date?
- How long is member data kept after withdrawal, and how is it deleted?
Because mid-month withdrawal rules differ by business, use a demo or free trial with your real cases to see whether the standard features suffice or manual work remains. Some continuing services, such as certain lessons, language schools and tutoring, may be subject to legal rules on cancellation and refunds. Check whether yours applies through public information such as the Consumer Affairs Agency, or ask a specialist.
Booking and attendance: class-based versus open access
Needed booking features depend on the business model. Fixed classes such as yoga or dance center on capacity, waiting lists and make-up requests. Open gym floors matter more for entry records and crowding. One-to-one sessions need per-instructor availability and remaining-ticket tracking.
- Class-based: capacity, waiting lists, make-ups for absences, handling no-shows
- Open access: crowd control by time slot, caps on visits
- Individual slots and ticket books: instructor availability, ticket expiry and remaining count
- Common: booking reminders, cancellation deadlines, attendance history per member
A booking-focused tool can be easier to use, but if booking is not linked to member status (suspended, unpaid), a suspended member may still be able to book. Whether member data, payments and booking can be managed together or linked is often the deciding factor. For the cost of building your own member site or pages, see membership site development cost.
Entry control: QR codes, IC cards and smart locks
Gyms and unstaffed studios also need entry control. Methods include tapping an IC card, showing a smartphone QR code, and unlocking through a smart lock. In each case, what matters is whether member status (active, suspended, unpaid) is reflected in whether entry is allowed.
| Method | Feature | Typical cost | Caution |
|---|---|---|---|
| Staff check at the front desk | No extra cost | Almost none | Needs staff and leaves few records |
| QR code (smartphone) | No membership card to issue | Reader hardware (from tens of thousands of yen) | Need an alternative for members without smartphones |
| IC card | Simple for members | Cards plus readers (tens to over a hundred thousand yen) | Need a process for lost cards and reissue |
| Smart lock integration | Suits unstaffed or late-night operation | Hardware and installation (from tens of thousands of yen) | Decide procedures for power or network outages |
Hardware may be limited to models your chosen SaaS supports. Buying devices first can leave you unable to integrate, so select the system and the hardware together. Entry logs are personal information, so decide retention periods and who can view them.
Data migration pitfalls
Migrating from spreadsheets or another system takes more effort than expected. Member lists, contract details (course, fee, start date), remaining tickets, suspended members, and stored payment details all need to be reorganized for the new setup.
- Clean up duplicates and inconsistencies (name spacing, full-width versus half-width characters, old addresses) before migration
- Check that each member's fee, discount and start date match both the list and actual billing
- Card data usually cannot be moved to a new payment provider, so members need to register again
- Direct debit may require new account registration under the new setup
- Fix the last billing date in the old system and the start date in the new one to avoid double or missed billing
- Keep the old data as a backup for a period
Assume card and account details cannot be migrated, and allow time to notify members and have them re-register. Rather than switching everyone at once, start new members on the new setup and move existing members in stages to reduce confusion.
How to decide
When unsure, work through these steps.
- Rank the problems first: collection, booking, or entry control
- Enter your own fee rules (proration, suspensions, family discounts) in a packaged SaaS trial or demo
- If only a few things are missing, check whether a general booking SaaS plus payments can cover them
- Consider custom development only if unique requirements remain non-negotiable
- In every case, compare one-year total cost and check that data can be exported (for example CSV) when you switch
With 100 members or fewer and collection as the only issue, a payment service with a simple ledger is often enough. With several hundred members and separately managed suspensions, bookings and entry, the benefit of consolidating on a packaged SaaS is large. Businesses with multiple locations and unique pricing may need custom development or integration with existing tools.
Pre-adoption checklist
- Have you ranked the problems (collection, booking, entry, withdrawal handling)?
- Do you know your current member count, the next one to two years' forecast, and number of locations?
- Have you documented fee rules (proration, suspensions, family discounts, enrollment fee)?
- Does direct debit or card billing suit your members?
- Have you set rules for contact, retry and booking restrictions on failed payments?
- Have you set how withdrawal and suspension requests are accepted and the cutoff date?
- If entry control is needed, did you confirm hardware and system compatibility?
- Did you compare one-year totals including initial, monthly, payment fees and hardware?
- Have you checked where member data is stored, who can access it, and deletion rules after withdrawal?
- Did you try your own cases in a free trial or demo?
- Can data be exported (such as CSV) when you switch?
- Do you have a schedule for notifying existing members and re-registration?
Is a system worth it with only around 50 members?
If checking payments and handling suspensions or withdrawals already takes time every month, yes, even at a small scale. At this size a SaaS costing a few thousand yen a month, or a payment service with a simple ledger, is often enough. Cutting collection effort first is more realistic than building something large.
Which is better, direct debit or card subscriptions?
It depends on your members. Card billing is easy if many members are younger and use cards daily, while direct debit stays in demand with older members and families who rarely use cards. Offering both is common. Fees are commonly a few percent of the amount for cards and tens to low hundreds of yen per transaction for direct debit.
Can I keep using my current booking tool?
Often yes, but booking may no longer reflect member status such as suspended or unpaid. Keeping booking in the old tool while running members and payments elsewhere leaves double management. First check whether your booking tool can integrate with member management and payments.
Can card details be moved to a new system?
Usually not. The payment provider holds card data, so changing providers means members must register their cards again. Direct debit may also need new account registration. Plan the notices and re-registration period before switching.
When should I consider custom development?
When packaged SaaS cannot reproduce your fee rules and much manual work remains, when you need to standardize unique pricing across locations, or when integration with a core system is mandatory. Trying packaged SaaS first and building only the gap usually keeps costs lower.
Summary
For membership and monthly-fee businesses, systemizing collection, booking, withdrawal and suspension handling, and entry control reduces missed billing and checking work. The three options are packaged SaaS, general booking SaaS plus payments, and custom development. Most businesses start with packaged SaaS or a combination and consider development once the gaps are clear. Before choosing, write down fee rules, failed-payment handling and withdrawal cutoffs so quotes and demos are easier to compare. Compare costs over one year and confirm how data can be taken out.
Related free tools (no sign-up, instant results)
Feel free to contact us
Contact Us