EventEase
A communication-first operations platform for Indian event agencies.
What is EventEase?
EventEase is an operations platform for Indian event management agencies. The idea is to replace the WhatsApp groups, email chains, and spreadsheets that currently hold everything together, with a single workspace where communication is at the centre, everything is scoped to specific events, and nothing gets lost. It's not a database you update after the work is done. It's where the work actually happens.
Who uses it?
Four operator types. One platform.
Sets up every event, builds channel clusters, invites vendors, creates parent forms, reviews dashboards, and sends broadcasts. Sees everything across all events simultaneously.
Owns a specific event end-to-end. Creates channels, assigns tasks, manages vendors, and tracks every stage of the run-of-show for their events.
Executes in their designated area. Sees the channels and tasks relevant to their role, without the noise of the wider organisation or other events.
Sees event portfolio status and key flags, without access to operational detail. A read-only view calibrated for oversight, not execution.
The Problem
The operational backbone of India's event industry is WhatsApp.
India's MICE sector generated ₹4,16,217 crore in 2024 and is projected to reach ₹8,73,559 crore by 2030. Despite that scale, most agencies are still coordinating through WhatsApp groups, email threads, and spreadsheets. There's no purpose-built software for how they actually operate. The failures this causes aren't rare. They happen at exactly the wrong times.
Vendors receive conflicting information because the briefing exists in too many places. One version is in email, another in WhatsApp, a third in the spreadsheet. Nobody knows which one is current.
A decision made in a WhatsApp conversation at 11pm is gone by morning. There's no record layer, so institutional knowledge lives on individual phones. If that person leaves, it goes with them.
The same information gets entered twice by two different people in two different places. That's two chances for versions to go out of sync. This isn't a discipline problem. It's a design problem.
Cvent is built for North American corporate buyers and is too expensive and generic for Indian agencies. Indian platforms mostly focus on ticketing. There's nothing designed for the internal operations of an Indian event agency.
Stakeholder Interviews
Four people. Four different insights.
“We run three events a month. Everything lives in my WhatsApp. When I leave the agency, the entire operational history of the last five years leaves with me.”
“I send the same update to the AV vendor on WhatsApp, then paste it into the ops sheet, then email the client. Three times. Every time something changes.”
“On event day I am in 40 WhatsApp groups. I have no way to know which ones need a response right now and which ones are just noise.”
“The vendor confirmed the load-in time with me on call. I updated my sheet. Nobody told the site manager. The truck arrived and there was nobody to receive it.”
Stakeholder Mapping
Nine primary categories. Twelve agency roles.
Nine primary stakeholder categories were identified across the Indian event ecosystem. Within the agency team alone, twelve distinct management roles were mapped. The key insight: the agency isn't just a service provider. It's the information router for an entire temporary multi-organisational network.
Corporate clients, government bodies, and institutions that commission the event and set the strategic brief.
The event management agency, the central information router for the entire temporary multi-org network.
Specialised agency leads across production, creative, client servicing, logistics, budget, and security.
Brands funding or co-presenting the event in exchange for visibility, data, or activation rights.
On-ground crew and internal staff executing the run-of-show across all departments simultaneously.
AV, décor, catering, transport, and technical service providers. Each engaged per event, not permanently.
Speakers, performers, and facilitators delivering the content of the event. Often externally coordinated.
Delegates, guests, and public participants. The primary audience for whom the event is produced.
Brands with a physical or digital presence at the event; managed separately from sponsors.
Ecosystem Mapping
Twelve simultaneous information flows.
The ecosystem map tracked four types of flows between the agency and everyone around it: goods, services, information, and money. We identified twelve distinct simultaneous information flows. When any of those break down, the result is a communication failure. Not a process problem, not a people problem.
Event Process Map
Five parallel workstreams. One WhatsApp group.
We traced the full event lifecycle across every party involved, from the corporate client and agency teams to sponsors, vendors, government bodies, and the venue. An agency is managing at least five distinct workstreams at the same time, with no clear way to know which messages need action, which are just informational, and which are already resolved.
Competitive Analysis
No platform inverts the model.
We looked at seven existing platforms. Lennd comes closest, describing itself as “a communications tool at its core,” but it's portal-based. Each vendor gets a separate website to log into, not a shared channel. No platform we found actually makes communication the core organising principle.
Database product. Communication is a notification layer on top of a project management core. Built for North American corporate buyers.
Closest competitor. Describes itself as 'a communications tool at its core.' But portal-based (each vendor gets a website), not channel-based real-time coordination.
Attendee experience platform. No internal agency coordination layer exists.
WhatsApp integration as outbound broadcast only: attendee notifications, not structured vendor coordination.
Indian-market ticketing and attendee registration. No operational or vendor layer.
Badge and registration focus. Communication entirely absent from the product.
Streaming and ticketing. Built for the public-facing event experience, not internal production operations.
Gap Closure Strategy
Nine market failures. Nine design responses.
Nine structural failures in the current market were each matched with a corresponding platform design response. Every EventEase design decision traces back to one of these nine gaps.
Research Takeaways
Everything works well, but they centre around the wrong thing
The research followed four methods, each building on the last. Stakeholder mapping helped us understand who was involved and what they each needed. Ecosystem mapping showed how information actually moved between them. A process map pinpointed where coordination was breaking down in practice. Competitive analysis confirmed that none of the existing platforms had addressed these gaps. From there, each structural failure became a direct design requirement.
Interactive Prototype
The Agency-side UX Prototype.
The prototype implements the complete agency-side information architecture: six operational modules with live mock data, the full channel workspace (Overview, Events, Channel Chat, DMs, Broadcast), and all role-specific views.
Design Thesis
Communication is the operating system.
The research pointed to one clear principle: communication should be the core, not a layer on top. Every operational object, whether it's a task, form, document, or approval, should be accessible from within a channel. If a team member has to leave the platform to coordinate something, the platform has failed at its job.
“Communication is the operating system of event management. Every other tool (forms, tasks, approvals, documents, budgets) is a layer on top of communication, not the other way around.”
Everything in EventEase lives inside a channel. Tasks, forms, documents, vendor relationships, all of it. A channel isn't just a place to chat. It's the operational unit the whole platform is built around.
Every channel, form, task, and conversation is tied to a specific event. An Infosys Summit thread can't accidentally show up in a Wipro Retreat view. The scoping is structural, not something you have to configure.
No entering the same information twice. A vendor fills out their side of a form, the agency sees the output on their side. Both are looking at different views of the same underlying record.
A vendor's view should feel complete for their needs, not like they're looking at a restricted version of something bigger. If the interface communicates 'limited access', that's a design failure. The tunnelled view should feel like its own product.
Indian vendors use WhatsApp. That's not a problem to fix. It's a constraint to design around, by making WhatsApp a structured broadcast fallback within the platform's communication layer.
Information Architecture
Three layers. One coherent system.
The information architecture is organised in three layers. The global navigation has three main destinations: Overview (all active events plus an activity feed), Events (the directory of events with individual dashboards), and DMs (direct messages and group conversations). Within each event, channels are split into three structural zones. Operational modules are accessed from the event dashboard. Each layer maps to one zone, so the structure is learnable and there's no overlap.
Mandatory and department channels that form the workspace backbone. These never archive. Role-gated: dept-finance is locked to Finance only.
- #company-general (locked)
- #company-wins
- #company-random
- #dept-operations
- #dept-production
- #dept-marketing
- #dept-finance (locked)
- #dept-logistics
A dedicated channel cluster per event, archived T+14 days after closure. Contains internal channels plus external-facing channels for each vendor, sponsor, client, and venue.
- #[event]-general
- #[event]-ops
- #[event]-production
- #[event]-marketing
- #[event]-finance (locked)
- #[event]-logistics
- #[event]-vendor-[name]
- △ [event]-alerts
Direct messages and saved content. Individual and private, belongs to the person not the project. Context-tagged by role, company, and event to solve the Slack identity problem.
- DMs (1:1)
- Group DMs
- Saved items
System Architecture
Who can see what. Precisely.
A vendor reading through their view from top to bottom sees exactly what they need: their channel, assigned assets, and the forms they're responsible for. Nothing else is visible. That's the tunnelled view in practice.
The initial brainstorm got to 200 potential tools across 17 modules and 6 clusters. We brought that down to 47 buildable components by identifying the seven core engines behind most of them: Communication, Forms, Task, Permission, Data Sync, Notification, and Analytics. Most features are just one of these engines applied to a specific part of the operation.
Module: Credentials
Configuration to on-site issuance.
Manages the full credential lifecycle from tier definition through on-site pickup in one place. Credential tiers (Gold, Silver, Classic) are configured once and referenced across distribution, monitoring, and fulfilment.
Define credential tiers with associated perks, colour codes, and access permissions. The configuration step is deliberately separated: changes here propagate to all downstream tabs without re-entry.
Staff and vendor credential distribution table. Each row shows name, role, tier, channel, and pickup status. Bulk actions available at the distribution stage.
Live pickup tracking against issued count. Waitlist management: guests can be promoted from waitlist to confirmed tier if a slot opens.
Sync status log and fulfilment confirmation. Shows gaps between what was issued and what was collected, with timestamp records.
Module: Guest Lists
RSVP to check-in in one module.
Tracks every attendee from invitation through on-day arrival. The guest table is the single record. RSVP status, dietary requirements, tier assignment, and check-in confirmation all live here, updated by the relevant team at each stage.
Full guest table with tier badges, dietary flags, and RSVP status. Sortable and filterable. A guest's record is created once and updated as the event approaches.
Waitlisted guests with position number and a one-action promotion flow. When a confirmed guest cancels, the next waitlisted guest is promoted and notified.
On-day scanner interface. QR-based or manual search. Marks guests as arrived in real time, visible to all team members with module access.
Download final guest list as CSV or PDF for venue ops, security, and administrative reconciliation.
Module: Assets & Equipment
Load-in to bill-back.
Tracks every physical asset across the event, from AV rigs to badge printers, with load-in and load-out schedules, vendor assignment, and status lifecycle. The load-in schedule view surfaces the asset timeline at a glance, preventing the common failure of assets arriving without a receiving point.
Tracker view with stat cards (Total / Confirmed / Pending / Draft). Each asset has a category, zone, vendor, load-in time, load-out time, and a status pill that cycles through Draft → Pending → Confirmed on click. A timeline view groups assets by load-in slot.
Distribution assignment and post-event bill-back reporting. Maps each asset to its usage zone and responsible team for reconciliation against vendor invoices.
Module: Forms & Tasks
Eliminating double-entry.
The most complex module, and the one that makes EventEase fundamentally different from all existing platforms. Forms are not data collection tools bolted onto a project management core. They are the connective tissue between vendor internal work and agency milestone tracking. A vendor completes their child form stage; the system automatically fires the corresponding parent form stage on the agency side. One action. One place. Both parties updated.
Pipeline list showing all active forms per event (Vendor Onboarding, Stage Tech Brief, etc.). Each pipeline shows stage count, last activity, and status. Clicking a pipeline opens the stage rail: Draft → Sent → Submitted → Reviewed → Approved. Submitting a stage auto-creates a linked Task.
Task rows with title, assignee, priority, due date, status, and tags. Full create/edit drawer with linked form field, description, and activity log.
Five columns: To Do · In Progress · In Review · Done · Blocked. Draggable cards with priority colour coding. Kanban state reflects form pipeline submissions in real time.
Timeline bars per task, grouped by assignee. Shows overlap, slack, and critical path at a glance without configuration.
Live computed views: status distribution bar chart, workload per assignee (assigned vs done), form linkage grouping, velocity, and burndown.
Module: Communications
The channel is the product.
Not a module added to the platform. It's the layer everything else surfaces through. Every operational object (task, form, document) is accessed from within a channel. Communication isn't a feature of EventEase. EventEase is a communication platform with operational depth.
Three-column layout: sidebar, chat, right panel. Right panel tabs: Overview, Members, Pinned Docs, Forms, Tasks. Messages support rich text, file attachments, poll cards, and system notices. Channels are event-scoped with no global feed.
One-to-many announcements with optional acknowledgement requirement. Sent tab shows real-time ack status per recipient. Unacknowledged after 30 min: Tier 1 reminder to recipient. After 60 min: sender notified of non-acknowledgers by name. On event day: thresholds compress to 10/20 min.
Filterable by Internal / External / Clients / Vendors. Every contact row shows role, company, and event, solving the Slack identity problem where DMs from unfamiliar names have no context.
“A channel without context is just another WhatsApp group.”