# Coaches Validation Checklist - 2 Weeks

## Goal
- End the two weeks with one clear wedge, one clear segment, and a yes/no on whether ATC is required for v1.

## Week 1

### Day 1
- Freeze the initial hypotheses in `docs/coaches-opportunity-brief.md`.
- Define target segments in `docs/coaches-research-repository.md`.
- Confirm what the form is trying to validate vs what it cannot validate.

### Day 2
- Review incoming form responses.
- Tag each response by segment and pain theme.
- Identify weak questions or ambiguous answers in the form.

### Day 3
- Book follow-up calls with the most promising respondents.
- Prioritize respondents with concrete operational pain, not generic interest.
- Write an interview script around current workflow, workaround, and cost of failure.

### Day 4
- Run interviews.
- Capture exact quotes, current tools, and failure moments.
- Note whether ATC or court availability comes up naturally.

### Day 5
- Summarize patterns.
- Rank top 2 workflow wedges.
- Kill weak hypotheses early.

## Week 2

### Day 6
- Pick one provisional wedge.
- Write the first JTBD/workflow map from actual evidence.
- Define what Ballbox would improve in one loop.

### Day 7
- Decide whether the wedge needs ATC read access only or also ATC booking/write access in v1.
- Keep ATC central to the Ballbox thesis even if the first validated loop starts with lighter integration depth.
- List the minimum ATC data/actions needed before any spec work.

### Day 8
- Write the first solution thesis.
- Explicitly list what is out of scope.
- Keep claims tied to observed evidence only.

### Day 9
- Draft the MVP PRD for one workflow loop.
- Add one success metric and explicit exclusions.
- Check that the PRD is not a generic multi-feature coach platform.

### Day 10
- Review the full discovery set.
- Decide: continue, narrow, or pivot.
- Update `PLAN.md` and discovery docs with the decision.

## Exit Criteria
- One segment chosen.
- One workflow wedge chosen.
- Strongest repeated pain documented with quotes.
- Buyer hypothesis documented.
- Clear answer on ATC requirement for v1.
- MVP PRD ready or consciously deferred.

## Failure Modes To Watch
- Too much interest language, not enough pain evidence.
- Building around ATC before proving the workflow deserves to exist.
- Mixing coach, academy, and club coordinator needs into one MVP.
- Confusing "would use" with "would pay".
- Jumping from form responses straight into product scope.