Context before conclusions.
Pace means something different on heat, hills, mud and tired legs. 2537m keeps those differences visible.
TRAIL + ULTRA TRAINING INTELLIGENCE
Run the terrain.
Run the terrain.
Train the runner.
Support for runners who manage their own training. Bring your completed runs, your experience and your race preparation together, so you can make informed decisions from today’s session to race day.
Runner-controlled connections
Evidence-led guidance
Built for trail and ultra
MEET THE FOUNDER
Rob Lee
Founder & Running Coach
Trail and ultrarunning · Focused on the 100 km distance
A longtime fitness enthusiast, Rob embraced ultrarunning in his late forties. Today, his running centres on the 100 kilometre distance, and his experience as a runner and coach informs the development of 2537m. He built the app to help independent runners understand their training, prepare for race day and make informed decisions.
Evidence before advice.
Repeated, comparable runs matter more than a single number. Missing evidence stays missing. Download your training history as a CSV, including recorded debrief, fueling, hydration and weather details.
The runner stays in control.
Connections are optional, recommendations are explainable and health data is never used for advertising.
THE PRODUCT
What your run
What your run
means next.
2537m connects what the watch records with what only the runner knows, so tomorrow’s decision reflects the full training story.
Every run teaches the next.
Bring completed training, terrain, recovery and body signals into the next decision.
Turn the finish into feedback.
Review pace and effort alongside finish reserve, fueling, GI response and how your body felt.
Fuel from what you have proven.
Record carbohydrate and fluid intake, then use tolerated practice to inform the next long run.
Build. Taper. Arrive ready.
See the work ahead through race week, with future sessions adapting while completed runs stay intact.
App previews from the current private-testing build. Select an image to view it full size.
FROM TRAINING TO RACE DAY
Your course.
Your course.
Your race plan.
Bring the route and the evidence from your long runs together. Work through the race one leg at a time, then export a spreadsheet to organize supplies and share the plan with your crew.
Drop in the course. Build the race.
Import a GPX to see the route’s distance, ascent and named checkpoints. Add missing stops by distance from the start while keeping the original route intact.
Fuel the race from your practice.
Build personal ranges from relevant long runs and tolerated intake. When the evidence is missing, the app tells you what still needs practising.
Know every leg before the start.
Review distance, climb, effort, fuel and fluid in course order. Export a planning CSV with space for your products, crew details and notes.
Race timing is an experimental estimate. Fuel and fluid guidance depend on your recorded practice and available evidence.
PUT YOUR PLAN TO WORK
From course file
From course file
to crew plan.
Import a GPX route or checkpoint CSV, or build a checkpoint list for a race without a course file. Review each leg and export a spreadsheet to organize supplies, crew instructions and notes.
CSV and manual plans do not create a GPS track. Terrain-based estimates require the relevant elevation data. Confirm checkpoint facilities and crew access with the current race guide.
See what lies ahead.
Review distance, ascent and the aid-station waypoints found in your GPX file. Confirm facilities, crew access and cutoffs with the race guide.
Bring the details together.
Review the next checkpoint, terrain, estimated time and effort alongside fuel and fluid planning figures, all in course order.
Screenshots: a Canyons planning example using a 2025 alternate-course GPX for a 2027 goal. Figures illustrate one runner’s plan; timing is estimated and intake is individual. The Grindstone worksheet below is a separate example.
INSIDE THE APP
From the course to each leg.
See how a course is organized into legs in 2537m, with the route and segment strategy in one place. The worksheet below illustrates the practical details you can organize for race day.
Example shown: Grindstone, using a 2025 course file for a 2026 goal. Confirm current route and aid-station details with the organizer. Independent runner example.
EXAMPLE ULTRA RACE PLAN
Download example CSV
A plan you can share.
Preview three legs from a working race spreadsheet, with all ten legs in the download. It includes timing, effort, elevation (m), carbs (g), fluid (L) and sodium (mg). Use the structure to organize your own race preparation.
ONE LEG FROM THE WORKSHEET
Wolf Ridge to Sand Spring
- Distance
- 15.5 km
- Elevation to next
- 695 m
- Carbs to next
- 170 g
- Fluid to next
- 1.75 L
- Sodium to next
- 1,800 mg
Scroll sideways to see all columns.
| From | To next | Leg time | Planned arrival | HR to next |
|---|---|---|---|---|
| Start | 9.2 km | 0:58 | 6:00 | 135–140 |
| Lick Run 1 | 9.4 km | 1:10 | 6:58 | 135–140 |
| Wolf Ridge | 15.5 km | 1:55 | 8:08 | 138–142 |
Source: a personal Grindstone worksheet, prepared separately from the app export. Figures are individual planning targets, not race results or recommendations for another runner. The walkthrough and worksheet show different planning figures.
HOW 2537m THINKS
Advice with reasons
Advice with reasons
behind it.
Defined calculations and evidence rules measure your training and look for trends across comparable runs. AI helps interpret that evidence and explain what it might mean, within the app’s planning limits. When there isn’t enough information to draw a conclusion, the app says so.
If 2537m tells you something is improving, you should be able to see what that conclusion is based on. Your experience remains part of the decision.
What was actually recorded
Activities, heart rate, sleep, HRV, elevation, weather and runner-entered feedback retain their source and timestamp.
What 2537m calculates
Rolling load, durability, comparable-run trends and readiness components are labelled as estimates with confidence.
What may change next
Plan adaptations explain the evidence used, respect ceilings and never treat a missed session as training debt.
FOR DEVICE & DATA PARTNERS
Clear purpose.
Clear purpose.
Limited access.
2537m requests only the runner-authorized data needed to understand training, recovery and progress. Connections are read-oriented and can be revoked by the runner.
Running activities
Completed workouts, duration, distance, route, elevation, heart rate, cadence, laps and available environmental context.
Used for the training record, rolling volume, load context and comparable-run analysis.Recovery context
Sleep, resting heart rate, HRV, daily activity and basic profile information when the source makes them available.
Used as supporting trends—not diagnosis, treatment or a definitive readiness verdict.Training continuity
Historical and newly available activities synchronized after the runner connects an account.
Used to avoid starting from zero and to preserve an existing training plan wherever practical.
EXPLICIT BOUNDARIES
What 2537m does not do.
- Does not sell connected health or activity data
- Does not use health data for advertising
- Does not present estimates as medical measurements
- Does not diagnose, treat or replace professional care
- Does not hide missing or low-confidence evidence
- Does not request watch-account passwords
PRIVACY BY DESIGN
The runner owns the connection.
Account authorization uses provider-approved OAuth flows. Tokens stay on the server, access is limited to the approved scopes, and imported records retain source provenance. A runner can disconnect a provider and remove 2537m’s access.
OAuthProvider authorization
Read-orientedLeast necessary access
RevocableRunner controlled
TraceableSource provenance
Build the runner who finishes with pride.
2537m is in private testing on iPhone and Android. The screens shown here are from the iPhone build; public store availability has not yet opened.