
We build GoodCoach because the software around sport never matched how much the people in it care
A coach with fifty athletes should know each of them better than they would tracking one athlete anywhere else. That is the bar we set for ourselves
Kaiden was a distance runner at the University of Saskatchewan, at practice every day. The coaches were great and stretched thin: thirty, forty, fifty athletes each, with workouts in spreadsheets, feedback buried in group chats and training history gone the moment someone switched programs.
Coaches had been stuck choosing between knowing one athlete really well and managing a whole team. Kaiden thought that was fixable: build for the whole team, and make what a coach knows about each athlete better because everyone feeds the same system, not in spite of it.
A coach sends a session, every athlete does it on their own time and tells the coach how it went, and the next session is better for it. Parents stay connected. Clubs and colleges run every team without it collapsing into a spreadsheet.
Coaches, athletes, parents, clubs and colleges, each with their own view of the same team. There is a lot left to build, and every piece of it comes from someone who coaches or trains telling us what was missing.
Both distance runners at the University of Saskatchewan, and both still training

In the middle of the Canadian prairies, where −40° winters leave a lot of time for writing code. Our office is at Co.Labs, Innovation Place