BookWedGo is a marketplace ecosystem that helps families across Tamil Nadu find and book marriage halls, mandapams, banquet halls and resorts. Behind the public site sit seven client apps (roughly 260 to 300 screens), more than 900 API endpoints, three backends and 25 integrations. Sakthi Vignesh worked on it as a Full Stack Developer at Hyperready Technology, including the public website, admin panel, vendor portal and CRM. It is live at bookwedgo.com.
This is client work done through an employer, not a Vantaverse product, so treat this as an account of what such a system looks like from the inside.
What are the seven apps?
The client apps include:
- An admin CMS
- An agent portal
- Vendor web and mobile apps
- The BWG CRM, used for telecalling
- The KAD app, used for field sales
Integrations include Razorpay, BillDesk, AWS S3, Firebase, Google Maps, WhatsApp, Exotel and Convox. The front ends are built with React 18, TypeScript, Vite, TanStack Router and Query, Redux Toolkit and Mantine, with Socket.IO for real-time features on Node.js.
How does an enquiry become a booking?
An enquiry arrives from the website and goes to a telecaller. If it needs more, it escalates, then a field visit happens, then it ends in a confirmed booking and a commission. Three different venue-onboarding routes all converge on one approval flow, so the marketplace sees every venue the same way no matter how it joined.
What is inside the BWG CRM?
The CRM has 16 modules and 7 roles, real-time Socket.IO alerts and AI call-quality and lead-analysis reports. That last piece, using AI to review calls and score leads rather than to chat with customers, is a useful reminder that "AI in the product" is often an analysis feature, not a chat window.
What do the numbers teach?
- Roles multiply complexity. Seven apps and seven CRM roles mean permissions touch nearly every feature. Design who can see and do what before building the screens.
- Converge early. Three onboarding routes into one approval flow is cheaper to maintain than three parallel systems.
- Integrations are product decisions. Payments, calling and messaging each have failure modes the user sees. Plan for them to fail.
- The business process is the spec. The enquiry-to-commission flow defined the screens, not the other way round.
Vantaverse's Take
This is the experience behind our full-stack development work: scoping starts with the operational flow, not a screen list. It also fed the next project: DeepSpot, an AI text-to-SQL product, began as the analytics layer for this ecosystem. The customer-conversation side is the same problem we address with WhatsApp AI agents. For how AI is changing this kind of build, see AI-assisted web development in 2026.