Find Flag Football

The problem

Adult flag football hosts were stuck stitching together static sites and spreadsheets. Running events means discovery, registration windows, capacity and waitlists, payments, refunds, teams, schedules, brackets, communication, and payouts. Those are workflows generic tools leave fragmented.

The solution

I designed and built Find Flag Football as an end-to-end operations product: players find and register for events; hosts and org admins create events, manage rosters and competition, collect payments through Stripe, and get paid via Stripe Connect, plus waivers, branding hubs, notifications, and admin tooling.

Technical execution

• Next.js App Router with a clear domain architecture, API routes, use cases, repositories, and ports/adapters for Stripe and email.
• Supabase (PostgreSQL) for auth, data, storage, and row-level security across registrations, payments-related tables, posts, gallery, and admin workflows.
• Stripe Checkout for registrations and related payments, Stripe Connect for host payouts, webhook-driven fulfillment, and idempotent event handling.
• Transactional and digest email via Resend and React Email, preference-gated notifications, and scheduled jobs for reminders and digests on Vercel.
• Mobile-first surfaces for field and sideline use, including PWA installability for the public app.

Why it matters

It turns a real organizational headache, running and finding adult flag football events, into a product hosts can operate and players can trust. Proof that I can take messy operational needs and ship a production system tying UX, data, payments, and automation together.