Keerthana Sanjay
← Back
Nunify

Any event. Any scale.
Minutes to launch.

Event Management System

Company
Nunify
Platform
Desktop
Team
1 Product Designer
1 Product Manager
2 Developers
Outcome
+22% organisers
+66% events created

Summary

The features were great. The product was terrifying.

Nunify is an event tech platform for events of any type or size. Its product suite covers registration, the event app, check-in, networking, gamification, and exhibitor tools.

One of my initial tasks was to align the visual design with the branding, so my role was to collaborate with leadership and the design director to establish a cohesive visual strategy and design system.

While the existing features were great, the product was incredibly complex for new organisers, which affected the support and success teams as most organisers shepherded their work off to them.

With that, the core challenge was to simplify the UI while still allowing organisers to build their events and adopt all the great features they were scared to use.

Approach

This approach was guided by core principles: template-first design, supported by AI, and progressive disclosure to manage complexity seamlessly.

Template-first Supported by AI Progressive disclosure
Before & after. The reskin is the obvious part. Each screen knows its moment. This one: during the event.

The build

One decision instead of nine.

Replaced a blank nine-module setup screen with smart defaults based on event type — organisers now confirm one decision instead of making nine.
The idea was to keep it simple — no popups, no preview to approve. The AI builds in the canvas and explains its choices as it goes, so everything stays editable, same as anything built by hand.
The organiser sees what they're making instead of what they're configuring — which is the difference between publishing confidently and routing it to support.

Craft

One canvas, live preview, and constraints on purpose.

The old grid gave every feature equal weight, so nothing was the point of the app. Now the organiser promotes what the event needs onto the main tab and the rest collapses out of the way. Same prioritisation the attendee experiences on open.
The harder call was what to leave out: no per-element colour control. Organisers don't have time to style individual components, and letting them would break consistency across every app page. Theme is set once and holds everywhere.
Each widget leads with one number and the gap behind it — 4,316 no-shows is the signal, and the list of who didn't show is the part that matters.

Outcome

+22%

More organisers came on and created events.

+66%

Growth in total events created.

22% more organisers came on and created events, and total events created grew 66%. Before, organisers only used the app for the events they had to; now smaller events get one too, because it turns out a 60-person meetup is allowed to be fun.

Support stopped bracing for event day, which nobody put in a dashboard but everyone noticed.

Niche features like networking match and ticket access codes stopped being buried. Sales could bring them up in a pitch instead of saving them for the demo.

Reflection

This project showed me that capability alone isn't enough — it must be easy to use within busy workflows. Templates helped organisers start quickly instead of facing empty setups, even if they sometimes felt rigid or led to mistakes. This was especially useful for low-stakes events.

Let's make something worth using

Get in touch

work email linkedin resume