FAQ on gym software
in Switzerland

Shared contacts or appointments do not automatically mean that both areas' technical and billing requirements are met. Keep processes separated and check them individually. Suitability for physiotherapy billing or special health data is not guaranteed here for My Gym App.

Boutique studios should especially test booking processes, personal support and their offer structure. For example, check limited course spots or single appointments with realistic cases. Whether the desired tariff and appointment logic is supported can be clarified in an appropriate demo.

Check memberships, access rules, responsibilities and reports by location. Important is which information is shared and which kept separate. Support for your specific multi-location model must be explicitly confirmed; a general admin function is not sufficient proof.

A small studio benefits primarily from simple processes for the services actually offered. Check members, payments, appointments, and necessary supervision effort. Compare total costs with expected benefits and confirm which modules are truly needed.

An implementation plan should include responsible persons, dates, data migration, technical checks, and approval. Also plan for handling queries and disruptions. Define measurable check points for the first operational days and record when the change is considered successful.

Train based on the tasks reception, trainers and management actually perform. Short exercises with typical cases show better than a pure presentation which questions remain open. Clarify in advance which training services are included in the offer and who supports after the start.

Prepare concrete cases: a new member, a subscription change, an open invoice and an appointment booking. Ask about required modules, responsibilities and ongoing costs. Have the steps demonstrated live and note which requirements were confirmed and where clarification is still needed.

First agree on a defined test scope and review anonymized sample data sets in a test environment. Compare numbers, assignments, and technical content with the source. Determine who approves the import and how to handle interim changes during the production switch.

Check for duplicate profiles, outdated contact details, unclear membership statuses, and unassigned invoices. Document professional decisions transparently. Only adopt data necessary for planned operations and for which processing conditions are clarified.

Create an overview of data, contracts, invoices, interfaces and ongoing obligations. Then agree on the scope of the takeover and a realistic schedule. Check sample data and the most important workflows before the switch. An import is only definitively promised after reviewing your data sources.

Prepare a short guide for first steps and test it with some members. Initially show the most common tasks like booking or accessing the training plan. Collect questions and improve the guide before rolling out the app to the entire studio.

An admin app supports processes like bookings, memberships, and documents. A training app focuses on performing and guiding training. One solution can combine both areas; still, check each process individually so that no needed function is only assumed.