Built a basketball analytics SaaS as a solo founder. Here's what I learned.
I've spent the last year building a basketball analytics platform as a solo developer and finally started putting it in front of people.
The idea came from a simple observation: a lot of coaches and smaller clubs still spend hours after games pulling stats into spreadsheets, building reports manually and trying to turn numbers into something useful for the next game.
Top professional teams have analysts and expensive tools.
Most teams don't.
So I started building Statly - a platform that takes game data and turns it into structured scouting and coaching reports.
The reports include things like:
* Team comparisons * Four factors * Shot charts * Player impact breakdowns * Game flow visualisations * Custom time-range reports
One thing that surprised me while building this is that coaches don't really ask for more dashboards or more numbers.
They want answers quickly.
They want to know why they lost the rebounding battle, why the offence stalled in the third quarter or which lineups actually worked.
Building the product was difficult.
Getting it in front of the right people is proving to be even harder.
I'd genuinely love some feedback from coaches, analysts or anyone working in sports analytics:
* What do you actually look for after a game? * Which metrics matter most to you? * What do current tools do badly? * Would something like this fit into your workflow?
Happy to share screenshots or sample reports if anyone is interested.
Posted Jul 6, 2026, 8:54 PM UTC