← All workBalaji SankarCase study 08 / 12
Hospitality / venue booking2025-26

Ubox

Online booking for a private mini-theatre and celebration venue: hall browsing, time slots, add-ons and online checkout, backed by a NestJS API and a staff dashboard - later simplified and handed over cleanly.

Client

Ubox

Role

Technical lead; built the booking site and core booking flows

Timeline

2025-26

Stack
React 19TypeScriptViteTanStack RouterTailwind CSS v4shadcn/uiFramer MotionNestJSTypeORMPhonePeNetlify
Outcomes
~2 weeks

Focused build for the full stack

✦

Clean handover to an incoming team with documentation and a prioritised backlog

Thechallenge

A private screening venue hosting birthdays, anniversaries, proposals and small celebrations was taking every booking by phone and chat.

They wanted customers to browse halls, pick a slot, add decorations and extras and book online, with staff managing venues, pricing, bookings and payments from one dashboard.

How Iapproached it

01

A fast booking site

A single-page marketing and booking site with hall listings, a detailed booking card handling several slot types, capacity-aware pricing, occasions and add-ons, and separate desktop and mobile layouts.

02

Payments end to end

The first release took full bookings: live venue and slot data from the API, PhonePe checkout, and proper success and failure handling.

03

A dashboard for the front desk

I set up the admin dashboard and built venue management, the booking create flow, OTP login, the payment page and booking details, with my team building the NestJS API and the remaining admin screens.

04

Simplify, then hand over properly

When the business chose to manage availability by hand, the site moved to a lead-capture flow feeding the venue’s task board and calendar. I stripped the unused payment stack and dead dependencies and wrote a full handover guide with a prioritised backlog.

Highlightsworth showing

  • (01)

    One booking flow covering multiple slot behaviours, add-on pricing and validation on desktop and mobile.

  • (02)

    Full stack delivered in roughly two weeks of focused build by a small team.

  • (03)

    A backend covering venues, pricing and booking rules, discounts, invoices, front desk, WhatsApp notifications and OTP login.

  • (04)

    A handover a new team could pick up on day one: accounts checklist, environment reference, architecture notes and the old payment system preserved for reuse.

Have a project like this?

Tell me what you’re building or what’s broken. I’ll tell you straight whether I’m the right person for it.

Next caseE-commerce / seller tools / SaaS analytics2021Marketplace Analytics→