Case study · RunLink · 2025–2026

RunLink

MVP shipped on iOS + web; first B2B pilot in motion with a 45-store retail chain.

In development
RunLink hero

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 for solo organizers and 45-store retail chains to use the same product, just with different surfaces.

What we built

  • Club discovery and membership flow on iOS
  • Event scheduling + RSVP + day-of check-in
  • Marketing site for clubs to list themselves
  • B2B retail layer, branded club programs under the parent retailer
  • Open API for retail partners to bulk-sync their store locator

Stack

Frontend
Next.js 16React Native iOSTailwind
Backend
FastAPIPython 3.12
Data
Cloud SQL PostgresGeospatial indexing
Infra
Cloud RunVercelApple Push

What’s next

Close the first 45-store B2B pilot, ship Android, and bring on partner retailers as a self-serve onboarding path.

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