Built by a runner, for runners.
RunSignal exists because one question kept going unanswered: not what happened in a race, but why.
About RunSignal
RunSignal started as a much smaller idea.
Originally, it was simply a personal project designed to collect and organize health and fitness data from different sources. The goal wasn’t to build a business or launch a platform—it was to solve a problem.
Then running re-entered the picture.
After years away from the sport, running re-entered the picture in 2024. Like many runners returning to training, the data was everywhere: GPS tracks, heart rate graphs, cadence charts, training load metrics, recovery scores, race predictions, and more.
The information was everywhere. What wasn’t available was a good answer to a simple question:
Why?
Why did one race go well while another didn’t? Why did a training run feel effortless one week and difficult the next? Why did fitness improve during one training block but stall during another?
The turning point came while preparing for and analyzing the Edinburgh Half Marathon. Every platform could tell you what happened. None could truly help explain why it happened.
So RunSignal evolved.
Today, RunSignal is being built as an intelligence platform for runners. It combines training history, race performance, readiness trends, recovery data, environmental factors, and historical context to uncover patterns hidden in plain sight.
Instead of focusing on more charts and more numbers, RunSignal focuses on context, correlation, and actionable insight.
The long-term vision is simple: help runners better understand their training, their performance, and themselves—whether you’re preparing for your first 5K, chasing a personal best, training for a marathon, or helping lead a local run club.
Because every run tells a story. RunSignal helps you find it.
Meet the Founder
Scott — Founder, RunSignal
Hi, I’m Scott.
I’m a husband to Pam, a father, a grandfather, a dog owner, and a lifelong technology enthusiast who somehow found his way back to running.
Like many runners, I spent years away from the sport. Not because I stopped loving it, but because life got busy. Careers, family responsibilities, and everything else that comes with adulthood gradually pushed running into the background.
In 2024, I decided it was time to come back.
What started as a few miles here and there quickly turned into a renewed passion. Training runs became race registrations. Race registrations became goals. Before long, I found myself chasing personal bests, exploring new places through running, and preparing for races I never imagined I’d be running again.
Along the way, I became fascinated by the story hidden inside the data.
Every run generated information—pace, heart rate, cadence, elevation, weather, recovery, race results—but the numbers alone couldn’t answer the questions that mattered most.
I wasn’t looking for more data. I was looking for understanding.
I’m not a professional coach, elite runner, or venture-backed founder. I’m a runner who loves understanding how things work. For most of my career, that curiosity was focused on technology. When I fell back in love with running, I started applying the same mindset to training, performance, recovery, and race execution.
That’s where RunSignal began. Built during early mornings before work, evenings after family time, and the quiet hours between training runs.
Today, I still wear every hat: developer, tester, product manager, infrastructure engineer, support desk, documentation writer, and occasionally janitor.
More importantly, I’m still the first user. Every feature starts with a simple question:
Would this help me become a better runner?
If the answer is yes, it gets built.