Prd

court-booking · discovery
discovery

Product Requirements Document: Court Booking Solution

Date: 2026-02-10
Version: 1.0 (Discovery)
Product: Court Booking Solution
Phase: Discovery → Design

Document Purpose

This PRD defines three implementation options for the Court Booking Solution, ranging from lean MVP to full-featured platform. Each option balances time-to-market, development cost, feature richness, and market validation needs.

Product Vision

For players: Book your court in 60 seconds, find opponents, and track your games — all in one app.

For venue owners: Automate bookings, increase utilization, reduce no-shows, and build customer loyalty — without hiring more staff.

Success Metrics

North Star Metric:

Monthly Gross Merchandise Value (GMV) — Total value of bookings processed

Supporting Metrics:

Player-side:

Venue-side:

Platform:

Three Implementation Options

Criteria Option 1: Lean MVP Option 2: Standard Option 3: Full-Featured
Timeline 6-8 weeks 12-16 weeks 20-24 weeks
Dev Cost ₱400-600K ₱1-1.5M ₱2-3M
Team Size 2 devs + 1 designer 3 devs + 1 designer + 1 PM 4 devs + 2 designers + 1 PM + 1 QA
Features Core booking only + Community basics + Full social, AI matching
Go-to-Market 5-10 venues (NCR) 20-30 venues (NCR) 50+ venues (NCR + Cebu)
Risk High (unproven) Medium (validated MVP) Low (proven concept)

Option 1: Lean MVP (Validate Core Hypothesis)

Goal: Prove that players and venues will adopt digital booking over Messenger/phone. Validate willingness to pay.

Timeline: 6-8 weeks
Budget: ₱400-600K
Launch Strategy: Invite-only beta, 5-10 anchor venues

P0 Features (Must-Have)

Player-Facing (Mobile Web)

1. Discovery

2. Real-Time Availability

3. Booking Flow

4. My Bookings

5. Notifications

Venue Owner Dashboard (Web)

1. Calendar Management

2. Booking Management

3. Venue Settings

4. Payouts

5. Basic Analytics

P1 Features (Nice-to-Have, post-MVP)

P2 Features (Future)

Technical Architecture (MVP)

Stack:

Key Collections (Firestore):

venues/{venueId}
  - name, location, courts[], pricing, policies

bookings/{bookingId}
  - venueId, courtId, playerId, slot, status, payment

players/{playerId}
  - name, email, phone, bookingHistory[]

payouts/{payoutId}
  - venueId, amount, status, transactions[]

Open Questions (MVP)

  1. Cancellation policy: Standard 24h refund? Or venue-specific?
  2. Payment flow: Pre-pay 100% or deposit (50%) + balance on arrival?
  3. No-show penalty: Charge no-show fee? Ban after X no-shows?
  4. Venue onboarding: Self-serve or assisted (we do initial setup)?
  5. Commission split: 5% player + 7% venue = 12% total?
  6. Minimum booking: 1 hour? Or 30-min slots allowed?

Option 2: Standard (Validated MVP + Community Features)

Goal: Launch with validated core + basic community features (find-a-player, reviews). Build defensibility via social graph.

Timeline: 12-16 weeks
Budget: ₱1-1.5M
Launch Strategy: Public launch, 20-30 venues, paid marketing (₱100K budget)

P0 Features (All MVP + Below)

Additional Player Features

6. Find-a-Player

7. Reviews & Ratings

8. Player Profile

9. Group Booking

Additional Venue Features

10. Marketing Tools

11. Customer Management

12. Enhanced Analytics

P1 Features (Post-launch)

P2 Features (Future)

Technical Additions

New collections:

players/{playerId}/friends/{friendId}
players/{playerId}/reviews/{reviewId}
lfp_posts/{postId}  // looking-for-player posts
conversations/{conversationId}/messages/{messageId}

Integrations:

Open Questions (Standard)

  1. Skill verification: Self-reported or validated somehow?
  2. Messaging moderation: How to prevent spam/abuse?
  3. Friend matching algorithm: Prioritize friends-of-friends?
  4. Review moderation: Manual review or auto-publish?
  5. Off-peak pricing: Venue-controlled or platform-suggested?

Option 3: Full-Featured (Complete Platform)

Goal: Launch category-defining platform with AI matching, native apps, full venue automation, and tournament/league features.

Timeline: 20-24 weeks
Budget: ₱2-3M
Launch Strategy: Major launch, 50+ venues, PR campaign, influencer partnerships

P0 Features (All Standard + Below)

Advanced Player Features

13. AI-Powered Matching

14. Performance Tracking

15. Digital Queue (Walk-ins)

16. Social Features

17. Native Mobile App

Advanced Venue Features

18. Equipment & Rentals

19. F&B/Locker Integration

20. Tournament Management

21. Membership Plans

22. Staff Management

23. Advanced Analytics

P1 Features (Post-launch)

P2 Features (Future)

Technical Additions

Advanced features:

New collections:

tournaments/{tournamentId}
leagues/{leagueId}
challenges/{challengeId}
inventory/{venueId}/items/{itemId}
memberships/{membershipId}
staff/{venueId}/users/{userId}

Open Questions (Full-Featured)

  1. AI matching: What data points to train on? Privacy concerns?
  2. Tournament liability: Insurance if player injury during tournament?
  3. Equipment tracking: RFID tags or manual?
  4. Membership vs. pay-per-use: Can users mix both?
  5. Staff payroll: Integrate payroll or just scheduling?
  6. IoT security: How to secure smart locks?

Comparison Summary

Feature Category Lean MVP Standard Full-Featured
Core booking ✅ ✅ ✅
Real-time availability ✅ ✅ ✅
Payments (SymphPay) ✅ ✅ ✅
Basic venue dashboard ✅ ✅ ✅
Find-a-player ❌ ✅ ✅
Reviews/ratings ❌ ✅ ✅
Group booking ❌ ✅ ✅
Off-peak pricing ❌ ✅ ✅
Digital queue ❌ ❌ ✅
AI matching ❌ ❌ ✅
Performance tracking ❌ ❌ ✅
Native mobile app ❌ ❌ ✅
Equipment rentals ❌ ❌ ✅
Tournaments ❌ ❌ ✅
Membership plans ❌ ❌ ✅

Recommended Approach: Phased Rollout

Phase 1: Lean MVP (Weeks 1-8)

Phase 2: Standard (Weeks 9-16)

Phase 3: Full-Featured (Weeks 17-24)

Risk Mitigation

Risk Impact Probability Mitigation
Venues resist change High Medium Free trial, white-label option, hands-on onboarding
Players don't see value High Medium Price parity with Messenger (convenience is free), refer-a-friend incentives
Payment fraud Medium Low SymphPay fraud detection, ID verification for high-value bookings
Technical debt (scaling) Medium Medium Firebase scales automatically, modular architecture for refactor
Competitor enters market Medium Medium Move fast, lock in anchor venues, build community moat

Next Steps

  1. Stakeholder review: Choose option (recommend: Lean MVP → Standard)
  2. User research: Interview 10 venue owners, 20 players
  3. Design phase: Wireframes, high-fidelity mockups
  4. Technical spec: Detailed architecture, API design
  5. Pilot recruitment: Identify 5 anchor venues for beta

Document Owner: Discovery Agent
Last Updated: 2026-02-10
Status: Awaiting stakeholder review