All-In Poker Club: a league’s weekly rhythm, in one place.

A weekly league creates a steady stream of small operational questions: who is coming, who checked in, what are the standings, what should players know and what does each venue need after the event?

The early setup had grown around the work. The next version needed a shared place for the event lifecycle, with live information that could be useful to the operator and the players.

I built a lightweight Firebase and Firestore app around the order people already followed: RSVP, check in, see the standings, read announcements and carry attendance into the venue invoice. Each step uses the same event data, so updates made during the night can show up where they are needed.

The player-facing steps and the operator’s follow-up use the same event record. Attendance connects the night people see with the venue work that follows it.

The club moved from an earlier Google Apps Script system to an app that supports the weekly operating rhythm across two partner venues. Players can RSVP, check in, follow standings and read announcements in one place.

Attendance data also feeds the venue invoices, connecting an operator task to the event record that produced it.

Players can also ask the app’s player desk, which answers league questions only from the club’s own rules, FAQ and records.

To explore the public schedule, open the live app and choose Schedule. The steps below explain the broader league workflow.

1. Event schedule and RSVPs. The schedule gives players the event details, and RSVPs show who plans to come.
2. Check-in and attendance. Check-in records who attended, giving the operator an attendance record for the later steps.
3. Standings and announcements. Players can use the same app to follow standings and read announcements about the league.
4. Venue follow-up. Attendance data also feeds venue invoices, linking the event night to the venue work that follows.

Jake runs All-In Poker Club and built its app around the weekly work of a league operating at two partner venues.

For another client, the useful starting point is the work people already do: understand its steps, connect the information those steps share and make the journey clear to the people using it.

If a recurring event, request queue or staff workflow has pieces that are hard to keep connected, let's talk about how people move through it.

This project is evidence of an approach, not a promise to clone its full stack for every client.