Pre / The runner behind the numbers
A first kilometre.
A fine margin.
Different levels of detail. The same respect for the runner.
Invented sample data · calculated observations · authored Pre interpretation. No connected Nike or Strava account. This demonstrates a review workflow, not professional coaching validation.
Novice / finding a steady rhythm
You covered the ground. Let’s look at how the run unfolded—not turn it into a verdict on you.
| Segment | Time | Versus mean |
|---|---|---|
| 1 | 6:30 | -10 sec |
| 2 | 6:40 | +0 sec |
| 3 | 6:50 | +10 sec |
| 4 | 6:45 | +5 sec |
| 5 | 6:35 | -5 sec |
What the numbers say.
What we still need to know.
Your splits range by 20 seconds. You slowed through kilometre three, then picked up again. That’s an observation—not proof of poor fitness or a failed run.
If this was meant to be easy, how did it feel? Could you keep a comfortable conversation going? What changed around the third kilometre: the route, your breathing, or your attention?
Fictional flat route. No heart rate, effort rating, weather or prior training supplied. Elapsed running time from the five supplied kilometre splits.
Your runs / account connection
Your training has a story.
Let’s make it personal.
We want Pre to discuss your own runs, with your permission: pacing, consistency, effort and what you’re working towards. A Strava connection to this demo is not available yet. The examples above use fictional data.
Can I connect my personal Strava account?
Strava offers subscribers an official, read-only MCP connector, currently documented for Claude. You authorise access to your own account and can revoke it. That personal route is separate from this Pre demo.
Calling the data “personal” does not authorise our commercial website to use it. A Pre integration requires appropriate permission from Strava; we won’t ask you to share a password, token or export as a workaround.
Strava’s personal connection instructions ↗ · Strava API policy, sections 3.5 and 5.3 ↗