About OrgFrame

Sports software has been bad for twenty years. We took it personally.

The tools sports organizations run on were never built for sports organizations. They were built for something adjacent — event ticketing, generic CRM, a WordPress plugin somebody's cousin wrote in 2011 — and then bent until they almost fit. We got tired of almost.

Origin

Why We Built It

Every organization we worked with had the same drawer of half-solutions. A registration tool from one vendor. A scheduling tool from another. A payments processor that never quite talked to either. A Google Drive where documents went to die. And a group text with forty parents that somebody was eventually going to have to leave, publicly, at 11pm.

The work those organizations did was genuinely beautiful. Coaches coaching, parents driving four hours on a Saturday, whole leagues running on donated time. The software was not beautiful. The software was in the way, and everyone had quietly accepted that it always would be.

We didn't accept it. We're a small team with ten years inside sports operations, building this slowly and deliberately with a handful of partner organizations — slowly because these orgs run year-round and we don't get to break somebody's season to hit a launch date. When we ship, it works. When it doesn't, you get a human who knows why.

Principles

Four Opinions We Refuse to Soften

Good software is invisible.

Nobody has ever finished a season and said the highlight was the admin panel. Coaches should coach, operators should operate, and this thing should get out of the way and stay there.

One roster, no exceptions.

A person exists once. Every module reads the same record. If a feature would require a nightly sync between two of our own tables, we don't ship the feature — we fix the model.

Twelve deep beats twenty shallow.

Every platform in this category grew by acquisition and it shows the moment you click between two of their products. We would rather have twelve modules that genuinely know about each other.

Volunteers are not a growth channel.

The people running youth sports are donating their evenings. The job is to give some of those evenings back — not to add one more dashboard they're supposed to check, and definitely not to sell ads against their families.

Team

Who You'll Actually Talk To

Deliberately small. There is no tier-one queue, no account manager who has to check with engineering. You email, and the person who wrote the code replies. That stops being true at some size — it is very true right now.

Koen StewartFounder, Product & Engineering We're Hiring avatar

We're HiringDesign · Engineering · Partnerships

Recognize your organization in any of that?

We onboard partner organizations a few at a time, on purpose. If the drawer of half-solutions sounded uncomfortably specific, that's the conversation.

Book a Demo Just Say Hello