Case study · RunLink · 2025–2026

RunLink

MVP live on iOS via TestFlight and on the web, with a B2B retail track warming behind it.

In development
RunLink hero
Fig. 01 · RunLink

Role

Studio · build + ship

Status

In development

Year

2025 → 2026

Surfaces

Web + iOS

Live

In development

The problem

RunLink is a platform built to fill the gap between messy group chats and overpriced enterprise tools for running clubs. Members register and pay through the app, club admins schedule events and track turnout, and retail brands run their own branded club programs on the same rails. Designed so a solo organizer and a multi-store retail chain use the same product, just with different surfaces.

What we built

  • Club discovery and membership flow on iOS
  • Event scheduling with recurring events, RSVP, and day-of check-in
  • In-app route maps with auto-calculated distance
  • Direct messaging between members
  • Role-based experience, distinct runner and club-admin surfaces
  • Marketing site plus an admin, club, and runner dashboard
  • Open API for retail partners to bulk-sync their store locator

Stack

Frontend
Next.js 16SwiftUI iOS 16+Tailwind
Backend
FastAPIPython 3.11
Data
Cloud SQL PostgresRedisGeospatial indexing
Infra
Cloud RunVercelMapboxApple Push

What’s next

Merge the role-based redesign, launch on the App Store, ship Android, and open a self-serve onboarding path for partner retailers.

Have something that looks like this?

Tell us what is broken. We’ll tell you what the first week looks like.

Next case study →

Smile PreVue