The Long Way to the Sideline.

I never set out to build software. I set out to coach my kid's soccer team. This is the honest story of how that turned into five apps, built at 5 AM around a full-time job, a family, and a club that needed better tools.

I never set out to build software.

I set out to coach my kid's soccer team.

That's the truth of it, and I think it matters, because every founder story you read makes it sound like the person sat down one day, identified a market opportunity, and went to work. That's not what happened here. What happened is I got handed a clipboard and a roster of nine-year-olds and discovered that nobody — not the club, not the league, not the internet — had figured out how to make this easier for the volunteer standing on the sideline at 5:45 PM on a Tuesday with thirty minutes until practice and no plan.

So I duct-taped it together. Spreadsheets for lineups. Bookmarked YouTube videos for drills. A Notes app full of substitution patterns I'd half-remember between water breaks. A group text with other coaches asking what are you running tonight, I've got nothing. Every single coach I knew was doing the same thing. Every single one.

Then I became a commissioner at DSYSA. A thousand-plus players. Hundreds of families. I got a five-minute handoff call from the previous commissioner and an hour of training on LeagueApps and GotSport, and then the season started. That's not a complaint — the people who came before me did exactly what was reasonable for a volunteer board to do, and the tools they handed me worked. But sitting in that chair I started to see, from the inside, how much of the job was held together by individual people remembering things in their heads. Institutional memory living in one person's inbox. The next commissioner inheriting a shared Drive folder and a wish of good luck. Good people doing thankless administrative work that should have taken a tenth of the time, while the actual mission — kids playing soccer — got squeezed into whatever was left.

I built PlayOS because I couldn't not build it.

Five apps, one at a time.

It started as one app. Coach. A drill library, a session planner, something I could actually open on the sideline. Then it became two — because the lineup-and-substitutions problem on game day was its own beast, and Game was born.

Then Ops, because the commissioner work was consuming my free time. Rosters that had to balance team strength while honoring every parent request. Schedules that were complex puzzles — seventeen teams, four fields, three blackout weekends. Coach support. Parent emails. Pre-game scrambling to make sure the fields were lined and the refs were assigned. All of it on top of actually trying to grow and elevate the program, which was the part I'd signed up for in the first place.

Then Tournament, because I'd heard the stories from the prior season's end-of-season event. Bracket mistakes. Disorganization. Upset parents. The kids — who'd worked for months toward that weekend — deserved better than that, and so did the volunteers running it. The same puzzle Ops was solving for a regular season, Tournament had to solve compressed into 48 hours with families traveling in from out of town.

Then Player, because somewhere along the way I realized the kid in the middle of all this — the actual nine-year-old — was the one person without a tool. Their soccer story was being told in their parents' camera rolls and nowhere else.

Five apps. One ecosystem. Built early mornings and weekends around a full-time job, around a once-a-week coaching practice, around a calendar of kids' activities that filled almost every other night of the week, around commissioner duties, around being a husband and a dad. Most of the work happened at 5 AM — coffee, quiet house, two or three hours before the day actually started.

None of this happens without my wife, who watched me disappear into this project for months and never once asked me to stop — who understood, before I could even explain it, that I was building something I needed to get into the hands of the youth soccer community. I'm not sure I deserve that kind of patience, but I'm grateful for it every day. The rest of it — the early mornings, the weekends, the obsession — that part was on me. Because the alternative was leaving the next coach, the next commissioner, the next family to duct-tape it together the way I had.

The hardest part wasn't the code.

The hardest part was the discipline.

Every solo founder will tell you the temptation is to keep building forever — to never ship because shipping means being judged, and being judged means being wrong about something. I had a planned launch date of May 25, 2026. The forcing function. The deadline I'd told myself for months.

I shipped on May 18 instead. Seven days early. Not because the apps were perfect — they're never perfect — but because by the morning of May 17 I looked at what was in front of me and realized I was proud of it. The five apps were live in production. The Stripe integration was clean. The audits were done. The drill library was at 357 drills, fully migrated to v2. The marketing surface was instrumented. The legal docs were published. The DNS was green across the board on every email-deliverability test.

Shipping when you're proud, not when you're scheduled — that's a lesson I had to learn the hard way. — Every instinct in me wanted to wait one more week.

The wall of decisions behind it.

What people don't see, when they look at a launched product, is the wall of decisions behind it.

The decision to position PlayOS as an organizer of discovered content, not a recreator — because the world doesn't need another mediocre drill diagram generator, it needs a coach to find the right drill faster.

The decision to make Player the long-term value multiplier — a 10-year story arc that follows a kid through their development — instead of a club-side feature buried inside a B2B tier.

The decision to charge for a credit card up front on the trial, even though every growth playbook says don't, because the families and clubs I serve don't have time to be tricked into a subscription they didn't mean to buy. Honest UX over conversion-optimized UX. Every time.

The decision to not call it SaaS in any customer-facing language — to say "the operating system for youth soccer," because the people I'm trying to reach are volunteer coaches and parents, and the moment you sound like a B2B sales deck, you've lost them.

The decision to provision Player Family accounts for the Wolfpack — my own U10 team — with personalized handout emails sent to each family. My team. My kids. My responsibility to get it right for them first.

Underneath the product.

Underneath the product is the part I'm most proud of, even though no customer will ever see it: the architecture.

Five apps. Pure vanilla JavaScript. No CDN. No framework du jour. No build-tooling treadmill that'll be obsolete in two years. Single HTML files that load in under a second on a parent's phone in a parking lot with two bars of signal. A subscription system that survives cancel-and-resubscribe within 90 days because families' lives are complicated and the software shouldn't punish them for it. An AI layer that costs fractions of a cent per query because I refused to build something that couldn't sustain itself economically.

It's boring technology. It's deliberately boring technology. Because every hour I'd have spent maintaining a fashionable stack is an hour I didn't spend talking to a commissioner in Austin or a coach in New Jersey or a tournament director in Virginia about what they actually need.

And now the work changes.

The launch wasn't the finish line. It was the starting whistle. The next stretch is about finding the right clubs to go deep with — not broadcast marketing, not spray-and-pray cold outreach, but real relationships with the people running real programs, who can tell me what's actually broken and what's actually working.

I am one person. I have a full-time job. I have a family and a life that exists outside the laptop. PlayOS will live or die on whether I can do the next stretch with the same discipline I did the last ten months — which is to say, by picking the right three things every morning, ignoring the wrong forty, and trusting that compounding is real even when it doesn't feel like it.

If you're reading this.

If you're reading this and you're a coach, a commissioner, a parent — I built this for you, because I am you. I'm still standing on the sideline on Tuesday nights. I'm still in the commissioner GroupMe at 10 PM on a Friday answering field-conflict questions. I'm still the dad in the bleachers cheering for a kid whose story deserves to be told better than a blurry video clip in a group text.

PlayOS isn't a product I'm selling to you. It's the thing I wished existed, that I finally got tired of waiting for, and built.

— Brett