Scale
1,000-person gymnastics operation
A system shaped for real volume, seasonal demand, and three locations.
Case study 06 / Registration platform
Tumble
Track.
Replacing Jackrabbit for a 1,000-person gymnastics operation.
TumbleTrack is being built for TumbleTown as one system for registration, schedules, billing visibility, day-to-day operations, and a controlled path off the legacy platform.
A concise product walkthrough using synthetic demonstration data. No real family, payment, or account information appears.
Purpose-built replacementRead the 50-second walkthrough
- TumbleTrack is introduced as the Jackrabbit replacement for a 1,000-person gymnastics operation.
- Families move from class search to a guided registration flow with availability and policy context kept together.
- Schedules, capacity, billing, and operational decisions become visible in one purpose-built system.
- Staff can work from the same source of truth across the organization’s three locations.
- A controlled Jackrabbit import and account-claim path supports the transition without pretending it is a one-click migration.
- The close returns to the brief: not another workaround, a replacement.
The brief
Built around the operation. Not the workaround.
Replacing a class-management platform means carrying the real business forward: family accounts, registration rules, money, capacity, staff workflows, and years of records. TumbleTrack is designed around that complete transition, not just a more attractive sign-up form.
- 01
Registration families can follow
Class discovery, availability, eligibility, policies, and checkout stay connected from the first search to confirmation.
- 02
Money stays understandable
Charges, discounts, deposits, and totals are surfaced before a family commits, with recovery paths when payment needs attention.
- 03
Operations share one picture
Enrollment, attendance, schedules, capacity, and reporting are designed as parts of the same operating system.
- 04
Migration is a product feature
Import, validation, account claiming, and cutover controls are treated as core replacement work rather than an afterthought.
Replacement
Jackrabbit to TumbleTrack
The target is a coherent operating platform, not a thin layer over the legacy system.
Coverage
Registration through operations
Family journeys and staff decisions are designed against the same domain rules.
Transition
Controlled import and cutover
Migration safety and reconciliation are part of the build.
Current product direction shown with synthetic demo data. TumbleTrack is in development; this case study does not claim that the final Jackrabbit cutover is complete. Jackrabbit is a third-party product, and this independent project is not affiliated with or endorsed by its provider.
Outgrown the workaround?