Damian Rodriguez
S·01 · SaaS · Live · 2026
PriorityCourt
Court scheduling that resolves conflicts the way a good front desk would.
prioritycourt.com ↗01 — The brief
A club with twenty courts and six kinds of user — players, coaches, hitters, staff, health practitioners, admins — runs on a scheduling problem that spreadsheets and goodwill cannot hold. Every double-booking is a member standing on a full court; every manual fix displaces someone else invisibly.
PriorityCourt encodes the judgement of an experienced front desk: when bookings collide, a displacement engine resolves them in priority order — cross-court swap, backward shift, forward shift, nearest free block — so the calendar heals itself instead of breaking quietly.
02 — The product
The schedule, by priority.
03 — The identity
04 — The build
- —Displacement engine — conflict-free resolution in four ordered strategies
- —Six-role permission model with founder override
- —Paired bookings, waitlists, and hitmate matchmaking
- —725 passing tests against real scheduling scenarios
- —Supabase backend — 22 tables under row-level security
- —GDPR layer — hashed credentials, data export, account deletion, audit logs
- —Commercial pack — security, privacy, and data-isolation documentation
05 — The journey
- Spring 2026Born on a real scheduling floor: twenty courts, six kinds of user, and a booking sheet that failed daily.
- April 2026The displacement engine lands — collisions resolved in priority order, proven against 725 tests.
- May 2026The prototype outgrows itself: 34,000 lines migrate to Supabase behind row-level security.
- June 2026It becomes a product — brand, security and data-isolation documentation, sales and onboarding operations.
- August 2026Live at prioritycourt.com; commercial rollout begins.
06 — The state
Live and in commercial rollout to clubs and academies, with a SOC 2 / ISO certification path underway.
Begin something