One marketplace for venues, vendors, negotiation, and event planning.
A multi-platform event marketplace built with NestJS, Flutter, and a web admin portal — cutting booking lead time 65%, lifting vendor onboarding 2.4×, and making 90% of admin operations fully self-serve.
Event booking was a coordination nightmare.
Organizers hunted venues across disconnected sites and negotiated pricing on phone and WhatsApp. Operators ran catalogs on spreadsheets — and booking never connected to planning.
No centralised discovery
Venues, caterers, photographers, and décor required separate research across disconnected directories.
Opaque negotiated pricing
Quotes lived in calls and chats with no digital record or structured approval path.
No booking visibility
Organizers could not see pending vs. confirmed status without constant follow-up.
No enterprise ops layer
Multi-location operators lacked a system for catalogs, teams, and booking pipelines.
Client
Leading event marketplace
Industry
Events & hospitality
Integrations
NestJS · Flutter · Push · Cloud
Engagement
Full marketplace delivery
What we learned before we designed anything
Findings from organizers and multi-location operators — the basis for every discovery, negotiation, and multi-tenant decision that followed.
Research is the biggest time sink
Comparing venues and vendors across disconnected websites consumed organizer calendars.
Informal pricing creates disputes
Phone and WhatsApp agreements left no reliable record of what was accepted.
Operators need pipeline visibility
Multi-location teams could not see bookings across venues from one system.
Booking and planning must connect
Guests, tasks, and budgets lived apart from the venue reservation.
Mobile location awareness was missing
On-the-go organizers had no distance-aware discovery without manual map searching.
Listings without negotiation
Most venue platforms still pushed pricing off-platform into calls and chat.
Uneven two-sided tooling
Few products served organizers and operators with equally strong purpose-built surfaces.
Planning tools disconnected
Guest lists, budgets, and tasks lived in separate products from venue booking.
Aditi
Event Organizer · Corporate Events
Goals
- • Compare venues by location and price
- • Negotiate pricing transparently
- • Track bookings and plan events in one place
Pain Points
- • Research across dozens of sites
- • No digital pricing record
- • No visibility into request status
Flutter for organizers, admin for operators, one NestJS API.
Discovery, offer negotiation, booking lifecycle, and event planning share a multi-tenant backend so consumer and enterprise experiences stay in parity.
Marketplace, negotiation, and planning in one platform.
Organizer and operator experiences are primary products — not afterthoughts — on a shared booking state machine.
No centralised way to discover venues and vendors by location, category, or price.
Geo-aware marketplace browsing
- ✓Venues, caterers, photographers, and décor in one searchable catalog
- ✓Flutter GPS sorting with rich galleries, ratings, and distance-aware results
Pricing negotiation happened offline with no record or structure.
Structured negotiation with audit trail
- ✓Requests, counter-offers, and accept/decline handled entirely in-platform
- ✓Defined booking states with push notifications on every change
Multi-location operators had no system for catalogs, teams, or bookings.
Multi-tenant self-serve operations
- ✓Independent catalogs, teams, and pipelines on shared infrastructure
- ✓Dynamic listing forms and content management without developer involvement
Booking and event planning lived in completely disconnected tools.
Guests, tasks, and budget on the booking
- ✓Event coordination tied directly to the venue reservation
- ✓Category-specific dynamic listings without custom builds per venue type
Built for two-sided event marketplace scale.
NestJS, Flutter, JWT/RBAC, and cloud CI/CD chosen so multi-tenant operators and mobile organizers share one reliable booking core.
Booking lifecycle first, then dual-platform parity.
The pending → offer → confirmed → completed state machine was designed before discovery and planning features layered on.
Discovery
Mapped organizer and operator journeys from first browse to post-booking coordination.
Booking lifecycle first
Designed the defined state machine as the core domain every feature depends on.
Dual-platform parity
Built Flutter mobile and web admin against the same NestJS API.
Multi-tenant ops
Implemented role-based data scoping for independent enterprise catalogs.
Launch & ownership
Deployed with CI/CD and ongoing platform ownership for marketplace growth.
What organizers and operators use every day
What changed after launch
65% shorter booking lead time - Discovery to confirmation accelerated across the marketplace.
2.4× vendor onboarding uplift - Onboarding rate rose in the first quarter post-launch.
8 touchpoints eliminated per booking - Manual coordination steps removed from the typical booking path.
100% in-platform pricing decisions - Offers and booking decisions moved inside the platform — zero offline coordination.
12 enterprise tenants live - Independent catalogs running on a single shared deployment.
90% self-serve admin ops - New venue categories and content updates require zero developer interventions.
Challenges & Learnings
Two primary audiences
Organizer app and operator portal both needed equal investment as products.
Dynamic listing flexibility
Banquet halls and cricket grounds shared one configurable form system.
Negotiation state complexity
Expired offers and multiple rounds required disciplined state machine design.
Multi-tenant isolation
API-level scoping prevented cross-operator data leaks on shared infrastructure.
Real-time sync
Booking status had to stay consistent instantly across mobile and web.
Where the platform goes from here
WhizCloud didn't just build us a booking tool — they built us a marketplace. The admin portal means our team manages the entire platform independently. The mobile app our customers use actually converts.
“That combination is rare — a marketplace where both organizer experience and operator control are genuinely strong.”