BookNKhel

Sports venues across Pakistan had no shared discovery or booking layer — availability lived in phone calls and WhatsApp threads. BookNKhel needed a booking system that a venue owner with no technical background could self-onboard into, while still holding up under real-time availability and payment-adjacent flows on the customer side.

A NestJS/Prisma API backed by Supabase Postgres handles venues, bookings, and business accounts; Firebase covers auth and push notifications; Google Places API powers venue geolocation and search. The API is split across two Render environments — a staging service deploying from the `staging` branch, and a separate production service (`booknkhel-api-production`) deploying from `main` on its own database and secrets, so a bad staging deploy can never touch live bookings.

Zero commission for the first 10 businesses onboarding, paired with a fully self-serve business registration flow — venue owners register, list, and go live without anyone from the team touching their account. That go-to-market mechanic carries real architectural weight: registration state, listing verification, and venue-owner permissions all had to exist before a single booking could happen, not bolted on after.

A customer-facing app for browsing and booking venues, and a separate business portal for venue owners to manage listings, availability, and bookings from a dashboard.