Pride Ops — Wiki Entry Point

Purpose: Business operations, governance, and strategic management workstream. Covers venue operations (staffing, rostering, suppliers, licensing, kitchen, programming), governance (board, shareholders, compliance, legal structure), and strategy (turnaround levers, revenue diversification, capital raise, expansion).

Loaded by: _ops-project-setup/INSTRUCTIONS.md (Cowork). No dedicated code repo — operates through Deputy, Google Workspace, Asana, Gmail, Calendar via Chrome MCP and Computer Use.

Always load at session start

Load when work touches…

Strategic levers (top 3)

Governance and compliance

Staffing

Kitchen, food, suppliers

Insurance

Marketing / audience

Operational gaps and risks

Expansion

Active decisions

Source documents

Analysis relevant to this project

Cross-project context

  • finance — Ops decisions have Finance consequences (kitchen → balance sheet; licence → cost line). Coordinate on timing.
  • humphrey — Ops processes feed Humphrey. If Ops documents a new process (banned persons list, incident form), flag for Humphrey to surface it.
  • website — Ops decisions about kitchen, licence, and programming shape what’s true on the website. Never make forward-looking claims on the site ahead of Ops reality.

Key operational facts

  • Trading: Wed–Sat only (Sun–Tue closed)
  • Revenue: ~$20k–$25k/week vs $25k survival threshold
  • Weekly targets: Wed $1.5k / Thu $2.5k / Fri $6k / Sat $15k
  • Weekly costs: ~$20.7k–$21.7k (performers $4k, wages $7k, security $2k, stock $6–7k, rent $1.7k)
  • Saturday collapse: $20k+ → ~$10k (single biggest problem)
  • Walk-in trade essentially dead — pre-sale ticket-driven

Recent updates

  • 2026-04-24 — Sub-index created (WIKI-META-1)