Built by a Commissioner
Coach Lefty is not a startup product. It is the tool I wished existed and still use every week running my own league.
The Origin
I have been playing Madden franchise mode for years. Not casually. I lab in practice mode, experiment with unique formations and schemes, and take my franchises seriously. When I started running my own league, I realized fast that the commissioner experience was a mess. Advances were manual, activity checks were a headache, trades were negotiated in DMs, and half your members never knew the schedule was posted until two days later.
The tools that existed were either too basic to matter or required someone with a computer science degree just to set up. What I actually wanted was a platform that met the league where it already lived, automated the repetitive stuff, and gave commissioners a real cockpit for the work that should not be buried in chat.
So I built it. What started as a personal project for my own league eventually became Coach Lefty.
Who I Am
I am a self-taught developer and engineer based in the Midwest, building Coach Lefty as a solo side project alongside a full-time day job. Every feature, every bug fix, every design decision comes from me. When something breaks at midnight before an advance, I am the one fixing it.
The reliability promise is plain: direct founder support, exportable league data, and a public roadmap that separates shipped work from what is still next. I would rather be transparent about the build than dress it up with fake proof.
I have been both a commissioner and a player in competitive leagues. I know what it is like to chase down inactive members, post standings manually after every week, and try to keep 32 different people engaged and accountable. Coach Lefty is built to solve those exact problems, not theoretically, but from real experience inside the same Discord servers you are running.
Why Discord Plus Web
Discord owns ordinary league work: alerts, posts, votes, confirmations, and the social moments members already expect in their server.
The web provides live-safe commissioner review where a browser handoff is necessary, and owns public product and legal information plus the handoffs Discord cannot safely complete, including OAuth, billing, EA connection, and bounded recovery. Discord remains primary for ordinary league work, while durable league state stays in the shared services behind both surfaces. The mobile companion is described only where current release evidence supports it.
Automation first
Repeated supported workflows should use reviewed automation with a durable completion receipt. Human decisions stay visible.
Built for real leagues
Every feature comes from a real problem I have seen in real franchise leagues. Not a hypothetical use case.
Data you can trust
EA-backed facts are labeled separately from declared or unavailable data. Missing evidence stays unknown instead of being filled in.
Always improving
A public roadmap separates source work, deployment proof, provider checks, and customer evidence so progress is not overstated.
Resources and Trust
Use the public sources below to inspect how the product works, how trust signals are computed, what remains unproven, and which legal controls apply.
Get in Touch
Questions, bugs, or billing support go directly to the founder. No public response-time promise is made yet.
Send Feedback
Feature request, bug report, or a quick review — goes straight to the developer.