The four stages of the ReviewCoach beta
ReviewCoach isn't opening to everyone at once. Here's why the beta grows in four deliberate stages, and what has to be true before it moves to the next one.
By Haytham Labrini (@playfulhay)
"Private beta" can mean almost anything. For ReviewCoach it means something specific: real footage from a real dance group, and a rollout that grows one small step at a time instead of opening to everyone on day one.
That's deliberate. A feedback tool either survives contact with a real class or it doesn't, and the cost of finding out in front of five students is a lot lower than finding out in front of fifty. So the beta moves through four stages, and each one has to actually work before the next one starts.
Stage 1 — we run it ourselves first
Before any real participant sees ReviewCoach, we run the entire workflow ourselves: a throwaway coach account, a throwaway student account, on the same phones people would actually use it on. Submit a clip, claim it from the queue, leave timestamped feedback, reply, check that one group genuinely can't see another group's footage.
Nobody outside the team is affected at this stage. It exists so that stage 2 starts with the boring bugs already gone.
Stage 2 — one coach, one student
The first real people. One coach, one student, their first real footage. We watch that first session happen rather than waiting to hear about problems secondhand — anything confusing about setting a password, joining the right group, or finding the review queue gets fixed before anyone else is invited.
This is also the point where anything privacy-related gets taken the most seriously: it's the first time real practice video and real names are actually in the system.
Stage 3 — a small group runs one real class through it
Three to five students, one real assignment, run start to finish. A short check-in after the first session and again during the week asks what was confusing and what wasn't.
The thing we're specifically watching for here is repetition: one person tripping over something is a data point, three people tripping over the same thing is a real workflow problem. Only the second kind gets fixed before moving on.
Stage 4 — the rest of the group joins
Everyone left in the existing dance group gets invited. This is the actual test of whether ReviewCoach is worth keeping, evaluated against plain questions rather than a gut feeling:
- Did people get in without needing hand-holding?
- Did most clips get a reply within a day or two?
- Did people actually open the feedback instead of ignoring it?
- Did people come back the following week?
- Would the coach choose to run another assignment through it?
That last one matters most. A tool a coach uses once because someone asked them to isn't the same as a tool they reach for on their own for the next class.
What happens after this group
If a cohort makes it through all four stages and the answers above hold up, the plan isn't to flip a switch and open ReviewCoach to the public. It's to invite another dance group and run the same four stages again. Going slow with one group at a time is how we find out ReviewCoach actually works before more people are trusting it with their footage.
If you run a dance group and want to be considered for a future cohort, reach out at reviewcoach@dancehub.io or read more on the beta welcome page.