One coach can now run a full roster from a single dashboard instead of one player at a time.

The situation

Golf data was everywhere and useful nowhere. Course directories, scoring apps and coaching notes each held a piece of the picture, and none of them told a player what to do differently on Saturday.

For coaches the problem was worse. Reviewing a player's rounds meant opening whatever app that player used, reading numbers, and writing feedback by hand. That is fine for one player. For a roster it does not scale, so most players got attention in rotation rather than when they needed it.

What we built

Two things that had to work together.

For players: a mobile app for logging a round as it happens, which returns specific feedback on the round rather than a scorecard summary — where strokes were lost, which decisions cost them, what to work on before the next one. A model fine-tuned on coaching material provides the language; a course knowledge graph provides the context about the hole they were actually standing on.

For coaches: a web dashboard showing every player at once, with progress over time and generated per-player summaries a coach edits before sending.

What we deliberately left out

No wearables or launch monitors in v1. Sensor integrations were the most requested idea and the least proven. We shipped with manual round entry, confirmed people actually logged rounds, and left hardware for a phase that had evidence behind it.

No social feed. It would have been fun to build and would have delayed the coaching product by weeks.

No autonomous coaching. Generated feedback goes to the player directly, but anything a coach sends is edited by that coach first. Coaches were not going to put their name on text they had not read.

The result

The platform shipped on web, iOS and Android in eight weeks against a fixed scope. Coaches moved from reviewing players in rotation to seeing the whole roster in one view, and players get feedback on a round the same day rather than at their next session.