Digivenue

Banquet operators in India run on WhatsApp, paper, and pressure. Inquiries get lost in chat threads. Vendor coordination happens five minutes before doors open. Payments arrive split between invoiced and non-invoiced amounts and someone has to do the GST math by hand. We were asked to replace the entire mess with one calm, mobile-first system the manager could actually use while standing in the hall.

• Inquiry CRM — fast-entry inquiries with a follow-up queue, source tracking, and one-tap WhatsApp actions. Nothing gets lost in chat anymore.
• Booking Operations — a readiness engine that scores every upcoming event against the things that should already be in place. Vendor visibility, escalation flags, and a single dashboard for the next 14 days of business.
• Event Command Center — the operational heart of the system. Five tabs (Overview, Finance, Vendor, Notes, Closure), a readiness score, an inline timeline engine, and a blockers list that surfaces what needs attention right now.
• GST Split Payment Calculator — practical kit for the real-world case where the client pays part of the booking with GST invoice and part in cash. 18% and 5% modes, inclusive/exclusive handling, automatic CGST + SGST breakdown, and one-tap copy-to-WhatsApp of the split.
• WhatsApp-native comms — OTP during booking, automated payment reminders, invoice and receipt delivery, vendor coordination, event-day update workflows. The manager never leaves the conversation.
• DigiStories — the storytelling layer. Event galleries, teaser videos, Instagram-ready stories and reels, and branded microsites for venue promotion.

The whole system is built phone-first because the people using it are walking the hall, not sitting at a desk. The Command Center loads enough to make a decision in under a second. Reminders go through WhatsApp because that’s where the conversation already lives. The GST calculator does the maths an accountant would otherwise do twice — once for the books, once for the client.

• Frontend — Next.js, React, Tailwind, shadcn/ui. PWA-first so it installs on the home screen and works offline when the venue WiFi inevitably drops.
• Backend — Supabase + Postgres. Row-level security keeps each venue’s data ringfenced.
• Comms — WhatsApp Cloud API for outbound, templated message flows for compliance.
• Architecture — modular by domain (Inquiry, Booking, Finance, Comms, Stories) so each can ship independently as the team adds capabilities.

• Stage 1 — MVP Core — authentication, inquiry CRM, bookings, payments, calendar.
• Stage 2 — Operations Layer — Command Center, readiness engine, vendor workflows, escalations.
• Stage 3 — Communication Layer — WhatsApp API integration, OTP, automated messaging.
• Stage 4 — DigiStories — gallery systems, story pages, reels and social content.

Digivenue stops being a CRM and starts being an operating system. The same manager who used to juggle five WhatsApp threads, three spreadsheets, and a paper diary now runs the entire event pipeline — from first inquiry to closure photo album — from a single phone.