PlayerPulse

Why they called us

A performance score built on years of research and millions of data points is worth nothing if a coach can't read it standing on the side of a pitch, in the rain, in the thirty seconds before the players come back on. The research existed. The thing that turned it into a number someone acts on did not.

What we built

Two apps and everything under them: one for the athletes generating the data, one for the staff reading it, and the backend and infrastructure that turn raw input into a score fast enough to matter that same day.

The hard part

The model keeps changing and the history does not. Every time the methodology improves, three years of scores have to still mean something, otherwise a coach comparing this month to last month is comparing two different scales without knowing it. Versioning the model and the data separately is the part that took the longest to get right, and it is the reason we are still on this after three years.

What had to be solved

• Turning a research methodology into a number a non-technical person trusts at a glance
• Keeping three years of historical scores comparable while the model behind them evolves
• Data arriving from the field with gaps, duplicates and clocks that disagree
• Two apps, two audiences, one source of truth underneath