Role
Product Designer
Prekindle
2026
Scope
Marketing dashboard
Responsive design
Visual direction
Where
Tickets sold on the platform
Layouts from desktop to mobile
From brief to design handoff
Prekindle is a US event ticketing and marketing platform. Its public website presented a strong, contemporary brand, while the dashboard used by event creators needed a clearer structure and updated visual direction.
I was brought in to redesign the marketing section: the hub where creators discover and access tools for advertising, messaging, event distribution, automation, and tracking.
The brief also included proposing visual and navigation patterns that could inform future updates elsewhere in the dashboard. The marketing hub became a practical starting point for bringing the product closer to the brand customers already knew.
I used Prekindle’s existing brand as the starting point for color, typography, and interface styling. The aim was to carry that identity into a working dashboard with clear hierarchy and consistent controls.
I organized the marketing tools into modules, each combining a recognizable label, a short explanation, and relevant actions. This gave the hub a repeatable structure while allowing different tools to present different information.
I designed the activation flows alongside the hub, covering the steps between discovering a tool and being ready to use it. These included explanatory dialogs, required inputs, consent, and approval states.
The work developed in two phases. The first established the hub and its module patterns; the second added the performance overview and embedded-events module. Across both phases, I adapted the layouts for five breakpoints while retaining the existing mobile navigation.
DECISION 5: Make activation requirements and status explicit
I gave each activation flow space to explain the tool and present the information required to proceed.
For advertising, the design included consent before activation. For email marketing, it included sender-email input and an account-approval state. These distinctions made the next step visible and explained when users needed to wait rather than take another action.
A. Two phases of scope
The first phase established the marketing hub and its module structure. The second added a performance overview and an embedded-events module, extending the same visual patterns.
B. Activation flows
Tool-specific dialogs covering product information, consent, required input, and approval status. The designs distinguish between starting activation, completing prerequisites, and waiting for an account to be approved.
C. Responsive system
Layouts across five breakpoints, adapting the performance overview, tool modules, and actions from desktop to mobile while preserving the existing mobile navigation.
Over three weeks, I delivered a redesigned marketing hub, its supporting activation flows, and responsive layouts across five breakpoints.
The design brought the section closer to Prekindle’s established brand and gave the team a concrete visual and navigation reference for future dashboard updates.
What I delivered:
A modular marketing hub covering the platform’s tool suite
A performance overview and embedded-events module
Activation dialogs with consent, input, and approval states
Responsive layouts across five breakpoints
A proposed visual and navigation direction for the wider dashboard
Designs prepared for handoff to the development team
J.R. Denson
CEO at Prekindle.com
Prekindle required improving a defined part of an established product while accounting for the patterns already in use. The existing brand provided a clear visual starting point, and the mobile navigation set a practical boundary for the redesign.
The project also showed how much of a tool’s experience happens before it opens. Descriptions, activation requirements, and approval states all help users understand what is available and how to get started.
Designing those details alongside the main dashboard made the work more complete. The result was a focused update with patterns the team could carry into subsequent product improvements.
Wider layouts placed related modules side by side. Narrower layouts stacked them into a single reading order, with adjustments to metric grouping, text wrapping, and controls. This defined the responsive behavior beyond a desktop and mobile endpoint.