# Coaches Opportunity Brief

## Status
- Stage: draft
- Last updated:
- Owner:

## Context
- Ballbox today already has host app, admin, network, TVs, payments, players, and a sports foundation.
- Sports foundation already includes `Coach`, `OpenMatch`, and `Class` as Ballbox-local entities.
- Coach discovery is still early and currently based on an online form plus any follow-up interviews.
- Do not write this doc as if the coach pain or ATC dependency were already validated.

## User Hypothesis
- Primary user: coach or coordinator running repeated weekly group classes
- Buyer: unknown yet; default hypothesis is coach, with explicit fallback that club/coordinator may become the payer
- Segment: coach-first discovery, with strongest current attention on group-class operators
- Why this segment first:
  - likely recurring operational pain
  - compatible with Ballbox current sports foundations
  - can be validated before ATC API access exists

## Problem Hypothesis
- Main pain: coordinating recurring classes creates manual admin overhead, missed communications, and avoidable schedule friction
- Current workaround: WhatsApp, spreadsheets, calendar tools, manual follow-up, club coordination by message or phone
- Frequency: likely weekly, sometimes daily during changes or cancellations
- Cost of the problem: lost time, stress, weaker student experience, and possible lost revenue when classes break or reschedule badly
- Why current tools are insufficient: they are fragmented, reactive, and not built around repeated class operations

## Why Ballbox
- Why Ballbox could matter for this workflow:
  - Ballbox can become the operational layer around classes using court/club context that ATC can unlock
- Why now:
  - coach validation is starting now, Ballbox already has sports primitives, and ATC creates a real strategic opening that generic tools do not have
- What Ballbox already has that helps:
  - sports data/admin foundation
  - network model for clubs and venues
  - existing operator/admin surfaces

## ATC Relevance
- Possible ATC advantage if confirmed:
  - better court-aware scheduling and reprogramming
  - possible future distribution inside the ATC ecosystem
- What depends on ATC:
  - any workflow that requires live court availability or booking writes
- What does not depend on ATC:
  - validating class coordination pain before the integration is live
  - validating repeated workflow friction before the integration is live
- Current status: no Ballbox ATC integration yet, but ATC is still core to the Ballbox strategic thesis and expected long-term moat.

## First Wedge Candidate
- Leading workflow hypothesis: group/class coordination
- User trigger: weekly class planning, recurring changes, attendance coordination, or operational follow-up
- Desired outcome: keep classes organized with less manual back-and-forth and fewer avoidable failures
- Why this is smaller and sharper than a generic coach SaaS:
  - focuses on one recurring operational loop instead of trying to solve scheduling, CRM, payments, and growth all at once
- Final wedge decision still waits for repeated evidence from interviews or strong form patterns.

## Evidence So Far
- Form signals: questionnaire is live, but no responses are documented yet
- Interview signals: none yet
- Repeated quotes: none yet
- Unknowns that still matter:
  - whether this is truly the highest-frequency pain
  - whether the real buyer is the coach or the club/coordinator
  - whether v1 needs ATC read access only or also booking/write access

## Success To Keep Investigating
- We continue if:
  - repeated interviews show recurring coordination pain
  - users describe manual workarounds and costly failures
  - the workflow can be narrowed into one MVP loop
- We pause or change direction if:
  - operational pain is weak or secondary
  - the pain is mostly commercial, not operational
  - the workflow is too custom per club/coach to generalize

## Immediate Next Questions
- Question 1: is the pain stronger for group-class coaches or club/academy coordinators?
- Question 2: is reprogramming actually a more painful wedge than base coordination?
- Question 3: if coaches love the workflow, who actually controls budget and adoption?