Event Registration & Ticketing

The Conference Organiser v1.0

Runs the annual congress of a trade association: 900 attendees over two days, member and non-member prices, workshops with twenty seats each, and half the bookings made by an assistant for three colleagues at once. Wants the shop on the association's own site, invoices that a company's accounts payable accepts without a phone call, badges printed at the door from the same data, and session check-in that counts towards continuing-education points.

The Venue Promoter v1.0

Books bands and DJs into a 250-capacity club, four nights a week, and pays the artists their guarantee before the show. Needs the ticket money before the event rather than three weeks after, a fee that buyers pay on top of a twelve-euro ticket, a door app two volunteers can run on their phones without signal in the basement, and the buyers of last month's show on a list the club can mail, not the platform.

The Course Provider v1.0

Runs a small adult education business: evening courses over eight weeks, weekend workshops for coaches, and a few seminars that employers pay for. Wants registrations with the questions each course needs, a waiting list that fills a cancelled seat by itself, VAT that is right for exempt teaching and taxable workshops in one shop, invoices to employers in her own name, and cancellation rules her terms can point to.

The Revenue Accountant v1.0

Keeps the books for a concert promoter and two conference organisers and gets a payout statement each month that nets ticket sales, refunds and platform fees into one number. Wants to know who sold the ticket in whose name, which VAT rate applied to each ticket, a fee invoice kept apart from the revenue, credit notes for every refund, and an export that reaches DATEV without a spreadsheet in between.

The Data Protection Officer v1.0

Advises a federation of sports clubs whose events collect names, employers, dietary needs and the odd wheelchair note. Reads the ticket buyer terms before the feature list, because they say whether the platform is a processor or a controller with its own newsletter. Wants a DPA that names the organiser as controller, subprocessors with their countries, and attendee lists that are deleted after the event instead of kept for marketing.

The Skeptic v1.0

Has seen "free for free events" turn into a fee on every paid ticket that buyers blame the organiser for, payouts held until a week after the show, and a platform that emails the organiser's audience about a rival's concert. Reads "your data belongs to you" next to buyer accounts on the platform's own app, and an export that stops at names and emails — and asks what leaving would cost.