The Scenario: Third Thursday, Every Month, Doesn't Stop
BayJS started in 2019 in someone's living room in the Mission. It's now 80 regular attendees, a rotating cast of 3–4 speakers per event, a different venue sponsor each month (Stripe hosted in November; Vercel in February; a Ramen Shop in the Tenderloin for the December "unconference"), and James, who is somehow still the only dedicated organizer.
The recurring monthly complexity:
- Speaker confirmation emails sent 6 weeks out, reminders at 3 weeks and 1 week
- Venue capacity varies 50–120; food order based on confirmed RSVPs 72 hours prior
- Sponsor reimbursement tracking: not all expense receipts come in the same day
- Waitlist management when RSVPs exceed venue capacity
- Post-event speaker slides, photos, and video links organized for the newsletter
- A Discord community where half the attendees also live — coordination across two platforms
Part 2 — The Monthly SquadPlan Workflow
Explore: Finding Community Events That Attract the Same Audience
James uses SquadPlan's Explore feature to track what other tech events are happening the same week — to avoid collision with major conferences or competing meetups in SF. Two months ago, he almost booked a date that overlapped with a major AI summit at Moscone. Explore surfaced it first.
The Explore page surfaces public events by location and date. Checking for conflicts before confirming the venue booking has saved BayJS from three scheduling collisions this year.
Creating Each Month's Event with a Template Pattern
Each monthly event gets created from the same structure: event name (BayJS — [Month] [Year]), description with the venue address and parking notes, three talk slots in the itinerary, and food expense tracking enabled. It takes James about 8 minutes per month.
Creating February's event from the standard structure. The date, venue address, and talk schedule slots carry over from the template pattern. Done in 8 minutes.
Speaker Coordination via Itinerary Items
Each talk slot is an itinerary item with the speaker's name, topic, time slot, and a notes field for AV requirements ("HDMI adapter needed," "prefers standing, no lectern"). When a speaker drops 10 days out — it happens — the item is updated and attendees automatically see the change in their view.
Each talk as an itinerary item. When a speaker confirmed their title two days before the event, the update was live within minutes — no emails to resend, no Eventbrite description edits.
Polls for Recurring Group Decisions
What topics do attendees want for next quarter? Should BayJS do an outdoor summer session? Does the group want a dedicated "career/job board" segment added to meetups? Rather than guessing, James runs quarterly polls and reports results in the community Discord. Attendance went up 22% after he added topics that ranked highest in the Q3 vote.
Community alignment polls. Eight weeks before the event, attendees vote on topic preferences. The highest-ranked theme becomes the organizing theme for that month's speaker lineup.
Expense Reporting for Sponsor Reimbursement
Sponsors cover food and drink (usually $600–$900 depending on headcount). James purchases everything, uploads receipts to SquadPlan, and sends the expense report to the sponsor's finance team. Turnaround went from 3 weeks to 9 days average after switching from email chains.
Itemized food purchases logged with receipts attached. The sponsor receives an export showing exactly what was bought, when, and for how many people — which is exactly what their AP team asks for.
BayJS hasn't missed a third Thursday in 14 months. James now uses the 15 minutes he used to spend on coordination emails on building the pre-event Slack thread instead. This, he reports, is a material quality of life improvement.