Set the week
Tell Runthread your goal and your available days. It builds a week with structure where it matters and slack where it doesn't.
Goal, days, key sessionsPrivate beta · Strava-first
Training that holds together.
Most plans assume a perfect week. Runthread assumes a real one — it imports the runs you actually did, matches them to the plan, and makes one small, explained change instead of handing you guilt.
Early access is invite-only while the plan, import, match, and adapt loop is tested with real runners.
Runthread Adaptive week
Plan ready
Mon Rest
Mobility
Tue Intervals
6 x 3 min
Wed Easy
7 km
Thu Rest
Optional
Fri Tempo
24 min
Sat Easy
5 km
Sun Long
13.5 km
Plan Build a week you can actually run.
Runthread starts with available days, useful training balance, and the next race or goal.
Every run you do is a stitch. Runthread keeps them on one thread.
How it works
One loop, from plan to adapted plan.
Just run
Head out like you always do. Your watch and Strava already record everything Runthread needs — there's nothing to log twice.
No manual loggingIt flows back in
The activity is imported and matched to the session it probably was, with the confidence behind the match shown to you.
Date · distance · durationOne small change, explained
If the week needs to shift, one session is adjusted and you're told exactly why. No resets. No guilt. No noise.
Calm adaptationFeature showcase
Built for the moments where plans usually break.
The first version is deliberately focused: make the adaptive loop genuinely useful before adding dashboards, badges, or noise.
Adaptive plans
A week built for your real life.
Runthread plans around the sessions that move you forward, then flexes the rest when work, weather, or tired legs interfere.
Strava import
Your runs flow in on their own.
Connect Strava once. Completed activities are imported automatically, so the plan responds to what actually happened — not what you remembered to log.
Workout matching
It knows which workout that was.
Date, distance, duration, and activity type link each run to its planned session — with the match confidence in plain sight, never hidden.
Calm adaptation
Changes are small, and always explained.
No dramatic resets. When the plan shifts, you see exactly what changed, why it changed, and what to do next.
Beta privacy
Only what the loop needs.
The first beta collects an email, Strava activity basics, and your feedback on plan changes. Nothing more.
Training timeline
The week is visible, not buried.
What's planned, what came back from Strava, and what changed — the whole training story stays on one screen, in order, in plain words.
Import panel
Morning run
- Distance
- 6.8 km
- Duration
- 42 min
- Source
- Strava
Match confidence
High confidence
Matched to Wednesday's easy run by date, duration, and effort range.
Adaptation note
Long run adjusted
Sunday reduced by 1.5 km after a partial completion earlier in the week. Friday stays exactly as planned.
Founder note
Built for runners who want less mystery.
Runthread exists because training plans tend to break the moment life shows up. The beta is about earning trust in one small loop: build a useful week, import completed runs, match them correctly, and explain every change. If that loop isn't right, nothing else matters yet.
Beta posture Focused, not maximalist.
Email capture uses Loops. Activity import is scoped to the training data needed to validate matching and adaptation before wider access.
Read the privacy placeholderFAQ
Straight answers before the beta opens.
How do I get beta access?
Join the waitlist and beta invites will be sent in small batches as the core training loop becomes ready to test.
Do I need Strava?
The first beta is designed around Strava-backed activity import, so Strava will be the preferred way to test matching and adaptation.
What data will Runthread import?
The beta focuses on activity details needed to match completed runs to planned workouts, such as date, distance, duration, and activity type.
Will there be pricing?
Pricing is not set yet. The first goal is validating whether the plan, import, match, and adapt loop is useful.
Which platforms will be supported?
The mobile app is the main product surface. The landing page is static and only handles beta signup for now.
How often will invites go out?
Invites will be gradual so feedback can be handled properly and plan changes can be checked before widening access.
Beta access
Pick up the thread.
First invites go to runners who are happy to test adaptive plan changes and say what felt right — and what didn't.