Case study — operator experience
Braun Brothers Reunion: how real festival operations shaped VenueVault
Braun Brothers Reunion is an established multi-day music festival that serves thousands of attendees. VenueVault founder Robert “Bobby” Paugh has hands-on experience supporting its ticketing, marketing, customer communication, and on-site operations. That work is where VenueVault’s requirements came from.
Create your account, connect Stripe, and build your first event before you publish.
What this case study does and does not claim
What is supported
Bobby’s direct operational experience with an established multi-day festival, the operational requirements that experience produced, and the VenueVault features built to meet them. The festival uses a Stripe-based ticket-payment flow.
What is not claimed
No ticket volumes, revenue figures, savings percentages, conversion improvements, payout-speed improvements, or before-and-after statistics are claimed. Nothing here is presented as a measured result produced by the VenueVault platform.
Festival context
Braun Brothers Reunion runs over multiple days and serves thousands of attendees. It is independently operated rather than run by a national promoter, which means the same small group of people handles the on-sale, the inbox, the gate, and the reconciliation afterward. There is no separate ticketing department to absorb mistakes.
A festival of that shape has requirements a single-night general-admission event never surfaces: multi-day passes alongside single-day tickets, capacity that has to stay honest across every day a pass covers, buyers who need to be reached before they travel, and gates that have to move quickly when everyone arrives at once.
Operational challenges
Multi-day inventory
Weekend passes and single-day tickets draw from the same physical capacity, so day-level counts have to stay correct as both sell.
Attendee communication
Buyers need arrival details, schedule changes, and gate instructions before they get in the car — not after.
Gate throughput
Arrivals cluster. Scanning has to work on ordinary phones, across several entry points, without a fragile hardware dependency.
Operational visibility
Organizers need to see what sold, what is left, and who has checked in while the event is happening, not in a report next week.
Payments and reconciliation
Ticket money and the records that explain it have to line up cleanly with the festival's own accounting.
Ownership of the buyer relationship
The festival's audience list is the festival's asset. It should not sit behind a marketplace.
What the real-world experience taught VenueVault
Multi-day ticketing is a capacity problem, not a naming problem. A pass has to consume inventory on every day it covers.
Communication tooling is part of ticketing. If you cannot reach ticket holders quickly, an operational change becomes an operational failure.
Scanning has to work on the staff you actually have, on the phones they already carry, in places with imperfect connectivity.
Operators need numbers during the event, not just afterward — sold, remaining, and scanned, per day.
Payments belong to the operator. Money should land in the festival's own Stripe account, on the festival's own schedule.
The buyer list, the export, and the reporting all belong to the event, not to a platform.
How VenueVault addresses those requirements
These are current platform capabilities, described as capabilities — not as measured outcomes at any specific festival.
Ticketing and payment workflow
Events can carry multiple ticket types, including multi-day passes that draw down capacity on every day they cover, so day-level availability stays accurate. Checkout runs through the venue’s own connected Stripe account, so ticket payments are collected by the operator rather than held by a marketplace. Braun Brothers Reunion uses a Stripe-based ticket-payment flow.
Standard Stripe payment processing fees still apply and are billed by Stripe, not VenueVault.
Customer communication
Buyers receive their tickets and order confirmation by email, and organizers can email ticket holders from the dashboard when arrival details or schedules change. Attendee records stay in the organization’s own account, so the audience list remains the festival’s to use.
Gate and scanning operations
Check-in runs in a mobile browser, so staff scan with the phones they already have. Scanner seats are assigned per plan, each ticket validates once, and check-in status is visible to the whole team as the gate moves.
Data ownership and reporting
Sales, attendee, and check-in data belong to the organization and can be exported. Dashboards show sold and remaining inventory and check-in progress, and Pro adds API access for teams that want the data in their own systems.
Lessons for independent festivals
- Model your passes against real day capacity before your on-sale, not after your first oversell.
- Decide who owns the attendee list before you choose a ticketing platform.
- Test your gate flow with the phones and staff you will actually have on site.
- Keep payments in an account you control so reconciliation is your own bookkeeping rather than a platform statement.
- Be clear with buyers about pricing. VenueVault adds no per-ticket platform fee; standard Stripe processing fees still apply on any platform.
Running a festival with these same problems?
Start on your own, or bring us your on-sale, pass structure, and gate plan and we’ll walk through it with you.
Standard Stripe payment processing fees still apply and are billed by Stripe, not VenueVault.