CoAtch didn't start as an app.
It started with linked spreadsheets, scribbled notes in a backpack pocket, and two separate apps for stats and lineups.
I was a few years into coaching at my alma mater and the team was growing. The good parts were obvious: players improving, relationships forming, late nights talking soccer with the assistants at the field. But the background noise was everything it took to manage that flow. Rosters, attendance, practice plans, scouting notes, player evaluations.
I loved every minute of the coaching. I hated the disconnected systems.
As the scope of our program grew, we implemented new tools — video, RPE, even xG tracked by hand to guide practice plans. Attempts at tracking periodization and adapting it to the high school game spread across entire docs. We were stringing tools together to build what I thought elite teams must already have.
Then I built CoAtch.
Practices planned and shared instantly to any assistant on the app. Lineups saved as snapshots at different points in the season. Playing time and stats reports generated the moment Game Time ends.
The coaching stayed.
The system improved.
The disconnect stopped.
TeamSnap handles rosters. Tactics boards draw formations. Drill libraries give you sessions. None of them connect the dots between Sunday's game and Tuesday's practice.
So I built one thing: a single place where the roster, plans, lineups, and reflections live together. Not to replace coaching, but to stop the constant resetting of information.
CoAtch isn't a tactics board and it's not a team messaging app. It's the structure around a season. The part most of us try to hold together with paper, memory, and late-night discussions at the field.
I didn't build it to sell software. I built it because I realized I was trying to do what the pros do with none of the resources. I needed a system the same way my players needed training.
If you've been looking for a system that connects your whole season, this is it.
