# Coaches Discovery Execution Plan

## Current Constraint Set
- No ATC API access in Ballbox yet.
- No coach form responses documented yet.
- Ballbox sports only has local admin/data foundations today.
- Therefore the immediate job is not shipping the coach product; it is reducing uncertainty in the right order.

## How We Should Work
- Ballbox owns docs, synthesis, and structure.
- Founder only needs to answer business-logic or product-decision questions when they materially change direction.
- Until then, Ballbox should keep moving by default and mark assumptions clearly.

## Step 1 - Freeze The Discovery Frame
- Goal: avoid generic "SaaS para coaches" thinking.
- Outputs:
  - `docs/coaches-discovery-stage.md`
  - `docs/coaches-form-current.md`
  - `docs/atc-integration-discovery.md`
- Done when:
  - current stage, current constraints, and ATC reality are explicit

## Step 2 - Choose Who We Are Evaluating First
- Goal: narrow the first target segment before interviews start.
- Output:
  - `docs/coaches-icp-segmentation.md`
- Decision to make:
  - which segment gets first-class attention in interviews and wedge evaluation

## Step 3 - Compare Wedges Before Falling In Love With One
- Goal: rank candidate workflows even before strong evidence arrives.
- Output:
  - `docs/coaches-wedges-matrix.md`
- Candidate wedges to compare:
  - scheduling / finding court availability
  - reprogramming classes
  - filling empty slots
  - group/class coordination
  - collections/admin follow-up

## Step 4 - Prepare High-Quality Interviews
- Goal: make the next 3-5 conversations much more useful than the form.
- Output:
  - `docs/coaches-interview-script.md`
- Done when:
  - we know exactly how to validate workflow, frequency, workaround, buyer, and ATC dependence

## Step 5 - Run Design Partner Discovery
- Goal: get strong evidence from a very small number of relevant coaches.
- Output:
  - update `docs/coaches-research-repository.md`
- Success condition:
  - repeated pain pattern, not just interesting anecdotes

## Step 6 - Write JTBD Only After Evidence Exists
- Goal: map real workflow, not imagined workflow.
- Output:
  - future `docs/coaches-jtbd-workflow-map.md`
- Rule:
  - do not write as fact until interviews support it

## Step 7 - Decide How ATC Enters V1
- Goal: keep ATC as core strategic leverage without assuming the wrong integration depth too early.
- Decision:
  - `ATC read access is enough for v1`
  - `ATC read plus booking/write access is required for v1`
  - `ATC is core in product logic now, with deeper distribution later`

## Step 8 - Only Then Write MVP PRD
- Goal: one workflow loop, one user, one success metric.
- Rule:
  - no multi-feature coach platform PRD

## Founder Checkpoints
- Ballbox should only interrupt for founder input when one of these is blocked:
  - choosing the first segment
  - choosing which wedge to prioritize after synthesis
  - deciding whether to lean into ATC or keep v1 independent
  - deciding whether the likely buyer is coach vs club/academy