SwiftSeat — the spec

SwiftSeat is a self-service client portal for solo business owners who run or attend speed dating events. It handles discovery, booking, and post-event contact exchange without operator involvement — so the organiser's calendar fills itself and attendees walk away with the connections they came for.

---

Decisions locked

---

The core loop

1. Attendee lands on the portal, creates or logs into their account, and sees the event calendar.
2. They select an upcoming speed dating event, review the attendee cap and format, and complete payment.
3. Booking confirmation fires via email or SMS; the event is added to their personal calendar.
4. On event day, the portal surfaces their session schedule and the anonymised profiles of other attendees.
5. During or after the event, the attendee marks which profiles they want to connect with.
6. Where both sides opt in, full contact details are unlocked and each party receives them by email or SMS.

---

v1 scope

Event Calendar — A filterable calendar view listing all upcoming speed dating events with date, time, capacity, and price. Lives on the main portal home screen; first thing every user sees after login.

Booking and Payment Flow — Attendees select an event, confirm their spot, and pay in a single checkout sequence. Stripe (or equivalent) handles the transaction; a confirmation record is written to the CRM immediately.

Automated Confirmation and Reminders — Triggered emails and SMS fire at booking, 24 hours before the event, and 1 hour before. No organiser action required; this is the engine behind the 30-day hands-off goal.

Attendee Profile View — A read-only screen showing other confirmed attendees' business-focused profiles (name, role, industry) once an event is within 48 hours. Mutual contact exchange is gated behind the event itself.

Mutual Contact Exchange — After the event closes, attendees select whom they want to connect with. Where both parties choose each other, the portal delivers full contact details automatically via email or SMS. No manual exports, no spreadsheets.

---

Deliberately later

• Quick profile creation with business focus — needs iteration on which fields matter; better after v1 data shows what attendees actually read.
• Real-time match suggestions based on industry — requires enough booking history to make suggestions meaningful; ship after the first cohort.
• In-event timer and conversation prompts — event-day UX is a separate surface; scope it once the booking loop is proven stable.
• Post-event rating and mutual interest matching — ratings create moderation overhead; add when the user base justifies it.
• One-click contact export — mutual exchange covers v1; bulk export is a power-user feature for regulars, not first-timers.
• Recurring booking templates for regulars — valuable once repeat-attendee patterns are visible in data.
• Event host dashboard and analytics — organiser tooling is a second product layer; build it once hosts are asking for it by name.

---

Data model sketch

• users — id, name, email, phone, role (attendee / organiser), created\_at
• profiles — user\_id, business\_name, industry, bio, contact\_email, contact\_phone
• events — id, title, date\_time, location, capacity, price, status
• bookings — id, user\_id, event\_id, payment\_status, confirmation\_sent\_at
• sessions — id, event\_id, attendee\_a\_id, attendee\_b\_id, slot\_time
• connections — id, event\_id, requester\_id, target\_id, mutual (bool), unlocked\_at
• notifications — id, booking\_id, channel (email / SMS), type, scheduled\_at, sent\_at
• payments — id, booking\_id, amount, provider\_reference, status

---

Screens

• Home / Event Calendar — browse and filter all upcoming events; entry point for every session.
• Event Detail — full event info, attendee count, price, and the Book Now CTA.
• Checkout — payment form, booking summary, confirmation trigger.
• My Bookings — attendee's personal record of past and upcoming reservations.
• Attendee Profiles — anonymised profile cards for a specific event, unlocked 48 hours before.
• Post-Event Match Screen — select desired connections after the event; mutual unlocks fire automatically.
• Account Settings — manage profile, notification preferences, and contact details.

---

How to use this document

• Bring it into Mind Palace, where the guided platform and its AI coach use this spec as the starting point and build the product with you step by step.
• Hand it to a developer as the complete v1 brief — scope, data model, and screen list are all here.
• Keep it as the single source of truth while you build, so every decision stays anchored to what SwiftSeat is actually for.