We shipped a demo last week.

Not a mockup, not a Figma prototype, but a working interface – sidebar nav, conversation layer, roster management – running on our stack. If you want to see what we're building toward, reach out and we'll send you a link.

A coach uploads their roster. LaRue contacts the athletes. Athletes complete their First Read and ACSI assessments. LaRue surfaces the results back to the coach: who's flagged, who's ready, who needs follow-up.

That's the loop. Coach uploads on Monday. By Wednesday, nine of twelve athletes have completed their assessments. LaRue shows the coach the picture.

Nobody built that for them.

That's the gap we spent the last few weeks mapping: what assistant coaches actually do, why coaches enter the profession, and where the structural breakdown happens between their motivations and their daily reality.

Assistant coaches exist because head coaches can't maintain individual attention across a full roster. The assistant is the proximate relationship – the person who actually knows what's going on with each athlete and surfaces what matters. In practice, that function fails almost everywhere it operates. Parent volunteers at youth level. Teacher-coaches doubling up at high school. Overextended professionals at college level carrying mental health responsibilities they were never trained for, with no tools to handle them systematically.

What coaches want – what they describe when you ask – is knowing where their athletes are before something goes wrong. Not after the performance collapses. Not after the parking lot conversation. Before.

The VAC, a virtual assistant coach, is readiness infrastructure.It fills the structural role of a good assistant coach: available between practices, consistent with every athlete on the roster, surfacing signal without requiring the athlete to volunteer it or the coach to ask for it.

The architectural decision we kept returning to during the demo build was the introduction problem.

The coach knows they signed up for a VAC. The athlete just gets a message from something called LaRue. Those are two completely different experiences of the same event. If we don't design the gap between them deliberately, the athlete receives it as cold outreach from an unknown sender asking them to complete an assessment. Which they'll ignore.

The frame we landed on: hospitality. The best hotel experiences don't feel like check-in. They feel like arrival: someone anticipated you, your preferences were already known.

That's what LaRue can do for an athlete if it's set up right. Not "complete this assessment." Something closer to: your coach set this up for you. We're glad you're here.

The coach's onboarding flow needs to end with a message they review and send to their team – a warm handoff that transfers their credibility to LaRue's first contact. Without that, LaRue is cold. With it, LaRue arrives as something the athlete's coach already vouched for.

This matters especially in youth sports where parents are the trust gatekeepers. If the program feels thoughtful and safe, athletes get permission to engage fully. The parent dimension isn't a compliance checkbox. It's a design constraint that determines whether the system works.

Privacy is where the architecture gets specific.

Research on sport psychology practitioners in professional football academies found that coaching staff actively tried – sometimes subtly, sometimes directly – to get practitioners to breach athlete confidentiality. That's not an edge case. That's the pressure environment this tool operates in.

The structural separation we built: what athletes tell LaRue and what coaches see are architecturally separate, not policy-separate. The coach sees activation and regulation coordinates, a readiness band (1–4), a flag if LaRue thinks an athlete needs support. The content of the conversation that produced those coordinates stays between the athlete and LaRue.

The one exception is explicit and stated upfront: safety. If LaRue ever has reason to believe an athlete is at risk of harm, it tells someone. That's the only time the rule changes.

This is the condition under which athletes will actually be honest. A system that reports conversations to the coach is a system athletes perform wellness for rather than use.

The demo runs end to end. We're opening a small pilot cohort: coaches who want a 20-minute walkthrough of what the system actually does before we scale. No roster enrollment required. Just a look.

The next build is the coach.md intake: a calibration layer that tells LaRue how a specific coach operates – what they prioritize, which athletes they typically struggle to reach, what their philosophy actually is versus what they say it is. That's what makes LaRue's recommendations fit the environment instead of defaulting to generic protocols. The question architecture is settled. The prompt that parses coach responses and generates the output is next.

More on that in the next update.

If you're building in this space or know a coach who should be in the pilot cohort: Interest list →