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)
-
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? -
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. -
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.
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.
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!
Yukin, one practical thought.
Since the full domain decision may be too early while you are still validating Pacr.city, I can help in a lighter way.
I do focused naming and positioning audits for early products: current name risk, category framing, domain perception, whether the brand can scale, and what stronger direction I’d take before more users, invites, social posts, and community memory build around the current name.
For Pacr.city, I’d specifically look at whether the product should stay framed as running matches or move toward social wellness, active connection, trust, and lightweight community.
It is not a long consulting thing. Just a sharp written breakdown with practical recommendations.
I’m doing a few of these at $99 while refining the format. If useful, I can do one for Pacr.city and give you a clear outside read before you build more around the current direction.
Yukin, one quick follow-up on the naming side.
The reason I brought up Lyriso seriously is because you already seem to be thinking beyond “running matches” and toward something softer: active connection, social wellness, trust, and lightweight community.
That is exactly where Pacr.city may become harder to carry over time.
It works for the current wedge, but every run, invite, post, and early user who remembers Pacr makes the eventual switch harder if Lyriso is the direction you actually prefer long term.
So I would not leave this as a vague “maybe later” naming decision.
If you want to keep validating under Pacr.city for now, that is understandable. But if Lyriso feels like the stronger long-term identity, it is probably worth discussing before more public usage builds around the current name.
Happy to keep it simple and founder-friendly if you want to look at securing it privately:
https://www.linkedin.com/in/aryan-y-0163b0278/
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/
Hi Yukin, curious to hear from your experience in detail! Let us know :)