India's venue industry ran on Excel and phone calls. We built the operating system it never had.
Fewer Booking Conflicts
Conversion Efficiency
End-to-End System
Client
Boozno
Year
2024
Role
Product Strategy & Experience Design
Duration
Multi-phase
The Brief
01The Situation
Venue operations ran on memory. Inventory lived in people, not systems. Conflicts and missed leads were routine.
What We Did
An operating system replacing Excel, WhatsApp and phone calls — built around how venues actually work.
What Changed
A unified SaaS for inventory, inquiries, bookings and revenue. +18–25% conversion efficiency. 65% fewer booking conflicts.
What Drove It
02What the research showed, and the bets we made in response.
What We Found
Venues don't lose bookings for lack of space — they lose them because time-bound sub-venue availability is invisible. The model had to be built around slots, not 'the venue.'
It wasn't lead quality — it was response time. The sales manager who can't confirm instantly loses to one who can.
Multiple staff quote overlapping slots before anything is confirmed. The conflict surface had to live at inquiry creation.
The Bets We Made
Situation
Real venues operate as multiple bookable spaces — main hall, garden, terrace — not single units. Flattening this caused misbooking.
The Bet
Hierarchical inventory: every Venue contains Sub-venues with independent capacity, availability and pricing. Every interaction lives at the sub-venue level.
The Payoff
Eliminated the most common conflict class — overlapping bookings on multi-space venues treated as one unit.
Situation
Availability lived in three places at once — sales head, ops sheet, WhatsApp group. Never the same, never current.
The Bet
All time logic centralised. Inquiries, bookings, holds and blocks write to one calendar. No parallel tracking anywhere.
The Payoff
~65% fewer booking conflicts. Availability confirmed on the first call, from the inquiry screen.
Situation
Venue deals span days of negotiation. Instant booking forced certainty venues couldn't deliver — creating phantom holds.
The Bet
Request workflow with configurable expiry. Client confirms in time or the slot returns to availability.
The Payoff
Cut inventory lock-up from verbal holds. Gave sales a legitimate way to manage partial commitments.
The Structure
03Architecture defined before a single screen was drawn — structure shapes behaviour.
Information Architecture
Core Primitives
The Work
04Every screen below was driven by a research insight — here's the decision chain from problem to pixel.
Screen 01 / 04
Real venues operate as multiple bookable spaces — treating them as single units caused constant misbooking.
The Design Decision
Venue → Sub-venue model with independent capacity, availability and pricing for each bookable space.
Eliminated the most common conflict class — overlapping bookings on multi-space venues.
Screen 02 / 04
Availability lived in three disconnected places at once — never the same, never current.
The Design Decision
Inquiries, bookings, holds and blocks all write to one calendar. One source of truth for every availability answer.
~65% fewer booking conflicts. Availability confirmed on the first call, from the inquiry screen.
Screen 03 / 04
Sales running on memory and fragmented tools — qualification happened late, if at all.
The Design Decision
Qualification gated at entry — event type, date, guests, budget. Duplicate detection runs automatically.
Unqualified leads reduced. Sales staff spending less time on non-converting leads.
Screen 04 / 04
Revenue visibility required month-end manual compilation — venue owners were flying blind.
The Design Decision
Revenue lifecycle, occupancy, and team performance in one live view — no manual compilation required.
Real-time revenue visibility for venue owners for the first time. Month-end reconciliation eliminated.
The Outcome
01 / 04
18–25%
improvement in conversion efficiency
02 / 04
65%
reduction in booking conflicts
03 / 04
Visibility
operational visibility across venues and teams
04 / 04
Sales velocity
shorter sales cycles, improved response times
Bluemint understood our business before they touched the design. The system they shipped reflects how venues actually run — not how software typically forces them to.
Ankit Agrawal
Founder & CEO
Before We Go
06Key Learnings
Hospitality operations SaaS fails when the data model oversimplifies reality. In venue management, every abstraction away from how bookings actually work — sub-venues, time-bound slots, negotiated holds — becomes a workaround that operators run alongside the system, not inside it.
In venue and event operations, control and clarity outperform speed. Sales staff don't need a faster interface — they need certainty: that availability is accurate, that their actions are reversible, and that nothing slips between systems.
First-time enterprise software users in the hospitality industry need vocabulary alignment before feature simplicity. If the product's language doesn't match how venues talk about their own business, adoption fails regardless of interface polish.
Let’s Collaborate
We design the data model and operational primitives before touching the interface — so your product reflects how the business actually works, not how software expects it to.
Usually reply within 24 h
We take on a limited number of engagements at a time — enough to give each one the focus it deserves. If you're building in AI, fintech, enterprise SaaS, or GovTech and need a senior partner who can shape the strategy, design the experience, and help it ship — let's talk.
No commitment. No pitch deck. Just 30 minutes on your product. We respond within 24 hours.
India / Remote-first · Global partnerships
