AI search · Crew logistics
Featured buildCrewFlow AI
Hands-on build · Media & Entertainment, live sports
AI search is the product
Example: “Who can cover Jets at Chargers on Sunday?”
Ask in plain English, not filters
A first-time scheduler shouldn't have to learn the crewing system's data model.
The AI explains its pick
People trust a recommendation when they can see the reasons behind it.
A person always decides
The AI recommends, a coordinator approves, and every decision is logged.
Plugs in, doesn't replace
It sits read-only on top of the crewing system a team already uses, so nobody has to migrate.
Crew logistics for live sports where the week is the home screen: one US map with every event and every crew member, and an AI search bar that answers staffing questions in plain English.
Why it mattered
Crews get scheduled one event at a time, so nobody sees the whole week. Putting the week on one map, and letting people ask for what they need instead of filtering for it, turns staffing from a hunt into a decision.
- Problem
- Staffing tools are built around one event at a time. Coordinators jump between screens to work out who is nearby, who is free, and who fits, and the tradeoffs across a full week of events stay out of view.
- Key decisions
- Made search the front door. The model turns a question into validated filters and the matching engine does the deciding, so every answer is grounded in real availability.
- Kept a person in charge. The AI recommends and explains, a coordinator approves in two clicks, and every decision is logged.
- Designed for trust over cleverness. The AI can't invent dollar figures, because every answer is checked against the matching engine, and if the AI is down the app falls back to basic matching.
- Plugs in on top of the crewing system a team already uses, through a read-only adapter layer, instead of asking anyone to migrate.
Under the hood
- Open-weight LLM (gpt-oss-120b on Groq) turns questions into validated filters
- Every answer checked against the matching engine
- Basic matching fallback when the AI is unavailable
- Read-only adapter layer that plugs in on top of your crewing system
- Python and SQLite backend, strict TypeScript and MapLibre front end
- 141 automated tests, built on open-source tools, Docker on a free host
Outcome
A working product anyone can try, with demo data from the public 2026 NFL schedule. The real exercise was product judgment: where AI earns its place, and where a person should stay in charge.
Runs on a free host, so the first load can take about a minute to wake up.
