Book a look
Venue Management Tool

Your venue already has all the information.VMT is the part that remembers it.

Your shows live in a spreadsheet or in Airtable. The details live in a mailbox. The booking is in Muzeek, the tickets are in Moshtix — and joining it all up lives in one person's head. VMT keeps reading all of it — the sheet or the base every couple of minutes, the mailbox every ten, bookings every few hours and ticket sales twice a day — and shows each person what needs them.

~2 minfrom your sheet
to everyone's screen
14 daysof what needs you,
always in view
1screen instead
of five
What needs you today 5 shows
Fri 16/10in 3 days
Marigold Static
specs missing
Sat 17/10in 4 days
Orbit & the Strays
advancing not submitted
Thu 22/10in 9 days
Lucy Fern Quartet
⏰ early load-in 2PM (requested)
Fri 23/10in 10 days
Kettle & the Low Tides
no tech
Sat 24/10in 11 days
Grace & the Greyhounds
4 unreviewed files
All clear for todayNothing needs you. VMT keeps watching.

↑ Try it — tap a fix

The problem

Nothing is missing. It's scattered.

A venue doesn't lack information. It has too many places to keep it — and the job of joining them up falls to whoever happens to remember. That works right up until the night they're off.

The schedule sheetDATES · STATUS · TECH The venue mailboxSPECS · RIDERS · QUOTES MuzeekBOOKINGS · ADVANCING MoshtixLISTINGS · SALES Phones & texts"DID ANYONE CHASE…" One person'shead
The schedule sheetdates · status · tech
The venue mailboxspecs · riders · quotes
Muzeekbookings · advancing
Moshtixlistings · sales
Phones & texts"did anyone chase…"
joined up only in
One person's
head

None of it shows up as a line in the accounts. It shows up as a bad night — the wrong times on the door, the rider nobody read, the tech who was never told — and by the time anyone notices, it's too late to fix cheaply.

01 · THE CHASE

The chase nobody remembers making

A follow-up made by phone is invisible to whoever's on next. Three people each assume somebody else chased the specs — and nobody did.

02 · THE ADVANCE

The tech who never got the advance

Sending the times, the specs and the notes is a step someone has to remember. Miss it once and a tech walks in on the night knowing none of it.

03 · THE EXTRA

The extra nobody billed

An early load-in or a backline hire gets agreed in an email. By settlement nobody remembers it happened — and nobody charges for it.

04 · THE SILENCE

The show nobody's touched

Three weeks out, confirmed, and nothing recorded against it — no tech, no chase, no notes — until show week arrives and it's a scramble.

How it works, in one sentence

VMT reads your sheet, your mailbox, Muzeek and Moshtix all day long, matches everything to the right show, and turns what's missing into a queue — with the fix one click away.

Your scheduleGOOGLE SHEETS · EXCELIN DRIVE · AIRTABLE Your mailboxMICROSOFT 365 MuzeekBOOKINGS · ADVANCING MoshtixLISTINGS · SALES VMTMATCHES · REMEMBERS What needs you todayTHE WORK QUEUE Everything about one showTHE SHOW WINDOW What's going on saleTHE SHOW TRACKER
Your scheduleGoogle Sheets · Excel in Drive · Airtable
Your mailboxMicrosoft 365
Muzeekbookings · advancing
Moshtixlistings · sales
VMTmatches · remembers
What needs you todaythe work queue
Everything about one showthe show window
What's going on salethe show tracker
The life of a show

From the booking to the bar report.

The easiest way to see what VMT does is to follow one show through it. Here's what happens, and when — most of it without anyone asking.

T–90Booked

It turns up on its own.

Someone adds the show to the sheet, as they always have. Within a couple of minutes it's in VMT. Over the next day it finds its emails and matches its Muzeek booking and its contact person (with Muzeek) — room by room (the bar's acts included), by the night even when the booking goes by another name, a matinee and an evening show each with their own booking (never one booking on both), and it spots the other nights of a multi-night run, and within the week it works out who the contact is. A show still without its booking? One button re-checks them all, and never touches a booking already linked. Or pick it from a list of every Muzeek booking email since a date you choose, nearest the show first. Or open Link shows: every show still without a booking on the left, every Muzeek booking (or Moshtix listing) by date on the right — click the show, then its booking, and it's linked. Muzeek's own booking calendar is read every hour too, so VMT tells you what's booked in Muzeek but not in the sheet (and the other way round), rings when a booking moves, is cancelled or is announced, and lines up the booking links still missing for a one-paste fix. Where Muzeek keeps the bar as its own account, VMT reads that account too and only ever matches its bookings in the bar. Every file it finds, and any you add from your phone or desktop, sits at the top of the show as cards you flick through, a PDF fits a phone screen page by page, a Word rider opens as a PDF laid out exactly as Word lays it out (Microsoft's own converter), and a photo that is really the stage plot can be renamed "Stage plot" for everyone, the original left untouched.

T–45On sale

You know when it launches — and how it's selling.

A launch diary lists every show by the day its tickets go on sale, so promo gets planned against a date, not a guess. Once it's selling, VMT tracks it week to week and flags the ones behind similar shows at the same distance out. Every ticket type's price and booking fee comes straight off the listing too, with the door price worked out from GA — and a flag when the schedule says something different.

T–21Advancing

The chase happens — and everyone can see it did.

Specs missing? One click writes the chase, you check it, it goes. The advancing form is tracked question by question (with Muzeek) — and if you switch it on, a reminder goes to the act by itself nine days out when the form still isn't done, once per show, logged on the show for everyone to see. An early load-in buried in an email is caught, priced by the hour and queued for a yes — so it gets billed, and once approved it becomes the show's load-in on every calendar, sheet and advance. The venue's own gear — a wireless mic at $90 — sits on a list of standard charges you keep yourself: pick it, set how many, and it's on the settlement — and when an act ticks Yes to it on the advancing form, it goes on their show by itself. Need a quick word with the act? Email them from the show, as yourself — with your own email signature and logo on it — and the replies land back on the show where the whole team can see them.

T–7Show week

The tech is briefed. Nobody retyped a thing.

With Muzeek, Advance to tech builds the email from the booking's times, the specs and the notes. The show lands in the tech's own phone calendar — with load-in and doors from the booking, and a tap-to-open link to every spec the venue has, from Muzeek, or by email or upload once someone ticks it spec (never a hospitality rider) — and when something moves, the calendar follows on its next refresh. Once the act submits the advancing form, the tech's entry gains the answers the tech needs — the act's on-the-day contact, the support acts' contacts, headcount, riser, backline, inputs, lighting, load-in requests — as a short list of the questions it recognises as tech; health, money, guests and the act's own proposed times stay in the app (the times on a calendar are the venue's). A big night with a lighting tech and a stage hand too? Add as many techs as it needs; each gets the show in their own calendar. An extra tech the act is paying for — an LX op, say — is ticked as an add-on (or added from Show extras) and lands in the show's needs with its cost, on the Prod notes and on the settlement — while the tech's own advance and calendar name them without the fee — techs see only the charges they make themselves: the early load-in at the venue's hourly rate and the multitrack's tech fee. What the calendar entry says is the venue's to write: reorder it, hide what the techs don't need, and add your own lines — a link to the house tech handbook at the bottom of every one.

Seated showThe day before

The tables are counted for you.

For a seated night, the ticket list comes straight from Moshtix or TryBooking: every reserved-seat booking with its party size and ticket type (from TryBooking, with the seats it was given, as a suggestion beside its table that never overwrites one you typed), a tally of bookings by party size (twos, fours, sixes, the social table), and a sheet to print, in whatever order the floor wants. General admission stays out of the way unless you ask for it, and so do the buyers' mobiles and emails: only the people who see the money can reveal them, with one button, and they are removed from the live system a week after the show, with the buyers' names; backup copies age out within a month, and once the venue's backup key is installed they are encrypted with a key kept offline. Accessible bookings are always included — they need specific seating, so they stay on the list, the print and the counts even while general admission is hidden.

Show dayTonight

Tonight, on one page.

A run sheet for the bar and the door, filled in from everything above and ready to print. The guest list and hospitality answers from the advancing form (with Muzeek) sit alongside, so nobody retypes a guest list at 6pm. After the show they don't linger: the guest-list box becomes a count the next day, and dietaries and allergies go a week after. A guest-list file someone sent or uploaded stays with the show's files under the file rules (an email's attachment 90 days after it was last used, an upload a year after the show).

AfterThe morning

Nothing is lost when the night ends.

The bar report is filed from the show itself — how it ran, what went wrong — with the crew's notes attached. The week's report is one click from those, ready for Monday.

Why it's different

No new system to feed.

Most venue software asks you to move your whole world into it. VMT goes the other way: it sits on top of what you already run and does the joining-up.

ADMIT ONE · 01

Nothing to migrate

It reads the sheet you already keep — the same columns, the same colours. No data entry, no cut-over weekend.

ADMIT ONE · 02

The sheet stays the boss

Edit in the sheet or in VMT. VMT's edits reach a Google Sheet in seconds, the sheet's reach VMT in a couple of minutes, and if they ever disagree, the sheet wins.

ADMIT ONE · 03

Nothing goes out without you

Every chase and every advance VMT writes is a draft until a person reads it and says go — unless you switch on one of its automated emails (an advancing reminder, a spec chase, worksheet auto-send) — and those wait until you've seen who they'll write to and pressed Start. It remembers; you decide.

ADMIT ONE · 04

It watches itself

If a sync stalls or something breaks, its health strip says so — and at our reference venue it emails the admin before anyone on the floor notices.

Your sheet — tap the cell
DateActStatus
Fri 13/11The Velvet Hours
VMT, on everyone's screen
The Velvet Hours
Fri 13/11 · evening
● On hold

Change it in the sheet and VMT follows — in about two minutes for real; sped up here.

Liveevery show,
every night
In use now

Built inside a working venue.

VMT wasn't designed in a meeting room. It's run every night at Brunswick Ballroom in Melbourne, through the same sheet the venue has always kept — with BABS, its second room, running its own programme alongside in the same system. Everything on this page runs there today, apart from worksheet auto-send — that one is there for the venues that want it.

Brunswick Ballroom · Melbourne BABS · its second room
Also from Riderly · Guest List

The door, sorted.

The guest list and door app for live music venues. Artists and promoters add their own guests through private links with their allocations; door staff check people in and out from their phones — partial +1s included — and it keeps working when the signal drops. One shared door counter, manager codes to go over capacity or an allocation, and a report after every night: door peak, guest list arrivals and no-shows, tickets sold against the door count.

It works on its own. With VMT, every confirmed show appears in it by itself, each night's door numbers come back to the show, and one tap on the show opens door mode already signed in.

318in · of 330
Try the door counter. Every phone on the door shares it.
Fair questions

The ones every owner asks.

Do we have to change how we run the schedule?
No. Your sheet stays the master. VMT reads it every couple of minutes and, if you run a Google Sheet, writes edits back within seconds. (Keeping an Excel file in Google Drive instead? VMT reads it the same way and writes edits back within about five minutes. Starting out with your programme in Airtable? VMT reads the base every couple of minutes and writes edits back within seconds — and if the two ever disagree, Airtable wins.) Whoever prefers the sheet keeps using the sheet; whoever prefers VMT uses that. They agree with each other.
What if VMT and the sheet ever disagree?
The sheet wins, always. Fix the sheet and VMT follows within a couple of minutes. Nothing in VMT can quietly overrule your own master record.
Does it send emails on its own?
Not unless you switch it on. VMT drafts the chase, the advance and the morning digest, and a person reads them and presses send. By itself it only alerts your admin if something stops syncing. There are opt-in exceptions: worksheet auto-send, which emails a show's worksheet to its booking contact about three weeks out, once a contact is on file; and the automated emails in Admin — an advancing-form reminder and a tech-spec chase, each sent at 9am a set number of days before the show, once per show, from the venue's mailbox, with a preview of exactly who the next run will email, and nothing goes until you have looked at it and pressed Start. All are off unless you turn them on, and anyone who asks to stop automatic emails is never sent one. Extras it spots in an email (an AI reads the few emails that mention one, with every email address and phone number taken out first) wait for a yes before they're billed (and an email saying one is no longer wanted waits for a person too); a contact it's confident about is filled in for you, and anyone can change it.
What happens if we stop using it?
Your schedule isn't trapped. Past and future, it's exactly where it always was — in the sheet you started with — and there's no export to run first. What exists only in VMT (bar reports, crew and contact notes, the jobs list, run-sheet edits, settlement figures) goes with the tool, so that's worth knowing going in.
Whose inbox does it read?
Your shared inbox and your production mailbox, always together — a spec sent to either one lands on its show within minutes. Your admin can add a team member's mailbox too. Anyone else who connects their own mailbox sees their own mail on a show; nobody else does unless your admin adds it, and every change to that list is logged. Reading the shared view is not writing as it: someone without a mailbox of their own can't draft as yours unless your admin allows it, and every such draft is logged.
What if someone asks what we hold about them?
One search by their name, email or phone finds them everywhere VMT keeps them — show fields, ticket buyers, door lists, Muzeek forms, emails, notes, the activity log, advances. Your admin downloads just their data (nobody else's from the same shows) to send them, or erases it after a preview: each place then says it was removed at their request, and VMT doesn't bring their contact details back when it reads Muzeek, your mailbox and your ticketing again (those systems themselves you ask directly). Admins only, and what was searched for is never logged. Every email VMT sends by itself carries a stop link for the person it's to, and anyone can delete their own Riderly account.
What does setting it up involve?
We read your existing sheet's columns and status colours, connect your mailbox through your own account, and connect your ticketing with your venue's own account. Works with Moshtix and TryBooking — read-only at TryBooking: VMT reads its sales and never changes anything there. Works with Google Sheets and Airtable for the programme — Airtable for a venue starting out on VMT; a venue already on a sheet stays on it. The Muzeek connection runs live at our reference venue; bringing it — or another booking or ticketing system — to yours is agreed before we start, not a surprise after. No retyping, no reformatting — and it arrives wearing your venue's own logo and colour.
How does everyone sign in?
One Riderly sign-in for every venue and tool. Each person has one account — a password and a code from an authenticator app on their phone — that opens every venue they work at, VMT and the other Riderly tools there included. You invite your team and choose each person's role in one place — the invite goes by email to the person's own address, so only they can accept it — and someone you remove is out of every tool within 12 hours. Signing out ends that sign-in on the server, and a password change or "sign out everywhere" ends it on every other device too.
Does it work on a phone?
Yes. It installs straight from the browser like an app — no app store — with tonight's shows, what needs you and the schedule one thumb away. Techs get their shows in their own phone calendars, kept up to date for them. And anyone you choose can have the next gigs — poster, times and on-sale — on their own dashboard or desktop widget, through a read-only link with nothing private in it.
A real next step

Ten minutes with the work queue beats this page.

No slides. We'll open a real week's schedule and show you what it would have caught.

Book a look

There's no pricing on this page — that's a conversation, not a line item. Write to wpmixing@gmail.com and we'll find ten minutes.