MindPalaceX · The Workshop
The Idea Wall →

On the Idea Wall · ▲ 0 votes

PartyDock — the spec

PartyDock is a client portal where people planning events or parties can search for rentals and services, book instantly, and pay securely — all without manual intervention from the operator. Vendors control their own availability and fulfillment; customers get confirmed bookings and order tracking in one place. The platform is designed to run bookings end-to-end with zero human handholding.

---

Decisions locked

QuestionAnswer
Product shapeClient portal
Primary audiencePeople planning events or parties
Core loopVendor updates availability → customer searches and books → payment captured → vendor fulfills
v1 success metricBookings complete without operator involvement within 30 days of launch

---

The core loop

  1. Vendor onboards — sets service listings, prices, blackout dates, and cancellation/rescheduling rules via the vendor dashboard.
  2. Customer searches — filters by date, guest count, and party type to surface available listings in real time.
  3. Customer books — selects a listing, reviews the cancellation policy, and completes secure checkout; confirmation is issued instantly.
  4. Vendor fulfills — receives booking notification, tracks order status, and communicates with the customer through the platform messenger.
  5. Settlement — payment is released to the vendor according to the platform's payout schedule; cancellations trigger automatic policy enforcement.

---

v1 scope

Search by date, guest count, and party type
Filterable search surface on the customer-facing browse screen; queries against real-time availability so only bookable listings appear.

Real-time availability and instant booking confirmation
Listings reflect live calendar state; on checkout completion the system locks the slot and emails/SMS confirmation to both parties immediately.

Integrated payment and secure checkout
PCI-compliant payment flow on the booking screen; handles deposits, full payments, and automatic refund calculation on cancellation.

Cancellation and rescheduling policies
Vendors define their own rules (e.g., 48-hour free cancel, 50% refund within 7 days); policy is displayed at checkout and enforced programmatically — no manual processing.

Vendor messaging and order tracking
In-portal thread between customer and vendor tied to a specific booking; order status (confirmed, in-prep, fulfilled, cancelled) visible on both dashboards.

---

Deliberately later

  • Vendor profiles with photos and ratings — trust signals matter more once there is booking volume to display; launching without them keeps scope tight and avoids empty-state problems.
  • Party timeline and checklist builder — high value for retention and upsell, but adds planning-tool complexity that should not compete with proving the booking loop first.
  • Reviews and photos from past events — requires a base of completed bookings before the feature has content; build it when the data exists to populate it.

---

Data model sketch

  • users — id, name, email, phone, role (customer | vendor | admin), created_at
  • listings — id, vendor_id, title, party_type, max_guests, price, deposit_amount, description, status
  • availability — id, listing_id, date, is_blocked, booking_id (nullable)
  • bookings — id, customer_id, listing_id, event_date, guest_count, status, total_amount, deposit_paid, created_at
  • payments — id, booking_id, amount, type (deposit | balance | refund), provider_reference, status, processed_at
  • cancellation_policies — id, listing_id, hours_before_event, refund_percentage
  • messages — id, booking_id, sender_id, body, sent_at, read_at
  • notifications — id, user_id, channel (email | sms), template, payload, sent_at

---

Screens

  • Browse / Search — customer-facing listing discovery with date, guest count, and party type filters.
  • Listing Detail — full listing view showing availability calendar, pricing, and cancellation policy before checkout.
  • Checkout — secure payment capture, policy acknowledgement, and instant confirmation trigger.
  • Customer Dashboard — active and past bookings, order status, and message threads.
  • Vendor Dashboard — listing management, availability calendar, incoming bookings, order status controls, and payout summary.
  • Messaging — per-booking conversation thread accessible from both customer and vendor dashboards.
  • Admin Panel — user management, booking oversight, manual policy overrides, and platform payment reconciliation.

---

How to use this document

  • Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the portal with you step by step.
  • Hand it to a developer as the complete v1 brief — scope, data model, and screens are defined; nothing is left open.
  • Keep it as the single source of truth while you build, so every feature decision is measured against the one success metric: bookings happen without you touching them.

This is AJ's. Build yours.

A spec like this is step 3 of Mind Palace's nine — the other six take a weekend: working software, a real offer, first customers.

Want to build this with AJ?

Tell us who you are and we'll broker the introduction — their contact details stay private until they say yes.