Case Study
DEXA and the 7-Pound Gap
A 47-year-old strength-trained runner uploaded his DEXA scan into Ask Coach. What came back was a synthesis no template plan could produce — and a reconciliation of three data sources he had been treating as contradictory.
The setup
The athlete is a 47-year-old man training for a 20-mile race. He deadlifts in the 300s, squats in the 270s, benches 225 for 11s. He runs consistently, logs everything in StrideIQ, and syncs his Garmin scale daily. He had recently spent the money on a DEXA scan — the gold standard for body composition.
He had a problem. His Garmin scale said 188 lbs. His DEXA said 195 lbs. Same body, same week. He uploaded the DEXA report into Ask Coach and asked what it meant.
What the coach said
The DEXA showed a T-score of +3.2 — bone density in the top 1% of the population. The coach connected this directly to his lift history (years of heavy compound work) and explained the implication for his 188-vs-195 reading:
“Garmin's algorithm assumes you have a standard skeleton. It literally cannot see the extra 7 lbs of mineral density you have packed into your bones. You are not fat at 195 lbs; you are just physically more solid.”
The coach went further than the reconciliation. It carried the finding forward into how he should fuel for his upcoming race:
“Trust the 195-lb fueling. Your engine and chassis require more energy than a standard 188-lb runner.”
And it told him what to ignore on race day:
“If you feel heavy on the hills, remind yourself: it is not dead weight; it is armor and horsepower.”
Why this matters
This exchange traces a chain that almost no other product in the running space can complete:
- External data ingest: The coach read a DEXA scan PDF — a data source most coaching apps cannot accept and most coaches do not have access to.
- Multi-source reconciliation: DEXA, Garmin scale, lift logs, and run history were treated as one body of evidence rather than four disconnected feeds.
- Causal explanation: The +3.2 T-score was not just reported. It was traced backward to its likely cause (years of heavy lifting) and forward to its operational implications (fueling, race-day mental reframe).
- Cited and specific: Every claim referenced the actual numbers — the deadlift weights, the bench reps, the 20-miler in his calendar. Nothing was generic.
The point
Most training products treat body composition, strength, and running as three separate worlds. They have to, because they only see one of those worlds at a time. StrideIQ does not have that constraint — it ingests whatever the athlete brings and synthesizes across sources.
This is what “evidence-based coaching that learns from your data” looks like in practice. Not a template plan with personalization theater on top. A coach that read the actual file, did the actual math, and reframed three numbers into a single story the athlete could use.