Skip to main content
GullySystem
Wellness

Business solutions for Yoga studios

Explore software for work such as “Trial class bookings”. Review each business function below, including when it fits and what to check before implementation.

Yoga studios

How the business operates.

Most studios start with a printed timetable and a notebook. That works for one room and one teacher. It fails once passes expire in different weeks and three teachers cover seven batches, because nobody can say who is owed classes or what each teacher has earned.

Class schedule and batches

Lay out the weekly timetable by room, teacher and style, with batch size, a substitute teacher and a cancelled session recorded on the same grid. A change reaches the students booked.

Booking and waitlist

Students reserve a mat for a batch. A full class opens a queue, and the first name in it is offered a freed place by message. The rest wait their turn.

Memberships and class passes

Monthly plans and ten-class passes count down at each check-in. Expiry date, a freeze for travel and a transfer to a family member are held on the pass, so the desk never argues from memory.

Teacher payouts

Per-class and per-head rates for each teacher are applied to classes taken, and substitutes and workshop shares are added to the statement.

Workshops and teacher training

Open registrations for a weekend intensive or a certification course and take instalments. Hours attended are tracked against the hours the course asks for.

Online and hybrid classes

Mark a batch as in-room, online or both, with the link sent to booked students. Mat spaces and online seats are counted separately.

Trial class follow-up

Lists everyone who took a free or discounted first class, with the teacher and style tried. The front desk calls after the session. Converted students are marked against the offer.

Health and injury notes

Holds what each student has told the teacher about a bad knee, pregnancy or recent surgery. Teachers read it before class. Changes are dated by whoever heard them.

Pass freeze requests

Records a student’s request to pause a membership for travel or illness, with dates and reason. The studio manager approves it. Billing and class entitlement shift to match.

Mat and prop stock

Counts mats, blocks, bolsters, straps and rental towels by room and by size. Damaged items are marked for repair or removal. The manager orders replacements before a workshop day.

The records that hold the operation together.

  • Class schedule and batches. Set the weekly timetable by style, hall, teacher and batch time. Changes show at once. Substitutions and public holidays reach every student the moment the desk saves them.
  • Student records. Keep contact details, goals, injury and pregnancy notes, plan history and attendance for every student. The teacher reads the notes before class and adapts the poses for a sore knee or a stiff back.
  • Booking and waitlist. Students reserve a mat in a class, and a full batch holds a waitlist. Cancellation closes before the class starts, and the freed mat passes to the next name in line without a call from the desk.
  • Attendance and check-in. Mark who came from the teacher’s phone, a desk list or a scanned QR code. The session is counted against the pass or the membership. The dated register stays on record for every class, so an absent student is never charged.
  • Memberships and class passes. Sell monthly memberships, ten-class passes and drop-ins, with sessions left and expiry dates kept on each plan. A freeze for travel, illness or pregnancy is recorded with the dates it covers.
  • Fees, billing and renewals. Issue receipts and tax invoices for plans, workshops, mats, blocks and straps. Students whose plan is ending are listed at the desk before the last class. The renewal conversation happens at the door. Receipts print from any phone.
  • Teacher payouts. Calculate what each teacher is owed from classes taught, per class or per head, at the rate set for that teacher. A substitute teacher is credited for the sessions they actually led, and the owner reviews each month’s pay total before it is approved.
  • Workshops and teacher training. Run weekend intensives, pranayama courses and teacher training batches. Each has its own fee, intake list, module dates and attendance, kept apart from the regular timetable and the drop-in sheet. A trainee’s fee instalments stay on one page.

Operational bottlenecks to check

Pass balances are not written against the student

A student claims four classes left, the desk thinks two. Without a count that falls at each check-in, the argument is settled by whoever is more polite on the day.

A full room has no waiting list

Eight mats are booked, a ninth student arrives, and cancellations come in too late to use. Nobody is called from a queue, so the freed mat stays empty.

Renewals are noticed after a pass lapses

A student stops coming because the plan ended last week, and the desk finds out only when the mat stays empty for a fortnight. No reminder went out. Nobody rang.

Teacher payouts rest on handwritten sheets

Per-class and per-head rates differ between teachers, and a substitute class is added by hand when someone is ill. Month end takes an evening, and a teacher who disagrees with the total has no sheet to point to.

Workshop payments sit apart from class fees

A weekend intensive and a teacher training course are paid in instalments recorded in a separate notebook, far from the student’s regular record. Nobody sees the whole account in one place.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Enquiry and trial

    An enquiry arrives by phone, WhatsApp or the website. Front-desk staff book a trial class and note the student’s goals, any back or knee injury and any pregnancy, so the teacher is prepared.

  2. 2. Joining

    The student picks a monthly membership, a ten-class pass or a drop-in. The payment is recorded, and the plan starts on the date chosen, not the day it was paid. Then the first class is booked.

  3. 3. Booking

    The student reserves a mat in a batch. A full class opens a waitlist. A cancelled mat goes to the next name.

  4. 4. Class

    The teacher opens the class on a phone and marks who is on a mat. One session comes off the pass, or the day counts against the membership, before savasana ends. The register is dated and timed.

  5. 5. Month end

    Classes taught by each teacher meet the rate agreed for them. Substitutions and covered batches are counted to whoever took the room, and the month’s payout is ready for the owner to approve.

  6. 6. Renewal

    Students whose plan is ending are listed a week ahead. A reminder goes through WhatsApp, text message or email. The renewal is recorded when payment is taken, so the plan carries on without a gap.

Roles and responsibility boundaries.

For studio owners

See collections by plan, active members, renewals due, attendance by class and the teacher payout for the month. Approve any change to a teacher’s rate before it reaches the payout run, with that month’s sessions per teacher beside it.

For the front desk

Take enquiries, book trial classes and sell plans. Record payments. Hand out mats, bolsters and blocks, and check a student in at the door.

For teachers

See your classes for the week, the students booked, their injury and pregnancy notes and the classes counted toward your payout, cover classes included.

For students

See the timetable, reserve a mat, check the remaining sessions and the plan end date from a phone. No call to the desk is needed.

Reports your managers need.

  • Attendance by class, batch, hall and teacher
  • Active memberships and ten-class passes with sessions left
  • Renewals due, frozen plans and lapsed students
  • Collections by plan, intensive, teacher training and retail
  • Teacher payout by class taken and cover class
  • Enquiries, trial classes and resulting memberships

Connections to scope

  • WhatsApp
  • SMS
  • Email
  • Wallet and payment gateway
  • QR code check-in
  • Accounts export on request

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Your timetable and halls

Styles, batch times, halls, class sizes and teachers go in first, as the studio runs them today, so the screen matches the wall chart.

Plans and passes

Monthly memberships, class passes, drop-ins and workshop fees are entered with their validity. The freeze and hold rules for travel, illness and pregnancy follow the studio’s own practice, and nothing is invented for it.

Teacher rates

Each teacher’s rate, per class or per head, is set the way the studio pays today. Substitutions follow the same rule.

Students and balances migrated

Student lists, phone numbers and pass balances arrive from your paper register or current software, and balances are checked against the desk’s own count first. Nothing is retyped.

Hosting for the studio

GullySystem hosts the system. Our team carries out any timetable or payout rule edit when asked.

Limitations to settle before implementation

  • A teacher who takes a handful of private students gets by on a notebook and cash payments.
  • A gym with machines, lockers and trainers will find Gym Management Software fits that work better.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Trial class bookings
  • Renewal of monthly and quarterly passes
  • Teacher training enquiries
  • Workshops and retreats
  • International Yoga Day on 21 June
  • Corporate and apartment-complex classes
  • Online batches for people who move away
  • Reactivating lapsed students
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. 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