Registrations
Processed across 3 tournaments (Apr–Jun 2026).
Proof of Work / Custom Tournament Platform
Tournament Titans: a live registration system built from scratch
A hand-built pool tournament website that does more than announce an event. It accepts player registrations, manages capacity and waitlists, gives operators a private dashboard, and sends the emails needed to keep players informed.
Results
Filling up, event after event
Table Titans came to JARGUS with no brand, no website, and no system. We built the whole engine — logo, hosted website, check-in dashboard, automated player emails, and the paid ads that drive sign-ups — and the tournaments keep growing.
Growth every event
Sign-ups rose each tournament — the latest hit 42 of 50 seats (~84% capacity).
Confirmed vs cancelled
The few cancellations came through self-serve links, freeing seats ahead of time.
Partner, whole stack
Brand, build, operations, and advertising — all run by JARGUS.
Glanceable proof
What shipped
The useful proof is the operating system behind the page: registration intake, database state, admin controls, and automated player communication.
Public launch
Responsive tournament site with venue details, rules, and registration.
Structured data
Supabase-backed registrations, tournaments, waitlist, and contacts.
Private admin
Password-gated dashboard for operators to manage players and tournaments.
Email operations
Confirmation, waitlist, reminder, and broadcast email workflows.
System map
From signup to operator action
This is the simple path a prospect can understand in seconds: the public site captures the signup, the backend decides the status, and the admin page gives the operator a clean control surface.
01
Player chooses a tournament date
02
Registration validates rating and contact fields
03
Server checks capacity and duplicate entries
04
Supabase stores confirmed or waitlisted status
05
Resend sends the right player email
06
Admin dashboard keeps operators current
Operator view
A private dashboard, not just a landing page
The admin layer is the strongest proof that this is a working product. The public version below is a redacted representation of the dashboard patterns used for player tracking.
Total50
Confirmed48
Waitlist7
Verified42
| Player | Skill | Status | Rating | Payment |
|---|---|---|---|---|
| A. Player | APA 5 | Confirmed | Verified | Paid |
| B. Player | Fargo 430 | Confirmed | Pending | Unpaid |
| C. Player | APA 4 | Waitlisted | Verified | Paid |
Built pieces
- Public registration form with client and server validation
- Capacity-aware confirmed vs. waitlist logic
- Admin tools for tournaments, contacts, attendance, payment, and verification state
- Confirmation, waitlist, reminder, broadcast, unsubscribe, and cancellation paths
Automated communication
The email layer keeps the tournament moving
Player communication is part of the product: registration confirmation, waitlist placement, reminders, and admin-triggered blasts are handled as repeatable workflows instead of manual one-off messages.
Confirmation
Date, venue, start time, check-in window, rating, and player name.
Waitlist
Capacity overflow routes players into waitlist status with a position.
Reminder and blast
Admin-controlled tournament updates with unsubscribe handling.