Clear answers.
Before any commitment.

GE2studio is in its pilot phase. Access is not yet self-service: usable features and go-live conditions are confirmed after scoping, configuration and testing with the studio.

GE2studio is designed for independent Pilates, Reformer, yoga and boutique fitness studios, as well as studios offering several activities. The scope is assessed against your bookable classes, capacities, offers and team organisation. Feature status still needs to be checked for your studio.

The Pricing page presents the platform, onboarding, options and possible third-party services. The quote depends in particular on the number of studios, volumes, required integrations, data migration and support. The amount and timeline are confirmed in the contractual documents before any commitment.

Describe your activities, capacities, offers, booking rules and the journeys your team cannot do without. If you are changing software, also prepare the available authorised exports. Configuration and testing confirm the scope before a go-live date is chosen.

Members, coaches, activities, rooms, credits, subscriptions, future bookings, booking rules, waitlists and essential integrations are assessed. Each category must be confirmed after checking the authorised exports, their quality and the rules to preserve. The existence of an export alone does not guarantee a complete migration.

Support is defined with the studio: configuration, data migration, testing, familiarisation and launch follow-up. Ongoing support, its channels and hours are specified in the offer and applicable documents. No generic service level is announced on this page.

The planned product is a responsive web application designed with mobile use in mind. The complete Member purchase and booking journey remains in preparation and must be tested end to end. No native app or installable PWA is announced as available; a native app remains a separate development.

Scheduling, booking and the initial catalogue, booking-rights and credit-tracking features are integrated into a controlled environment. New booking rules, the member purchasing journey, waitlists and payments retain their own preparation status. The features actually enabled are confirmed in the offer, then configured and tested before go-live.

Yes, that is the planned organisation according to each person’s responsibilities. Manager and Coach journeys remain limited to tested pilot features; the complete Member journey is in preparation. Access and visible information depend on each role’s permissions.

“Available” means a feature can be used within the confirmed scope. “Pilot” means an integrated feature whose activation still requires configuration, testing and approval. “In preparation” indicates a feature still in development or integration. “Roadmap” means a future or conditional development, without an availability commitment. A demonstration illustrates a use case; it does not prove that the feature is available.

No. They are three levels of depth in the Manager experience, on the same product, data, studio workspace and business permissions. They are neither three roles nor three subscription plans. Smart is the planned default mode. The initial V1 targets Essential and the first Smart components; full Smart remains in preparation and full Advanced is a future development.

The planned copilots must explain calculated results and may prepare an action according to the data and permissions available. A sensitive action requires a preview and human confirmation. Availability is progressive; the full Manager Copilot remains in preparation.

Smart is the planned default mode. It follows five steps: SPOT → EXPLAIN → SIMULATE → QUANTIFY → DECIDE. The manager starts with an important topic, reviews its data and possible explanations, compares scenarios and their estimated effects, then decides. Results are measured afterwards. Full Smart remains in preparation; calculations and assumptions must be verifiable.

The planned questionnaire follows confirmed attendance, at a frequency agreed with the studio. It includes a rating from 1 to 5, the main topic of the feedback, an optional comment and separate permission to be contacted. It is not an NPS survey. The public example on the Experiences page runs locally and does not transmit responses.

The planned Manager view starts with aggregated results: rating distribution, response rate, topics and trends. Access to comments, alerts and any Coach views depends on permissions, the minimum response count and the privacy rules approved with the studio.

A low rating does not trigger a penalty, automatic ranking or autonomous action. It may open a contextual review or a contact request only when the responsible role and the Member’s consent allow it.

Depending on the agreed permissions, an administrator can search for a member or transaction, manage access, handle certain incidents, review the audit log and run authorised exports. The precise scope is approved before go-live.

Exportable data, formats, filters, frequency and recipients are defined in the offer and applicable documentation. A report or format must not be considered included before confirmation.

Backup frequency and retention, restoration tests, monitoring and support arrangements must be defined, verified and documented before go-live. Channels, hours and responsibilities are specified in the applicable documents; no generic response time is promised here.

Notifications within GE2studio and operational emails form the planned foundation. SMS, WhatsApp, Instagram and campaigns remain future developments until providers, permissions, consent, countries and volumes have been confirmed.

A future development is intended to bring together conversations, their history, the person responsible for follow-up and proposed actions before human approval. This presentation does not mean that an email, WhatsApp or Instagram integration is already available.

A future development is intended to connect an underbooked class with eligible members, prepare a campaign and measure its results. No message may be sent without consent, an authorised channel and Manager approval. No commercial outcome is guaranteed.

A calendar invitation or Google/Microsoft integration can be considered. The chosen solution, permissions and synchronisation level are confirmed during scoping; they are not assumed to be active by default.

Replacement depends on the features and integrations your studio cannot do without. These are inventoried, checked and included in the agreed scope before any commitment. A feature list alone does not confirm complete replacement of your current software.

We examine the exports and rules to preserve, prepare a test import, then compare the migrated data with the sources. The migration is rehearsed before your team approves go-live, rollback conditions and the agreed support.

They are not announced as available on the basis of the validated information. TWINT remains under assessment depending on the Swiss configuration and chosen technical solution. ClassPass must be checked if the studio needs it when changing platforms: the contract, technical connection, responsibilities and tests still need confirmation.

The export scope, formats, timelines and exit rules are documented before commitment. Actual portability also depends on data and services supplied by third-party providers.

Responsibilities, access rights, permitted uses, subprocessors, retention periods, exports and exit conditions are specified in the applicable contractual documents before go-live. This FAQ does not replace them.

Sales, collection, refund and reconciliation rules are scoped with the studio and payment provider. Real transactions are never simulated or restored as though they were ordinary data.

No. GE2studio can show collections, revenue and management indicators according to validated definitions, but it does not maintain a general ledger, statutory payroll, VAT returns or tax filings. Accounting remains in dedicated tools and processes.

Remuneration calculation is conditional on the rules actually used by the studio and the agreed scope. It requires approved rules and costs. The planned exports remain management documents; they do not replace payslips.

They are not included by default. Access control can be explored with a partner if the studio needs it; GE2studio does not develop hardware. Point of sale and inventory remain future developments unless a confirmed need changes the agreed scope.

No generic term can be inferred from this site. The commitment, change and exit conditions, and any third-party costs are presented in the quote and contractual documents before signing.

Each project is assessed according to the studio’s country. Currency, payments, practices, data and local requirements must be confirmed before deployment. Potential international expansion does not mean immediate availability in every country.

The Security page distinguishes principles built into the design, checks required before go-live and commitments that must be documented in contracts. It does not claim any certification.