GymCash
The trainer’s pocket CFO
Trainer: full access — can log sessions and chase failed payments
- Open the “$500 at risk” card and recover a failed payment
- Search the client list, then log a session with an invalid amount to see validation
- Switch to the accountant role and try the same action
The guided demo runs on sample data in your browser — nothing is connected to a production system and no real transaction is processed. Where a real URL can be framed, the toolbar above switches to it and says so.
Capabilities you could commission.
Supabase auth with email and magic-link sign-in, sessions stored in the device keychain on mobile.
See it on its own →An optional app lock built on the device biometric API — Face ID, Touch ID or Android biometrics — with a passcode fallback and a settings toggle.
See it on its own →Sessions and tokens held in the iOS keychain / Android encrypted storage, never in plain application storage.
See it on its own →RevenueCat sits on top of StoreKit 2 and Google Play Billing: the store still processes every purchase, RevenueCat resolves it into an entitlement the app can check on any platform.
See it on its own →Scheduled local notifications and remote push, with permission handling and a deep link that opens the exact screen the notification is about.
See it on its own →Lead and customer records with history, stage, notes and follow-up state.
See it on its own →KPI tiles and charts over live operational data, with date-range switching and drill-down.
See it on its own →CSV and report exports scoped to a date range, formatted for finance and operations.
See it on its own →System-driven light and dark themes, plus layouts that adapt from phone to tablet to desktop.
See it on its own →What this product exists to fix.
Independent trainers run a real business out of a notes app and a payment link. The money that leaks is invisible: a card declines quietly, the client keeps training, and nobody notices for six weeks.
A pocket CFO — recurring revenue, session logging and, above all, failed-payment recovery surfaced as the first thing on the home screen with the amount at risk attached to it.
The implementation, at a level we can share.
- ✓Failed payments are a first-class screen, not a line in a settings menu
- ✓Cross-platform from one codebase (React Native / Expo) with a web build for the desktop view
- ✓Subscription state handled through RevenueCat so entitlements match on both stores
- ✓A read-only accountant role that can see every number and move none of it
A capability-level overview. Endpoints, credentials, internal architecture and client-specific code stay private.
The same architecture, other industries.
Don’t copy the app — copy the capability. Every workflow above can be rebuilt around your business, your data and your users.
We can build your version of it.
Everything in this demo is a capability we can adapt, redesign or rebuild for your company — on its own, or combined with others into a single product.
Other products you can use right now.
You don’t have to build GymCash.
We can adapt individual features, workflows, interfaces or the whole system to your business.