About

Built by someone who's lived the scouting grind.

Founder photo
coming soon

Chris O'Connor, Founder

Before FalconEye was a product, it was a Sunday-night problem: hours spent re-watching film for one opponent's first move, notes scattered across a dozen files, and no good way to remember what a specialist did the last time you saw him. That gap is what FalconEye was built to close — not as a general sports-analytics platform retrofitted for lacrosse, but as a tool built from the inside, for the specific, narrow job of faceoff and draw-control scouting.

Every decision in the product — the move-distribution charts, the wing and circle diagrams, the exploit callouts — comes from actually sitting in that chair: staring at film, trying to turn tendencies into a plan a staff can execute by Friday. FalconEye is built for coaches first, because coaches are the ones who actually have to use it on a Tuesday night before conference play — not a generic sports-tech audience.

Why FalconEye exists

This wasn't a market I researched. It was a grind I lived.

I lived out of Hudl and a notebook.

Clips in one place, tendencies in my head, and a scouting doc that changed every week. Nothing connected — and for most staffs, it still doesn't.

I watched years of scouting knowledge disappear every spring.

A specialist we'd faced before, a tendency we'd already cracked — gone the moment the staffer who tracked it graduated.

I burned entire days hand-tagging film.

Clamps, exits, and counters, logged one clip at a time — time a conference-week staff doesn't have to spare.

FalconEye is the tool I wish existed back then. I built it for every staff still living that grind.

— Chris O'Connor, Founder