8 min read
App2025–26 — Product Designer & PM

GymGoer: Fitness is now accessible on Holiday

Role
Product designer & Product Manager
Team
Techne HQ — 1 UX designer, dev team
Timeline
Mar 2025 – Jan 2026
Platform
iOS app + operator web

Executive summary

60-second read
Problem
A traveller who wants four sessions in a city they don't live in has to sign a contract, pay a joining fee and complete a paper waiver at a front desk. Independent gyms sit empty off-peak with no digital shopfront to sell that capacity from.
Hypothesis
If casual access could be booked in one tap and verified at the door without training a single staff member, both sides of a market that already existed would finally meet.
Solution
A two-sided marketplace with one flow each: discover → book → check in for travellers, passive fill for gyms, and a unified waiver signed once instead of at every door.
What changed
29+ gyms onboarded and 650+ downloads by launch, on a product that carried a $4M+ valuation into its next round.

01 — Context

GymGoer was built inside Techne HQ's R&D arm for founder Ryan Clarke. I ran product design and product management on it — strategy, interface, and the sequencing calls — with one UX designer and the development team, from March 2025 to launch in January 2026.

02 — The problem

Two markets were failing each other. Getting four sessions in an unfamiliar city meant a contract, a joining fee and a waiver at a front desk, for a week of use. Meanwhile independent gyms had spare capacity every off-peak hour and no way to be discovered. Finding a casual-friendly gym still meant phone calls, manually checking hours, and negotiating a rate in person.

Fig 01Before state — the casual-access path as it actually ran: call, visit, sign, pay, repeat per gym.

03 — Constraints

  • Gym staff could not be trained. Anything that required a front-desk workflow change would break at the door, whatever the app did.
  • Two audiences, one build. Travellers wanted to book; operators wanted numbers. Both needed a coherent product, not one app with a mode switch.
  • Payment models and gym types would keep changing after launch, so the architecture had to absorb new ones without a redesign.

04 — What we learned

The guiding line came out of the early sessions: effortless access to the right gym at the right time. People didn't want more options, they wanted a clear path through the ones they had. And every failure I watched happened at the front desk rather than in the app — when the staff member hesitated on a check-in, the booking felt broken no matter how good the screens were.

Fig 02User check-in flow research to see how can payment be done in a win-win situation.

05 — The move

So the product collapsed to three steps. Every screen answers exactly one question, and the one-tap booking carries the waiver, the payment and the door code in one confirmation — so nothing is left for the front desk to interpret.

Fig 03Core interaction — three frames: the gym list, time and price selection, and the confirmed pass with its check-in code.

06 — What shipped

  1. AOne-tap booking: select gym, pick time, pay, done — onboarding cut to the four decisions that can't be removed.
  2. BPeer reviews written by casual visitors rather than aggregate stars: cleanliness, check-in ease, and whether the equipment was free — the things that decide whether you come back.
  3. CReferrals with no codes and no multi-step redemption, because a share that needs explaining doesn't get sent.
Fig 04Shipped UI — three tiles: the booking confirmation, the waiver, and the operator's capacity view.

07 — Tradeoffs

The operator side shipped thinner than the traveller side. Gyms got capacity and revenue numbers but not the scheduling depth two of them asked for. For a marketplace that needed supply before it needed features that was the right order, but it cost us both of those chains in the first cohort.

08 — What changed

29+
gyms onboarded across launch cities
650+
downloads in the first months
$4M+
valuation carried into the next round

09 — What I'd do next

Design the front desk, not just the app. The only thing that reliably broke the experience was a staff member who wasn't sure what a tap meant, and no amount of polish inside the product fixed that. On the next two-sided build the operator-side onboarding — a one-page card at the desk, an audible confirmation, a visible success state — gets designed before the consumer screens do.