CoachSlot - Mobile Booking and Payments for Solo Fitness Coaches

Acceptance Criteria

Booking flow: done when a client can select a session, pay via Stripe, and receive a confirmation SMS without coach involvement. Cancellation policy: done when a booking cancelled under 24h triggers an automatic Stripe charge for the configured fee. Dashboard: done when coach sees all upcoming sessions and total monthly earnings in under 2 seconds. Onboarding: done when a new coach can set up their profile and first session type in under 5 minutes.

How to build it, step by step

1. Run npx create-next-app@latest coachslot --typescript --app to scaffold with App Router. 2. Create Supabase project and define schema: coaches (id, slug, name, stripe_account_id), session_types (id, coach_id, name, duration_mins, price_cents, cancellation_policy_hours, cancellation_fee_pct), bookings (id, session_type_id, client_id, start_at, status, stripe_payment_intent_id), clients (id, coach_id, name, email, phone). Enable RLS on all tables with coach_id-scoped policies. 3. Add Supabase Auth with magic link and Google OAuth; store coach profile row on first sign-in via auth trigger. 4. Build /[coachSlug]/book public page: query Supabase for coach session types, render available slots using react-day-picker for date selection and a custom time slot grid component (scaffold with v0 prompt: 'time slot picker grid, 30 and 60 min slots, mark unavailable slots grey'); fetch booked slots from bookings table to exclude conflicts. 5. On slot selection, POST to /api/create-checkout with session_type_id and client details; create a Stripe PaymentIntent with capture_method=manual (to hold funds without capturing, enabling cancellation fee partial capture later) via Stripe Connect on the coach's connected account; return client_secret to frontend and confirm with Stripe.js. 6. Build /api/webhooks/stripe to handle payment_intent.succeeded (set booking status=confirmed), payment_intent.payment_failed (status=failed), and custom cancellation event to capture partial amount for cancellation fee. 7. On booking confirmation webhook, enqueue Twilio SMS reminders: use Supabase Edge Functions with pg_cron or a Vercel cron job at /api/send-reminders that queries bookings where start_at is between now+23h and now+25h (24h reminder) and now+55min and now+65min (1h reminder), then calls Twilio Messages API with coach-branded text. Send confirmation email via Resend using resend.emails.send() with a React Email template. 8. Build /dashboard page (auth-gated) showing: upcoming bookings from Supabase query ordered by start_at, monthly earnings summed from confirmed bookings, client list with last booking date. 9. Build cancellation logic: when client cancels via booking management link, check hours until start_at against session_type.cancellation_policy_hours; if within window, call Stripe paymentIntents.capture() with amount_to_capture set to the cancellation fee percentage of original amount; update booking status=cancelled_charged. 10. Set up Stripe Connect onboarding: on coach signup, call stripe.accounts.create({type:'express'}) and stripe.accountLinks.create() to redirect coach through Stripe Express onboarding; store stripe_account_id on coaches table. 11. Deploy to Vercel, set all env vars (SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, RESEND_API_KEY), configure Stripe webhook endpoint in dashboard pointing to your Vercel deployment URL.