UX case study · RevoTickets · 2026

Designing onboarding for production houses

Three small production houses got stuck in the same three places while setting up RevoTickets. This is the onboarding I am designing in response.

Responsibilities

Product, UX

Product

RevoTickets, for Revolution Stage

Year

Status
Design proposal, not built yet

Where they got stuck

Three small indie production houses besides Revolution Stage have signed up to RevoTickets. Each of them signed up through a link I sent, explored on their own, and messaged me when they got stuck. They got stuck in the same three places: the hall builder, setting up seat categories, and not knowing what to do first, or what comes after that.

A team that signs up lands in the default onboarding of Bullet Train, the Rails framework RevoTickets is built on, and then an empty dashboard with four counts, a table of recent bookings and a New event button. Behind that button is a chain of work: a venue, a hall drawn level by level and section by section, seat categories with prices, an event page, and shows that each pick a hall and a configuration before their seats are generated. The dashboard never says which of those comes next.

The hall builder is the most demanding screen in the app. It also has English strings only, while the storefront, the organiser dashboard and check-in are all in English and Malay. Seat categories are set up in two places. You create them on the venue, then go into the hall builder, pick a category chip, switch to Paint and click seats to assign them, so the second half of the job happens inside the hall builder.

The design

The design has two parts: a start page, and a setup checklist that walks the team through the rest.

The start page. It asks the three questions the WhatsApp call to action on the RevoTickets site already asks: the venue, the dates, and roughly how many seats. From the answers it creates the event and its draft shows, all on one page. I made a similar change on Sama², where I replaced a six-step onboarding wizard with a single page, because six screens and a row of progress dots gave people a journey they could fail halfway through.

The setup checklist. After the start page, the dashboard shows the remaining steps in the order the data needs them: hall, seat categories, event page, shows, put on sale. Each step is one link, and each tick comes from the data instead of being clicked by hand. The hall step is done when the venue has a hall, seat categories when every seat has one, shows when they exist, and the last step when the event is published. Only one step is marked as next at a time, so a new team always knows what to do first and what comes after it.

The hall step. RevoTickets can already share halls between teams. An admin marks a venue as shared, and another team can browse a catalogue and clone its seat-map structure, without pricing, into their own account. In onboarding, that catalogue is the first thing the hall step offers. If the hall is there, the team clones it and moves on. If it isn't, the venue starts as free seating, which the app already supports, and the hall gets drawn properly before the next run. When the builder does become part of a team's first week, it needs its Malay translation first.

The seat categories step. Staff name each category, give it a colour and a price (the features page uses VIP, Premium and Standard as its examples), and paint seats onto it in the same view. The builder already counts what's left, from "N seats have no category" down to "Every seat has a category.", and that count becomes the step's progress bar. A cloned hall always lands on this step, because cloning leaves pricing behind, so every new team will do it. For a free-seating venue the step is shorter: a price and a capacity per category.

Help on each step. An in-app help centre is still on my to-do list, so today there is no in-product help for staff at all. The hall and seat category steps each get a short explanation of what the step is for and what "done" looks like. Each step also has a "stuck? message us on WhatsApp" link, so when someone asks for help I can see which step they were on.

Everything the design uses already exists in the app: the shared catalogue, free seating, the seat-category counts, the publish toggle and the WhatsApp link. The new work is the start page, the checklist, and putting the seat-category painting into its own step.

What comes next

Two smaller fixes come with the design. When a new team invites people, the invite screen should describe roles as jobs the team already has. Admins handle money (bookings, coupons, marking a booking paid), editors manage events and shows, and everyone else can read. Described that way, they become the producer, the person running the event pages, and the door crew.

The second fix is copy on the public features page. It describes the settlement summary as "Gross, fees and net, with the payout schedule laid out", but the settlement tab in the app says fees, net payout and settled refunds aren't tracked yet. A production house moving off a spreadsheet will ask about money early, so that page should describe what the settlement tab actually shows today.

None of this is built yet. Until it is, new teams keep exploring on their own and messaging me, and each stuck message is worth noting against the step it came from, so the next version of this design starts from a list instead of my memory.

Sama²