Case study · The Beaumont Studios
What happens when a venue gets a real operations layer.
The Beaumont Studios is a Vancouver arts charity: artist studios, a gallery, a venue, and the hundred small operational fires that come with all three. I spent eight years as its Operations Director. This is what got built.
- 12+
- hours/week of admin absorbed
- 30+
- recurring reports automated
- 371
- artworks registered, tracked, and shown through one system in a single fundraiser
- 8
- years running venue operations
[PLACEHOLDER metric]
[PLACEHOLDER metric]
№ 01
The situation
Like most small cultural organizations, the Beaumont ran on goodwill and spreadsheets. Studio rentals, event bookings, artist rosters, donor records, and grant reporting all lived in separate documents that agreed with each other on good days.
The people were excellent. The information layer was not. Every hour spent reconciling a booking calendar against an invoice list was an hour not spent on artists, audiences, or the building itself.
№ 02
The operations layer
Over eight years I built the venue a management platform: one place where bookings, studios, events, and the money attached to them actually lived. Not enterprise software with a nonprofit discount. Purpose-built tooling shaped around how a small venue really works.
On top of that came the automation: reporting and scheduling workflows that assembled themselves from live data instead of being hand-built at month-end. The recurring question "where are we at?" started having a recurring answer.
№ 03
The show that proved it
The clearest test was Art Incognito, a fundraiser exhibiting 371 artworks. The part nobody saw: a purpose-built registration system where artists submitted work and staff catalogued every piece, so 371 artworks moved from intake to wall to sale night without a lost label or a hand-typed list. The paperwork that usually buries an event that size simply ran.
The part everyone saw: a fully offline, three-projector coordinated presentation. No cloud, no wifi dependency, no single point of failure at showtime. That is the standard operations technology should be held to in this sector: it works during the event, in the dark, with the internet down and the room full.
“It works during the event, in the dark, with the internet down and the room full.”
№ 04
What it means for your organization
The Beaumont years are why Quietworks exists. Every workflow I automate for clients is one I have personally run the manual way: the grant report at 11pm, the board package the night before the meeting, the schedule that three people maintained in four places.
The tools have gotten dramatically cheaper and better since I started building them. The approach has not changed: understand the operation first, then automate the parts no human should be doing.
From the build log
Six automations, plainly described.
All real, all built for working venues, most still running in production. The names are simplified; the workflows are exactly as described. Every one of them has a nonprofit twin.
01
The enquiry that files itself
- Was
- Every event enquiry and artist submission landed in a website forms plugin, got copy-pasted into a spreadsheet, and occasionally got lost on the way.
- Now
- The website’s forms now write straight into the operations database: attachments saved, source page recorded, mailing-list opt-in handled, and the lead sitting in the pipeline the moment someone hits submit.
- In your world
- Volunteer applications, program registrations, artist submissions. Any form a human currently retypes.
02
Contracts that chase themselves
- Was
- Artist and venue agreements lived in email threads. “Did they sign yet?” was a research project.
- Now
- Contracts generate from templates, pull the booking’s numbers straight from QuickBooks so nothing is re-typed, go out for e-signature, and show live status on the ops dashboard. Nothing books until the signature exists.
- In your world
- Artist agreements, facility rentals, MOUs with partner organizations.
03
The morning numbers
- Was
- Bar sales, ticket sales, deposits, and who-still-owes-us lived in four systems and one long-suffering spreadsheet, reconciled by hand at month-end.
- Now
- A dashboard pulls the money picture from the POS, the ticketing platform, and QuickBooks: sales, deposits, and a standing list of overdue events. “Where are we at?” has a permanent answer.
- In your world
- The board asks; the dashboard answers. No more building the answer by hand the night before the meeting.
04
Scheduling by text message
- Was
- Filling shifts meant a group chat, a spreadsheet, and hope.
- Now
- The system messages staff about open shifts on WhatsApp, records their replies, and syncs the final schedule to Google Calendar. The manager approves; the machine does the tag.
- In your world
- Swap staff for volunteers and it is the same machine.
05
The program that runs its own admin
- Was
- A community radio station inside the venue: presenter applications, show schedules, and presenter payments, all managed by hand by people who had other jobs.
- Now
- One pipeline holds applications, shows, and payments. The humans decide who gets a show; the system does the paperwork around the decision.
- In your world
- Any recurring program with rotating people: classes, residencies, workshop series, mentorships.
06
The end of night that fills itself in
- Was
- Every night ended with a manual close-out: sales totals copied from the POS, the staff list rebuilt from memory, tips split on a calculator at 1am.
- Now
- A mobile end-of-night app pre-fills the sales from the POS and the night’s staff from the scheduling system, does the tip math, counts the inventory, and emails the report on submit. Dark mode by default, because venues are dark at 1am.
- In your world
- Any closing routine your team reconstructs by hand: the event debrief, the program wrap-up, the till count.
Want this kind of operations layer?
The Audit is where every engagement starts. Two weeks, $3,000, and you leave with a roadmap either way.