Subscription Billing for Pilates studios
Manage recurring invoice cycles and changes to customer plans.
Does this function belong in your operation?
Use when customers pay recurring charges for continuing access, membership or service.
A recurring agreement starts, renews or changes.
Packs, monthly plans and drop-ins are sold with sessions used and left, validity dates and freezes recorded for each member.
Bring the records the workflow depends on.
- Subscription plans
- Customer billing dates
- Proration and cancellation rules
Outputs to check
- Customer plan and cycle register
- Recurring invoice and adjustment record
- Overdue, paused and cancelled account list
Follow the subscription billing workflow.
Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
Decide how exceptions are handled.
These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.
Can this work independently?
Recurring invoicing can run independently from automatic payment collection. It needs customer plans, dates and approved proration rules. Mandates or payment providers collect funds, while service-access or delivery systems decide entitlement from the agreed account state rather than assuming every raised invoice was paid.
Systems and records it connects with
- Mandates and auto-debit: Provider-confirmed mandates and recurring collection outcomes.
- Invoice management: Issued invoice references, line amounts and outstanding balances.
- Payment gateways: Authorised payment attempts, outcomes and settlement references.
- WhatsApp and SMS: Permitted message content and channel delivery responses.
Configure, test and introduce the workflow.
- We list your plans, cycles and how customers pay. You supply the customer file. A plan sheet comes back.
- Pauses, upgrades and grace periods are written down. You approve each rule. A sample cycle is run in a test copy. Accounts check invoices against what they would raise.
- Debit mandates and payment links are connected. A trial payment confirms the flow. Invoices are raised by the system. Accounts watch the failed list closely.
Check the result before rollout.
Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.
- Each billing period is charged as configured.
- Plan changes apply from the agreed date.
- Cancelled subscriptions stop future charges under the defined rule.
How the business operates.
Reformer, mat and private sessions are booked through Pilates Studio Management Software, which GullySystem sets up for a studio. Instructors and the front desk share one timetable. Classes hold a fixed number of places, with waitlists, session packs, client intake and health notes, attendance and invoices on the same screens. Instructor payouts follow the sessions taught.
The records that hold the operation together.
- Class timetable and capacity. Set weekly reformer, mat, tower and chair classes with an instructor, a room and a fixed number of places for each.
- Booking and waitlist. Take class bookings from the desk or from a client’s phone, with the waitlist and cancellations handled in order.
- Private and duet sessions. Book one-to-one and two-person sessions against an instructor and an apparatus, with their own pricing and notes.
- Session packs and memberships. Sell packs, monthly plans and drop-ins, with sessions used, sessions left, validity dates and freezes recorded.
Operational bottlenecks to check
Class places are counted on a chat group
A reformer class has a fixed number of machines. When bookings arrive by message and call, one more client than the studio can seat may be promised a place.
Pack balances live in a notebook
A client buys a pack of ten sessions with a validity period. Sessions used, sessions left and the expiry date are written in a register that only the front desk can read.
How work flows across this business
This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.
1. Enquiry and trial
A person asks about classes by call, message or the website. The enquirer is booked into an introductory class, and the enquiry is recorded with its source.
2. Intake
The front desk opens the client’s profile and records health notes, goals and any injury, so the instructor sees them before the first session.
3. Booking
A client books a place in a reformer or mat class, a duet or a private session. If the class is full, the booking goes onto the waitlist.
4. Class and check-in
Attendance is marked at the studio, and one session is taken off the client’s pack. The instructor’s count for the month goes up by one class.
5. Billing
A pack, a monthly membership or a single drop-in is billed with its payment mode. Socks and other retail items go on the same invoice.
6. Renewal
When a pack nears its last session or its expiry date, the client is reminded to renew. Clients who have stopped coming are listed for a call.
Industry reports to connect with
- Class fill by day, time and instructor
- Pack and membership balances, with expiry dates
- Instructor classes and payouts for the month
- Late cancellations and no-shows
Questions before implementation.
When should pilates studios consider subscription billing?
Use when customers pay recurring charges for continuing access, membership or service. A recurring agreement starts, renews or changes.
What should we bring to the requirements discussion?
Bring anonymised examples of Subscription plans; Customer billing dates; Proration and cancellation rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.
Does this replace our existing business software?
The starting point is your current system and the gap you need to close. Manage recurring invoice cycles and changes to customer plans. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
Automatic collection is separate from recurring invoicing; contract and tax treatment require approved rules.
How are scope, price and rollout decided?
The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Each billing period is charged as configured. Use this check when reviewing the first working version.
Related functions for pilates studios.
Discuss subscription billing for your business.
Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.
What happens after you share your requirements
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- Review the scope and commercial terms before deciding whether to proceed.
Start with your requirements
Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.
Share your requirements