BY EVENT TYPE
Roadshow and multi-city event software
- Cities6
- Currencies · time zones4 · 5
- Built from one templateYes
- Combined reportingOne view
Set the series up once, then repeat it city by city.
Common challenges
The same event, five times over
Rebuilding each leg from scratch means five chances to get a date, a price, or a form field wrong — and no single view of how the series is doing.
Every city collects in its own currency
London takes pounds, Singapore takes dollars, and neither should be converted at checkout or pooled on a platform.
Nobody agrees what time it is
A session at 14:00 means five different things across the series, and a wrong invite time costs you the room.
What to look for in roadshow and multi-city event software
A roadshow is the same event run again and again in different cities, currencies and time zones. The work is repeating it without re-keying it. Six checks.
- 01
A new leg in minutes, not a day
Duplicate the first leg and change the date, venue and capacity; ticket structure, form and branding carry over.
- 02
Local currency in every city
Price each leg in its local currency, and attendees pay in it. Every leg settles into your organization's Stripe account; a leg sold by a different legal entity runs as that entity's own organization.
- 03
Local time everywhere
Session times are stored against each leg's own time zone, so the public agenda, confirmation emails and calendar invites show local time rather than a converted one.
- 04
One brand across the series
Every leg is built from the same saved template and can have its own branded address, so the series reads as one programme.
- 05
Check-in that travels light
Local staff join a phone with a short code and no account of their own, download the list before doors open and keep scanning offline — no hardware to ship between cities.
- 06
Series-level reporting
Cross-event reports put the legs side by side, and channel attribution shows which partner or campaign filled each city.
Tools for roadshows
Every leg settles into your organization's own Stripe account. A leg sold by a different legal entity runs under that entity's own organization.
Each leg has its own currency, capacity and pricing, and attendees pay in that leg's currency.
Clone the site for each leg. Content and branding carry over; dates, venue, and speakers change.
Session times stored against each leg's own timezone, so every invite and every public page shows the right local time.
Compare legs side by side — which city filled and which channel worked there.
Give each leg a branded address, such as series-london.bagevent.io, so every city's link reads as part of the series.
Your event workflow
- SET UP ONCEBuild the first leg
Site, ticket structure, and registration form for city one.
- PER CITYClone and localise
Duplicate it, change dates, venue, and capacity. Pricing and branding carry over.
- SET CURRENCYPrice each leg locally
Set the leg's currency before tickets go on sale; attendees pay in it.
- RUNSame kit in every city
The crew uses the same check-in setup at every stop, so nobody relearns it.
- AFTERReport the series
Per-leg numbers side by side, with revenue shown per currency.
Frequently asked questions
One programme, one set of content, and a leg per city: each leg is its own event with its own date, venue, capacity and currency, duplicated from the first. Reports read across the legs and per city, which is what roadshow event management software has to do that a single-event tool does not.
Yes. Each leg is priced in its own currency and attendees pay in it, into your own Stripe account. If a different legal entity sells a leg, run that leg under the entity's own organization and Stripe account. bagevent takes 0% of it.
No. Duplicate the first leg and change dates, venue, and capacity — ticket structure, form, and branding carry over. That is usually the difference between a day and an hour per city.
Session times are stored against each leg's own timezone, so the public agenda, confirmation emails, and calendar invites all show the correct local time rather than a converted one.
Yes, on every plan. Cross-event reports line the legs up side by side on registrations, revenue, and check-in rate. Revenue is shown per currency rather than added together.
Pro is $99 a month billed annually ($129 month to month) and Business $479 a month billed annually ($599 month to month), with Enterprise quoted individually. Cross-event reports and channel attribution are on every plan; the API and webhooks start on Business. bagevent takes 0% of ticket sales on every plan; the only deduction from an order is the payment provider's processing fee. There is a 14-day free trial with no credit card.
0% platform fee on every plan — from $99 a month billed annually, with a 14-day free trial, no credit card, fair use on paid tickets (50 registrations / $500).
See pricingReady to take the programme on the road?
Get started in minutes — or try the live demo to see what your attendees get.