Community-leader journey
Mapped how leaders announce runs, track members, collect money, and answer repeated questions before and after events.
An all-in-one platform for running community leaders. Publish your club, run events, manage memberships, and take payments, while runners find sessions matched to their pace.
Project frame: Runite: one platform for running clubs to grow, run events, and get paid
A leader hub and runner experience share the same product model without crowding each other.
Ticketing, memberships, and platform fees are built into the product from day one.
Running clubs are some of the most engaged communities there are, and some of the worst served by software. Leaders were stitching one together from a group chat, a spreadsheet of members, and a bank transfer for fees. There was no simple way to publish a club, run ticketed events, match runners to the right session, or get paid.
Mapped how leaders announce runs, track members, collect money, and answer repeated questions before and after events.
Runners needed difficulty, pace, route, timing, and social context before committing to a session.
Difficulty labels were grounded in real running paces instead of vague organiser guesses.
Subscriptions and event fees had to support club growth without creating payment admin for volunteers.
Running clubs are high-trust, high-frequency communities, and badly served by the tools their leaders actually use. The job ran on a group chat for announcements, a spreadsheet for members, and a bank transfer for fees. Runite's bet was that publishing a club, running events, and getting paid are one problem rather than three, and that solving it well could make a leader's whole week lighter.
Leaders and runners want very different things, so Runite is built as two focused apps over a shared API: an Owner Hub where leaders create communities, schedule events, and manage billing, and a runner app where people discover clubs, book events, and pay. Splitting them keeps each surface focused, so neither audience wades through the other's controls.
The sharpest design problem was ability. Show every event to everyone and beginners get scared off while fast runners get bored. So every event carries a difficulty (beginner, progressing, intermediate, advanced) and Runite infers it from real paces (5k through marathon) rather than asking an organiser to guess. A colour-coded badge lets a runner self-select a session that fits in a single glance.
Money was a first-class concern. Runite runs on Stripe Connect, so leaders are paid directly for tickets and memberships while the platform takes a small, configurable fee, with Club and Club Pro subscription tiers for owners on top. It all ships from one lean Vite/React/Chakra monorepo on Firebase and Render: runner app, owner portal, and API in a single codebase a small team can move fast in.
Runite turns a pile of disconnected tools into one platform a running community can actually run on, with discovery, events, memberships, and payments in a single loop.
Runite reduces the operational load on club leaders while giving runners a clearer, safer way to find sessions that match their pace and intent.