2
3 Comments

Stealing Timeleft's playbook (but for runs, in Tokyo, at 1/3 the price)

Quick gut-check before I commit to building.

The premise
Every Wednesday night, an algorithm matches you with 4 strangers in
Tokyo for a 30-min group run. Fresh 4 every week — no fixed group,
no regulars. Pace + language (JP/EN/both) + preferred course matching.

Why I think it works

  • Timeleft hit €18M ARR with the dinner version of this exact pattern
    (4 strangers, weekly, algorithmic)
  • Tokyo has 740k foreign residents, many of whom can't break into
    the established run clubs (Midnight Runners, Namban, etc.)
  • Running is cheaper to operate than dinners — no restaurant ops,
    no reservation friction, no minimum bills
  • Phase 1 free → Phase 2 ¥500-1,000/mo. Lower friction than
    Timeleft's $20/mo, betting on volume + retention

Where I'm uncertain (want your gut)

  1. Is "run instead of dinner" enough wedge to justify a separate brand?
    Or should I be terrified that Timeleft adds a "Runs" tab and steamrolls me?

  2. Pricing: ¥500-1,000/mo feels right for Tokyo, but am I leaving
    money on the table? Timeleft proves people pay $20 for this
    experience format.

  3. The "graduation problem": people meet 1-2 good run buddies,
    start running with them privately, churn from the app. LTV target
    is 4 runs (~¥2-4k). Is there a retention mechanic I'm missing?

Status

  • LP live: pacr.city (JP/EN bilingual)
  • 30-day pre-launch waitlist test, gate at 100 signups
  • 4-week manual operations phase before any native build
  • Native build only triggers if both gates pass

Will report the raw numbers back in 30 days regardless of outcome.

Brutal feedback welcome — especially if you think I'm wrong about any
of it.

posted to Icon for group Ideas and Validation
Ideas and Validation
on May 16, 2026
  1. 2

    The wedge is stronger than “Timeleft for runs” if you frame it around social fitness, not just running. The real pain in Tokyo is probably not lack of run clubs, it is that existing groups feel fixed, intimidating, already-networked, or hard to enter as a foreigner/newcomer.

    I’d be careful with the “fresh 4 every week” rule though. For dinner, novelty is the product. For running, trust and comfort may matter more because people are meeting outdoors, moving together, matching pace, and possibly dealing with language/culture friction. A better retention loop might be “fresh matches plus lightweight continuity,” where people can re-run with someone once but still keep discovery alive.

    Name-wise, Pacr.city is clear for pace/city, but it feels very local and functional. If this becomes broader social wellness or city-based active connection, Lyriso .com would carry the softer community/wellness side better than a name tied mainly to pacing.

    1. 1

      Thank you so much for the incredible feedback!

      I love your note on the retention loop. You're completely right that running requires more trust and comfort than a dinner. Moving towards a "fresh matches + lightweight continuity" model makes total sense to ease that friction.

      For the naming, your perspective on scalability convinced me. Lyriso.com definitely carries that softer, broader wellness vibe better than Pacr.city as we grow.

      This was extremely valuable. Thanks for sharpening my vision!

      1. 1

        Glad it helped.

        Honestly, if Lyriso.com already feels closer to the direction you want to grow into, I’d think about this before Pacr.city gets more users attached to it.

        Pacr.city works for the current running wedge, but it keeps the brand tied to pace and city. That is fine for validation, but if the real product becomes social wellness, active connection, trust, and lightweight community, the name may start feeling too narrow very quickly.

        The tricky part is that naming is cheapest to fix before people start inviting friends, joining runs, and remembering the brand publicly. Once that happens, even a better name becomes harder to move into.

        That is why I’d seriously consider securing Lyriso.com now if this is the direction you want long term.

        I have access to it and can keep it founder-friendly if you want to make it simple.

        Happy to discuss privately here:

        https://www.linkedin.com/in/aryan-y-0163b0278/

Trending on Indie Hackers
7 years in agency, 200+ B2B campaigns, now building Outbound Glow User Avatar 105 comments How I built an AI workflow with preview, approval, and monitoring User Avatar 60 comments The "Book a Demo" Button Was Killing My Pipeline. Here's What I Replaced It With. User Avatar 46 comments I built a desktop app to move files between cloud providers without subscriptions or CLI User Avatar 27 comments Show IH: I built an AI agent that helps founders find the right people User Avatar 24 comments After 4 landing page rewrites, I finally figured out why my analytics SaaS wasn't converting User Avatar 20 comments