Race effort
without a wrist screen.
Cross country is the most urgent side lane because the hardware fit is closer to the core HyperPulse product. The opportunity is not replacing Garmin or COROS for every runner. It is giving parents and coaches a rule-aware, no-GPS, no-athlete-facing way to review effort, cadence, surges, and consistency after a race or workout.
More immediate
than golf.
If we are ranking sidecar opportunities, cross country moves ahead of golf for 2026 testing. It uses the same youth-athlete buyer, the same parent-managed account model, the same no-GPS hardware story, and the season gives you a near-term reason to talk to local teams.
Why it fits
Distance runners already care about data, but high school meets can be rule-sensitive. A low-profile sensor that does not show the athlete live pace creates a clean conversation with coaches and parents.
What it cannot do
No GPS means no exact course map, exact mile split, or certified distance. HyperPulse should sell effort signatures and consistency, not pretend it is a GPS watch.
Fast pilot wedge
Test with local runners in workouts first: compare HyperPulse cadence and effort signals against watch data, then decide whether any meet-day use is worth rule review.
Allowed sometimes.
Never assume.
NFHS track and cross country rules have opened more room for electronic devices, but they still restrict electronically transmitted information from a coach or third party to a competitor during competition. Illinois-specific materials have previously allowed watches, but that does not equal blanket approval for every sensor at every meet.
Safe positioning
- Training and post-race review first.
- No GPS hardware inside HyperPulse.
- No display to athlete during the race.
- No coach-to-athlete live instructions.
- Meet director or official approval before competition use.
Do not say
- Do not say "NFHS approved."
- Do not say it is legal in every meet.
- Do not claim exact split timing without validation.
- Do not claim medical fatigue, hydration, heat illness, or injury detection.
- Do not market live coaching feedback for races.
What parents
could see.
Race effort profile
Segment a race or workout into effort blocks using acceleration, cadence stability, and barometric change. This is a pattern report, not a GPS trace.
Surge and fade
Count meaningful pace-change events, identify where stride consistency drops, and compare late-race output against early-race output.
Hill response
Use barometer plus movement signatures to flag climbs and descents. This must be validated course-by-course before marketing as a reliable metric.
Training load
Keep load as athletic-performance context, not medical fatigue. Pair with subjective coach notes rather than health claims.
Coach report
Export a shareable report that says what happened: consistency, effort distribution, and session comparison. No percentile claims until there is real data.
Founder dashboard
Because HyperPulse already relays through Supabase, a founder-only dashboard can show active devices globally once accounts, roles, and consent are built correctly.
What local kids
probably have.
If local runners already have something, the likely answer is not SPT first. It is Garmin, COROS, Apple Watch, Stryd, Polar, or a school/team training system. HyperPulse should not fight watches on exact pace. It should fight on parent-managed team visibility and rule-sensitive meet use.
Do not replace
the timer.
The "band around the chest" parents talk about is often a timing tag on the bib, not a sensor that streams workout data. School XC timers commonly use RFID bib tags, shoe tags, or active/passive transponders read by mats or antennas. HyperPulse should treat official timing as the source of truth and layer athlete movement context around it.
RFID timing
Vendors such as MYLAPS, IPICO, ShaZam Racing, and local timing companies use chips linked to bib numbers or shoe tags. They produce official finish times, split times, placements, and team scoring. HyperPulse should not try to duplicate that job.
Strava lane
Strava is useful after a workout or race if the family opts in. A HyperPulse export could eventually generate a FIT, TCX, or GPX-style activity file or receive activity-created webhooks. For middle schoolers, age and privacy rules matter: do not build this as automatic public sharing.
Best integration
Use bib number, athlete name, team, and official result URL to attach HyperPulse effort context to the race result: cadence stability, surge count, late-race fade, and hill response. That gives coaches more than the time without disputing the timer.
Layer onto results.
Do not fight them.
The smart play is not becoming a timing company. Timing crews already own official finish order, cameras, mats, bibs, shoe chips, meet software, and school trust. HyperPulse becomes the context layer around the official result.
Current HyperPulse hardware does not market heart-rate. Any heart-rate lane would require explicit external BLE sensor pairing, parent consent, and careful youth privacy handling.
Do this before
the season heats up.
Bench-test Feather: motion logging, battery, relay, and placement comfort.
Compare against one Garmin/COROS watch over a controlled interval session.
Ask one XC coach which report would actually change a workout plan.
If competition use is considered, get written meet-director approval first.