How event work is won in India
One event, several functions, many decision-makers
An Indian wedding is not a booking, it is a programme. Mehendi, haldi, sangeet, the wedding itself and a reception each have their own date, venue, headcount, decor scope and vendor set. The client is rarely one person either: the couple has a view, the parents hold the budget, and an uncle or family friend usually leads the negotiation. Quotes are revised repeatedly as the guest list moves.
A pipeline that models this as a single deal with a single contact loses the plot within a week. The event needs linked functions and a stakeholder map, or the team ends up rebuilding context in every conversation.
Everything arrives on WhatsApp, and most of it at night
Enquiries come from wedding marketplaces, Instagram, venue and caterer referrals and word of mouth, and they all migrate to WhatsApp within a message or two. Reference images, venue photos, guest counts and price negotiations happen there. When those threads live on individual coordinators' phones, a resignation in October costs the company a season.
Money moves in advances, and the season is short
Payment is staged: a booking advance, milestones as vendors are confirmed, and a balance due before the function. Corporate clients deduct tax at source, so the amount received rarely matches the invoice. Meanwhile the wedding window from November to February compresses most of the year's revenue into a few weeks, which is exactly when a manual process fails.