Account boundary

Profile, service area, and billing readiness

This screen defines how the demo app will map into Supabase profiles, service areas, alerts, and Stripe billing without pretending a real login exists yet.

Auth

Ready

Profile persistence

Ready

Service areas

Ready

Billing

Ready

Demo profile

Company

DFW Roof Crew

Owner

Demo Owner

Email

owner@dfwroofcrew.example

Metro

Dallas-Fort Worth

Role

Owner

Status

Demo pending auth

When Supabase Auth is connected, this shape maps to a profiles row keyed by the authenticated user id. Until then it stays local/read-only.

Connected service area

Broader DFW storm route

ZIPs: 75023, 75034, 75070, 75248, 76012, 76108 • 42 mile radius

Latest alert: 214 likely impacted homes.

Edit setup flow

Implementation notes for the backend handoff

  • • /api/account/status exposes the same safe readiness boundary for smoke tests and Vercel verification.
  • • Missing Supabase env vars: none.
  • • The service-area form remains validation-only until it can attach rows to an authenticated profile.
  • • Billing remains tied to Stripe Checkout and the placeholder lifetime Price ID until Ben supplies the real value.