Service

Gym software development

For gym owners and operations managers who need memberships, class capacity, inductions, personal training packages and door access designed around how their sites actually open, fill and renew, rather than a generic membership app bent to fit.

The problem

What goes wrong today

Where it usually starts

An independent gym with two sites runs memberships through a direct-debit provider, classes through a free timetable app, inductions through a diary on the front desk and door access through a fob system that nobody has reconciled with the membership list since it was installed.

  • A member cancels their direct debit and keeps training for three months because the fob still works.
  • Another freezes for a holiday, is charged anyway and argues at the desk, where the receptionist has no record of the freeze because it was agreed by text with the manager.

Where it gets harder

The 6pm spin class has sixteen bikes and twenty-two names on the sheet; four people are turned away at the door while two booked members never arrive and nobody is penalised, so the waiting list is a formality.

  • A new joiner books an induction for Tuesday with an instructor who is on holiday.
  • Off-peak members train at peak and nobody can tell without checking a card.
  • Personal training packages are sold by the trainers themselves, so the owner does not know how many sessions are owed to members.
  • At month end the owner cannot say how many members joined, lapsed or froze, which classes are full every week and which run at half capacity, or which members have not checked in for a month and are about to leave.

Scope of the service

What the build covers

A custom gym build normally covers:

  • Membership plans with joining rules Peak and off-peak access windows, class credits, freezes with a maximum duration and cancellations with notice periods
  • A member record With a health declaration recorded as a questionnaire at joining, emergency contact and check-in history
  • A class timetable with per-class capacity Instructor assignment, booking windows, a waiting list that promotes automatically and a late-cancellation rule
  • Induction booking against instructor availability
  • Personal training packages sold as session packs and drawn down By the trainer
  • Recurring billing through a payment adapter With failed-payment handling that changes access status
  • A door or turnstile access integration point That asks the system whether a fob or code is valid at that moment
  • Attendance and retention reporting by plan Site and class

How discovery works

Discovery follows one member from first enquiry to renewal with you: how they join, what they sign, when they are inducted, how they book and miss classes, what happens when their payment fails, how a freeze is agreed and how a cancellation is served. Each becomes a named workflow stage in the scope document.

  1. Join
  2. Induct
  3. Book
  4. Check in
  5. Pay or fail
  6. Freeze
  7. Renew or cancel

Deliberately out of scope

  • Supplying or installing door hardware, which stays with your access-control supplier and is connected through its published interface
  • Nutrition or training advice of any kind
  • Payroll for instructors
  • Accounting

When the scope grows

Scoping scenario

A three-site gym group with a group membership valid at every site, a single-site plan at a lower tier, two studios per site with different class capacities, eleven instructors who teach across sites and a turnstile at each entrance needs access decisions that know which site a member is standing at, class capacity per room and an instructor rota that spans sites. That is a different build from a single gym with one studio and a receptionist checking cards, and the scope document says so.

Deliverables

What you receive

  • Discovery notes from following one member from enquiry to renewal and one instructor through a teaching week
  • A written scope document naming each membership stage, the access rules, the class capacity model and what is out of scope
  • Design of the member portal, the front-desk check-in view, the class timetable and the manager reports on phone and desktop
  • The build, deployed to your hosting or ours
  • Migration of member records, active plans and future class bookings from your current membership app, where practical
  • Training for the front desk, instructors and the manager, with a short written guide
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access, contacts, your current membership export, timetable, induction diary and the documentation of your access-control and payment providers.

    Project stage: Onboarding
  2. Planning

    Discovery with the owner, the front-desk lead and a senior instructor; the membership stage model, access rules and scope document are agreed with a milestone plan.

    Project stage: Planning
  3. Design

    Clickable designs of the member portal, the check-in view, the timetable and the retention report, checked on the devices the front desk actually uses.

    Project stage: Design
  4. Development

    Built in stages: plans and member records first, then billing and access status, then the timetable with capacity and waiting lists, then inductions, PT packs and reporting.

    Project stage: Development
  5. Client review

    Your team runs a mock week: joins, a failed payment, a freeze, a full class with a waiting list and an induction, and tells us where it does not match the desk.

    Project stage: Client review
  6. Revisions

    Plan rules, access windows and capacity behaviour are adjusted from the review and re-checked against the scope document.

    Project stage: Revisions
  7. Ready for launch

    Members migrated, recurring payments tested with the provider, door access tested with real fobs you control, launch checklist signed off.

    Project stage: Ready for launch
  8. Delivered

    The gym runs on the new system; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Door, turnstile and locker access-control systems through their published interfaces
  • Direct-debit and card payment providers for recurring membership billing and one-off sales
  • SMS and email providers for booking confirmations, waiting-list promotions and failed-payment notices
  • Accounting software for membership revenue and PT package reconciliation
  • Calendar feeds so instructors see their classes and inductions on their own phone
  • Wearable and fitness-tracking platforms where a member chooses to share activity data
  • Body-composition and fitness-testing equipment that exports results per member

How we would approach it

Worked example

Concept demo

A three-site gym group with cross-site instructors and turnstiles

The situation

A gym group with three sites sold a group membership valid everywhere and cheaper single-site plans, and its turnstiles let anyone with a fob into any site because the access list was a flat export.

Why it is a custom build

This needs a custom build because the access decision depends on plan, site, time and billing state together, and that combination is exactly what a flat fob list and a separate membership app cannot represent.

The scope we would propose

  • An access decision service that answers each turnstile with the member's plan, the site they are at, the time of day and their payment status, so a single-site off-peak member is refused at a different site at 6pm with a reason the front desk can see
  • Class capacity defined per studio per site
  • An instructor rota across sites that drives which classes are bookable
  • A retention report that flags members with no check-in for a chosen number of days at any site

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of sites and whether memberships are valid across them
  • Number of plans and the complexity of peak, off-peak and class-credit rules
  • Access-control hardware and what its interface supports
  • Payment provider and how failed payments and freezes must be handled
  • Number of studios, instructors and classes per week
  • Personal training packages sold online and drawn down by trainers
  • Volume of member records and bookings to migrate
  • Custom reporting such as retention, attendance by hour and class fill rates
  • Hosting choice: your own hosting or ours

FAQ

Frequently asked questions

Would the package do, or do we need a custom build?

A single-site gym with a handful of plans, one or two studios and a standard access reader is usually well served by the gym membership package configured around your timetable. Custom work is the honest answer for multi-site access rules, unusual plan structures, a specific turnstile or locker system, or reporting the package does not ship. Discovery settles it before anything is quoted.

Can you connect our existing door or turnstile system?

Where the access-control supplier publishes an interface, we scope the connection against that documentation and your contract with them. The system decides whether a fob or code is valid at that moment; the hardware remains the supplier's responsibility and we never promise a connection before we have seen what the interface allows.

How is the health declaration handled?

As a recorded questionnaire completed at joining and renewed on a schedule you set, stored against the member with a timestamp and shown to the instructor before an induction. The system records answers and flags where you ask it to; it does not interpret them or give health advice, and the questions are yours.

What happens when a direct debit fails?

The payment provider reports the failure, the member record moves to a status you define, access can be restricted after a grace period and the front desk sees why. Retries and notices follow rules agreed during discovery rather than anything hard-coded.

Who owns the system afterwards?

You do. Source code, member records, bookings and reports are handed over at delivery; hosting and maintenance are optional and separately agreed, and you can move the system to another provider.

Get a project quote for gym software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote