Productizing this for a coaching business

Scenario

You run a cycling coaching business or training-camp operation. You have 50–500 athletes. You want them to upload rides, see training load, get AI-assisted feedback, and stay engaged between sessions — under your brand.

What gets deployed

• Athlete onboarding and Strava connect.
• Coach-facing dashboard: roster, load by athlete, flags (overload, undertraining, missed plans).
• AI coach branded to your voice, scoped to your training philosophy.
• Workout library and per-athlete .zwo generation.
• MCP endpoint so you (the coach) can interact via Claude Desktop or your own tools.
• White-labelled domain, your auth, your data.

Out-of-scope (deliberately)

• Smart trainer control (use Zwift, Rouvy, TrainerRoad).
• Competing with Strava as a social network.

Note: Routebook ingests rides via Strava sync or direct FIT upload. Most users prefer Strava — one-time connect, automatic backfill — but the FIT pipeline is there for athletes without Strava.

Rough timeline

4–8 weeks from kickoff to athlete-ready, depending on auth, branding, and the depth of coach-facing features. Hosting on Vercel + Supabase keeps ops light.

Next step

Email info@orbital.co.nzwith your athlete count, current toolchain, and what success looks like. I'll come back with a fixed-scope proposal.