# Coaches Wedges Matrix

## Status
- Stage: draft
- Evidence level: hypothesis only

## Candidate Wedges

| Wedge | Core problem | User value if solved | Depends on ATC? | Ballbox fit today | Validation priority | Main risk |
| --- | --- | --- | --- | --- | --- | --- |
| Scheduling / court finding | Coach cannot easily align classes with real court availability | Faster class planning | High | Medium | High | Might depend too much on ATC access |
| Reprogramming | Last-minute changes create manual chaos | Save time and preserve revenue | Medium to high | Medium | High | Pain may be episodic, not constant |
| Fill empty slots | Unused time and weak occupancy reduce income | Recover revenue | Medium | Medium | Medium | Needs strong demand-side data/matching |
| Group/class coordination | Managing groups, attendance, reminders, and slots is messy | Operational clarity | Low to medium | High | High | Can drift into generic coach SaaS |
| Collections/admin follow-up | Chasing payments and reminders consumes time | Time savings, maybe cashflow | Low | Medium | Medium | Could be too generic and weakly differentiated |

## Current Ballbox Bias
- Strongest current strategic bias should be toward wedges that become clearly better with real court/club context.
- ATC dependence is strategic by default; the question is not whether ATC matters, but how deeply v1 must integrate with it.

## Initial Recommendation
- Shortlist for discovery:
  1. Group/class coordination
  2. Reprogramming
  3. Scheduling / court finding

## Why This Shortlist
- Group/class coordination is likely the easiest wedge to anchor in real coach pain while still keeping room for ATC-backed class/court context.
- Reprogramming is high pain and likely becomes much stronger with ATC availability and booking data.
- Scheduling / court finding is strategically attractive because it leans hardest into Ballbox's unfair advantage through ATC.

## Kill Criteria
- If a wedge sounds attractive but users describe it as infrequent, low-cost, or already solved, drop it.
- If a wedge only works with deep ATC write access and that access is uncertain, deprioritize it for v1 in favor of an ATC-read-first wedge.
- If a wedge requires broad CRM/payments/attendance/product surface from day one, narrow it or drop it.