# Coaches Interview Script

## Goal
- Learn the real workflow, not just collect opinions.
- Identify pain frequency, workaround, cost of failure, buyer, and whether ATC-like data would actually help.

## Interview Target
- Prefer coaches or coordinators with repeated weekly class operations.
- Prefer respondents with clear admin burden over purely aspirational respondents.

## Interview Structure

### Part 1 - Context
- What type of classes do you run most often?
- How many classes or groups do you coordinate in a normal week?
- Do you work independently, for an academy, or through one or more clubs?

### Part 2 - Current Workflow
- Walk me through how you schedule a normal week.
- What tools do you use at each step?
- Where do things start breaking?

### Part 3 - Pain And Frequency
- What is the most annoying recurring part of this process?
- How often does that happen?
- What happens when it goes wrong?
- Who loses time or money when it fails?

### Part 4 - Workarounds
- How do you solve it today?
- What is frustrating about that workaround?
- Have you tried any tool or process to improve it?

### Part 5 - Buyer / Value
- If this problem disappeared, what would improve first: time, revenue, fewer cancellations, less stress?
- Would you pay for that yourself, or would the club/academy need to pay?

### Part 6 - Court Availability / ATC-Like Dependency
- How important is knowing real court availability to solving this problem?
- If you had better visibility into available courts and bookings, would that materially change your workflow?
- Is this problem still painful even without direct booking integration?

## Red Flags
- User speaks in vague preferences, not real recurring events.
- Pain is rare or low consequence.
- Workflow is too unique to one club or one person.
- The buyer is unclear and the user would not pay.

## Good Signals
- User can recall recent concrete failures.
- Pain happens weekly.
- Workaround is manual and annoying.
- Outcome maps clearly to time saved, revenue recovered, or fewer class losses.
- User volunteers to keep talking or test something.