A polished reservation product connecting players and venue managers through discovery, availability, approval workflows, calendars, team spaces, and operational dashboards.
My role
Product engineer
Scope
Complete product flows · Active development
In development · Responsive player and venue-manager journeys with connected booking state.
I designed and built Pitchly as a complete two-sided football-pitch reservation product. Players discover venues, choose slots, manage bookings, and coordinate a team; venue managers review the same requests, control schedules, inspect revenue signals, and maintain venue information. The connected product model is ready for production identity, payments, concurrency, and booking services.
Search, filters, favorites, list and map views, amenities, formats, ratings, distance, and pricing.
Reservation Workflow
Date, time, duration, note, price, confirmation, cancellation, and status-aware booking details.
Team Space
Roster, captain status, join code, invitations, next match, and team performance context.
02Shared1 capabilities
Calendar & Notifications
Month and week schedule views connect booking changes to visible player and manager follow-up.
03Manager2 capabilities
Approval Queue
Venue staff review the same pending requests and can approve or decline them from focused operational views.
Venue Operations
KPIs, revenue signals, occupancy, schedule, venue settings, hours, and availability support the supply side.
03 /System design
How the pieces connect.
System workflow
A reservation seen from both sides.
Player and manager views share persistent product state. Production payments, identity, and concurrency guarantees are outside the current demo boundary.
Documented project flow
Player
Discover & requestChoose a venue and slot; manage team and bookings
Shared reservation
Booking domain
Lifecycle statePending, confirmed, declined, completed, or cancelled
Review & update
Venue manager
Schedule & approvalsReview requests and maintain venue availability
01One Product, Two Operational Perspectives
A shared booking domain powers player and manager journeys. Direct role entry and persistent state let approvals and cancellations carry between both views while production services are integrated.
Player workspace
Discovery, booking, calendar, booking history, and team coordination.
Shared state
Venue and reservation records with explicit lifecycle status.
Manager workspace
Requests, schedule, operational overview, and venue maintenance.
04 /In action
A closer look at the build.
Actual project screens and documented visuals. Open any image for the full view.
