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.
↑ Try it — tap a fix
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.
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.
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.
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.
An early load-in or a backline hire gets agreed in an email. By settlement nobody remembers it happened — and nobody charges for it.
Three weeks out, confirmed, and nothing recorded against it — no tech, no chase, no notes — until show week arrives and it's a scramble.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
It reads the sheet you already keep — the same columns, the same colours. No data entry, no cut-over weekend.
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.
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.
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.
Change it in the sheet and VMT follows — in about two minutes for real; sped up here.
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.
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.
No slides. We'll open a real week's schedule and show you what it would have caught.
Book a lookThere'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.