Skip to content
All work

Sweap · Founding designer · 3 min read

From 60+ minutes to 9: rebuilding how teams create events at Sweap

Sweap was powerful once customers learned it, but getting started depended on demos and hands-on training. As its founding product designer, I used a rebrand to rethink how new customers navigate and create events, from finding their way through the product to a wizard that prepares every page and email. Core setup fell from over an hour to 9 minutes, and the first customers completed setup without assisted onboarding.

  • Event platform
  • No-code builder
  • Design system
  • 60+ → 9 min

    To set up an event

  • −30%

    Time from design to build

  • 103% → 119%

    Net dollar retention, company-wide

A MacBook displaying the Sweap no-code registration-site builder
The registration-site builder. Real product, one part of a wider transformation.

New customers couldn't find where to start

Sweap sold through demos and hands-on training. Trained customers became experts, but newcomers got lost in navigation and dense tables built for people who already knew the product. I used the rebrand to reorganise menus, headers and pages around the work people came to do, replace tables with card views a new user could scan, and shorten the path to each persona's aha moment.

What I worked on across the product EVENT CREATION Event creation one guided flow instead of a blank form Event series a variation of the same flow Online events a variation of the same flow REGISTRATION AND GUESTS Registration sites no-code builder for branded sites Templates starting points for new events Guest management guest lists and segments Communications invitations and emails ON SITE AND FOUNDATIONS Check-in on-site check-in and devices Design system tokens and components Design process one specification per feature Blue outline: restructured or built new. The rest adopted the shared system as it was touched.
What I worked on. Outlined: restructured or built new.

DecisionI restructured navigation and page layouts instead of simply applying the new brand, accepting disruption for existing customers to make the product easier to learn.

One event meant styling every page and email by hand

An event runs on a series of pages and emails: invitation, registration confirmation, reminder, thank you for attending. Each was set up and styled on its own. I designed one setup wizard: event type, event data and branding go in once, and every page module and email comes out prefilled and styled. I also designed and coded a new email template, the best performing Sweap had sent.

Before: each page and email was set up and styled on its own.

DecisionI focused on getting organisers to a nearly complete event in one flow, rather than making every page and email easier to configure separately.

OutcomeCore setup fell from over an hour to 9 minutes, including finding the logo and event details; pages and emails came prefilled, with only copy left to adjust.

Organisers needed to see the site they were building

A registration site was a long, static form you clicked through, with no view of the result. I turned it into a modular builder: pages made of modules you add, reorder and style while seeing the site as you work.

Section structure and live canvas
Structure and live canvas: the hierarchy stays visible while editing.
Module library with previews
The module library, with previews after testing showed names alone weren't enough.
Global styling
Global styling: the event's logo, type and colours flow into every module.
DecisionI made modules appear with preview content and the event's branding rather than empty, so organisers could recognise and edit what they'd added. Why →

Testing revealed three problems: users couldn't find how to add a module, couldn't recognise modules from their names, and couldn't see the empty modules they'd added. We made adding modules easier to discover, added previews, and filled modules with content styled from the event's logo, type and colours.

OutcomeOrganisers could build and edit branded registration sites directly, without needing support to make those changes.

The team needed one way to keep the product consistent

Inconsistent components and scattered specifications made the product harder to maintain and left engineering resolving design questions during build. I rebuilt the interface on semantic tokens and shared components, and introduced one feature specification that product, design and engineering work from, with Jira tasks linked to its decisions. It later became the onboarding framework for new design contributors.

Three systems had to grow together THREE SYSTEMS Product system shared event concepts and flows instead of independent mini-products Interface system tokens, components and page patterns used across the application Delivery system one repeatable process from product definition to development Systems thinking is not a component library: the product model and the process had to scale as much as the UI.
The same token layer later gave the product dark mode without a second component set.
DecisionI migrated the system area by area rather than relaunching everything, accepting temporary inconsistency so the team could keep shipping. Why →

Engineering first had to refactor parts of the styling layer. A single relaunch would have concentrated the risk; events and guests moved first as the most used, then registration, communication and check-in.

DecisionI moved decisions into a shared specification before implementation, accepting more upfront work to reduce rework during build.

OutcomeFeatures went from design to build 30% faster, with fewer rounds of fixes after build: typically 0–1 instead of 2–3.

Business contextTowards the end of my time at Sweap, the founder reported net dollar retention rising from 103% to 119%, engagement growth of 16% and ARR growth of 26% over one year. These were company-wide results with several drivers, not outcomes I attribute to design alone.

Recommendation

I really liked that he built prototypes for us internally to understand how things could be working and also for external people to do user research on … he also tells it like it is and I valued that quite a lot.

Philipp Heuberger, teammate at Sweap · on LinkedIn

ReferenceMatthias Heicke, Co-founder and CTO, Sweap · ask me for an introduction

More work