# Coaches Discovery Stage

## Current Status
- Ballbox is still in validation stage overall; there are no customers yet.
- Ballbox already has a sports admin/data foundation in the host app for `Coach`, `OpenMatch`, and `Class`.
- Current coach research input is an online form; Ballbox does not yet have enough real workflow evidence to lock the sports product thesis.
- No ATC integration exists in Ballbox today.
- The current questionnaire is documented in `docs/coaches-form-current.md` and still has no responses captured in repo docs.

## What Is Already Advanced
- Host app, admin shell, network core, TVs runtime/admin, and payments callback persistence are already implemented and should stay documented as implemented state, not future plans.
- Sports already has Ballbox-local admin/read APIs and CRUD UI for coaches, open matches, and classes.
- The next sports step is not "invent the module"; it is to validate which coach workflow deserves a product loop.

## Safe ATC Framing
- ATC is the current strategic moat hypothesis and likely core leverage behind the Ballbox thesis.
- Ballbox likely has an unusual wedge because ATC access/context and the relationship path through Seba may enable workflows that others cannot easily ship.
- Discovery should not treat ATC as optional product garnish, while still keeping v1 integration depth and exact dependency as open product questions.
- Still avoid documenting ATC as a live Ballbox integration or current source of truth until the integration actually ships.
- Current ATC API discovery notes live in `docs/atc-integration-discovery.md`.

## Assumptions That Stay Unvalidated For Now
- Which coach segment has the strongest pain.
- Whether the top pain is scheduling, reprogramming, filling empty slots, communication, payments, or something else.
- Whether coaches or clubs will pay, and for what exact outcome.
- Whether ATC data is necessary for the first valuable workflow or just a later acceleration lever.
- Whether the buyer is the coach, academy, or club owner.

## Minimum Doc Set For This Stage
1. `Opportunity Brief`
   - user, pain hypothesis, why now, why Ballbox, why this matters for padel centers
   - status: pending
2. `ICP + Segment Scoring`
   - freelance coach vs academy vs club coordinator vs premium clinic operator
   - status: pending
3. `Research Repository`
   - form questions, raw responses, interview notes, repeated quotes, objections
   - status: in progress via online form
4. `JTBD / Workflow Map`
   - current steps, tools, frictions, cost of failure, frequency
   - status: pending until enough responses exist
5. `Solution Thesis`
   - first wedge, why Ballbox, where ATC could matter, what is explicitly out of scope
   - status: pending
6. `ATC Integration Discovery / Spec`
   - only after the wedge requires court-availability data or ATC distribution
   - status: pending and intentionally deferred
7. `MVP PRD`
   - one workflow loop only, with success metric and exclusions
   - status: pending
8. `GTM One-Pager`
   - direct outreach, club intros, partner channels; ATC framed as potential future channel
   - status: pending

## Exit Criteria Before Building The Coach Product Loop
- Enough form/interview evidence to rank segments and choose one workflow wedge.
- Clear statement of user, buyer, pain, current workaround, and success metric.
- Clear answer on whether ATC is required for v1 or only makes v2 better.
- MVP PRD scoped to one loop, not a generic "SaaS para coaches de padel" bundle.