360PhysioClub

the problem

Sunday, 11pm. The coach is at his desk building next week's training plans — one by one, in a Word document, exporting each to PDF, attaching them to Viber. Tuesday morning a member asks to move Wednesday's run to Thursday. He types "yes". There's no system that knows. The plan says Wednesday. Reality says Thursday. Nobody's keeping score.

Throughout the day, the same loop: "I'll come at 7." "I'll come at 8." Members pick the quietest-looking hour by reading each other's replies. "When are you open this week?" — because the gym schedule shifts week to week and lives in one person's head. A race comes up: information goes out as a screenshot, RSVPs trickle back as messages, the count lives in a notes app.

The setup worked, because this is the kind of coach who makes any setup work. But one person was being asked to be the system, the surface, the memory and the coach — all at once, twenty-four-seven.

the system

360PhysioClub is a private members' platform with two sides: the coach's and the athlete's.

For the athlete: a real training calendar on a real week — every workout a card you can move, complete or skip, so the plan bends with your life instead of breaking on Tuesday. After each session, a check-in: how it felt, pain level, a voice note if you'd rather talk than type, and a screenshot of your watch stats. This week's gym hours as they actually are, with live capacity per slot. Race pages with the details, the entry list and the chatter kept in one place. Direct messages with the coach that don't compete with eighty other people's questions.

For the coach: a dashboard that answers "who needs attention today?" at a glance. A plan builder in his own notation, with his own protocols and exercise library, so a new plan is dragging and adjusting rather than retyping. Every check-in read for him — transcript, extracted numbers, planned-versus-actual, a traffic light — with the AI switchable to on-demand or off, because the athlete's note and photo are always there regardless. End-of-plan retrospectives that compute the figures exactly (sessions done, kilometres actual vs planned, which weekday they always move away from) and only then ask the model for judgement. A three-month read of the season. Member CRM, payments tracking, roles for assistants with doors that are actually locked.

Push notifications with quiet hours, so it works like a real messaging app without buzzing at night. Installable on the phone. Greek and English.

the layers

• Interface — Next.js 16 · React 19 · Tailwind · drag-and-drop calendar (DnD Kit) · installable PWA
• Database — Supabase Postgres with row-level security across roles (coach, assistants, members) · adherence event log · storage for voice notes and screenshots
• AI — Gemini for transcription, stat extraction, plan-vs-actual reading, retrospectives · per-feature modes (automatic / on demand / off) · spend dashboard and cost caps
• Automations — plan publishing emails, weekly plan summaries, race groups, scheduled jobs
• Notifications — web push with per-user do-not-disturb · Resend email
• Deployment — Vercel · custom club subdomain · Playwright end-to-end tests

the result

The coach's Sunday night is a plan builder, not a Word document. Members see their week the way they see the rest of their lives — on a calendar, on their phone — and "can I move Wednesday?" is a drag, not a message. "When are you open?" and "is there room?" are answered by the system, giving every conversation back to coaching.

The part we're proudest of is the shape of the AI: it never replaces what the athlete submitted, it reads it. With AI fully off, the app is still everything the club replaced — just organised.

status

Built 2025–2026 for a real club and its coach. In testing with the coach and first members from September 2026; launching on the club's own subdomain.