Hero
Data & Knowledge AI
Predictive Modeling & Forecasting
Beauty, Spa & Wellness

Member Performance Analytics and Studio BI for an Indoor-Cycling Franchise


Let's Connect

Overview

What we built

A 45-studio indoor-cycling franchise delivered post-class performance stats from each studio's own siloed bike system, so members saw a one-off email and headquarters had no network-level view of occupancy or instructor performance. We built a central data platform with member dashboards and a BI suite on top.

In plain terms: a 45-studio indoor-cycling franchise had performance data trapped inside each studio's own bike system. A member finished a class, got a one-off email, and that was the end of it, there was no personal trend view that followed them across studios. Franchise headquarters had no network-level picture of occupancy or instructor performance either, so schedule decisions across all 45 studios were made on gut feel rather than on any shared data.

We built a central data platform ingesting bike telemetry and booking data from all 45 studios, then delivered two products on top of it: in-app member dashboards with personal records, trends and cross-studio ride history, and a BI suite giving studio owners and headquarters occupancy heatmaps, instructor benchmarks and early-churn indicators to steer schedules and coaching. 61% of active members now check their performance dashboard at least weekly, booking frequency among dashboard users is up 19% versus non-users over 12 weeks, underfilled class slots fell 14% network-wide after BI-driven schedule changes, and all 45 studios were onboarded within 5 months.

The Problem

Ride stats siloed per studio

Each of the 45 studios in the franchise ran its own bike system, and performance data stayed exactly where it was generated. A member's ride stats lived and died inside that one studio's system, delivered as a one-off email after class and nothing more, with no way to see how a ride compared to last week's, let alone a ride at a different studio.

That siloing worked against the franchise's own structure. Members who trained across more than one studio, which the brand's model encourages, had no personal trend view connecting those rides together. Every studio was an island as far as a member's own history was concerned, even though the franchise itself was one network.

Headquarters felt the same gap from the operator's side. With no network-level picture of occupancy or instructor performance across the 45 studios, schedule decisions, when to add a class, which instructors were drawing riders, were made on gut feel rather than on any shared view of what was actually happening studio by studio.

Siloed studio systems

Each of the 45 studios ran its own bike system, so a member's performance data stayed trapped inside whichever studio produced it.

One-off email, no trend

Members saw a one-off email after class and nothing more, with no personal trend view connecting rides across studios over time.

No network-level view

Headquarters had no network-level picture of occupancy or instructor performance across the 45 studios to inform decisions.

Gut-feel scheduling

Schedule decisions across the franchise were made on gut feel, with no shared occupancy or instructor data to steer them.

What it was costing them

Every studio operating as its own island meant the franchise's own network effect was going to waste: members training across studios got no connected picture of their own progress, and headquarters could not see occupancy or instructor performance across all 45 studios to guide decisions. Schedules were set on gut feel rather than evidence, leaving underfilled slots and uneven instructor performance unaddressed studio by studio.

The Solution

Network-wide analytics platform

We built a central data platform that ingests bike telemetry and booking data from all 45 studios into one place, so a ride's data no longer stays trapped in the studio that generated it. That single platform became the foundation for two products built directly on top of it.

For members, we built in-app dashboards showing personal records, trends and cross-studio ride history, so a rider training at more than one studio finally sees one connected picture of their own progress instead of a series of disconnected one-off emails.

For studio owners and headquarters, we built a BI suite giving a network-level view: occupancy heatmaps, instructor benchmarks and early-churn indicators drawn from data across all 45 studios, letting schedule and coaching decisions be steered by evidence instead of gut feel.

Key decisions

01

Centralise telemetry and booking data

Bike telemetry and booking data from all 45 studios now flow into one central platform, replacing data that used to stay siloed per studio.

02

Build member-facing dashboards

In-app dashboards give members personal records, trends and cross-studio ride history, connecting rides that used to arrive as separate one-off emails.

03

Build a network-level BI suite

A BI suite gives studio owners and headquarters occupancy heatmaps and instructor benchmarks drawn from data across all 45 studios.

04

Add early-churn indicators

Early-churn indicators surface riders likely to drop off, giving studios and headquarters a signal to act on before a member disappears.

05

Steer schedules with shared data

Occupancy and instructor data now inform schedule and coaching decisions network-wide, replacing gut-feel calls made studio by studio.

Measurable Impact

What changed after launch

Members engaged with the connected picture we built for them. 61% of active members now check their performance dashboard at least weekly, and booking frequency among dashboard users is up 19% versus non-users over 12 weeks, suggesting the trend view itself is drawing people back.

Headquarters put its new network-level view to work directly. Underfilled class slots fell 14% network-wide after BI-driven schedule changes, and all 45 studios were onboarded to the shared platform within 5 months, bringing the whole franchise onto one connected data foundation.

Member dashboards

One-off email, no cross-studio trend

61% check dashboard at least weekly

Booking frequency

No connected view driving return visits

Up 19% among dashboard users over 12 weeks

Class scheduling

Set on gut feel, no shared data

Underfilled slots down 14% network-wide

Platform rollout

45 studios each running their own system

All 45 studios onboarded within 5 months

Headline results

61% of active members now check their performance dashboard at least weekly

Booking frequency among dashboard users up 19% versus non-users over 12 weeks

Underfilled class slots reduced 14% network-wide after BI-driven schedule changes

All 45 studios onboarded to the shared platform within 5 months

Tech & Tools Used

What powered the build

Every tool below earned its place in this engagement. Here is the part each one played.

Python logo

Python

Provides the ingestion and processing logic that pulls bike telemetry and booking data out of each studio's own system into the central platform.

Apache Airflow logo

Apache Airflow

Orchestrates the data pipeline across all 45 studios, scheduling ingestion and transformation jobs that keep the platform current.

Snowflake logo

Snowflake

Warehouses telemetry and booking data from all 45 studios, giving both the member dashboards and the BI suite a shared source to query.

dbt logo

dbt

Transforms raw telemetry and booking data into the personal records, trends and network-level metrics the two products are built on.

Metabase logo

Metabase

Powers the BI suite's occupancy heatmaps and instructor benchmarks, giving studio owners and headquarters a self-serve view of network performance.

React Native logo

React Native

Builds the in-app member dashboards, presenting personal records, trends and cross-studio ride history on members' phones.

Node.js logo

Node.js

Runs the backend services connecting the central platform to the member-facing app and the BI suite.

PostgreSQL logo

PostgreSQL

Stores application data behind the member dashboards, including personal records and cross-studio ride history.

AWS S3

Holds raw telemetry and booking data ingested from all 45 studios before it is transformed for the dashboards and BI suite.

Ready to Build your Beauty, Spa & Wellness Business with Predictive Modeling & Forecasting

Ask Byte

Ask Byte

Typically replies instantly

just Now

Hi! I'm OrganByte's assistant. How can I help you today?

AI-generated content may be incorrect


OrganByte

Building innovative software solutions that transform businesses and drive digital success.

© 2026 YourCompany. All rights reserved.