The venue back office, sorted: now, next, never.

Nobody opens a venue to do admin. But run an honest count of where the working week goes in an independent venue and the picture is consistent: a large share of paid hours — a booking manager's, an admin's, or the owner's own evenings — goes on work that follows the same shape every single time. Read the thing. Sort the thing. Reply to the thing. Chase the thing. Log the thing. Report the thing.

When we talk about MarsAI replacing staff workload, this is the workload we mean. Not the humanity of hospitality — the paperwork wrapped around it. The useful question isn't "can AI run a venue?" (no), it's "which specific jobs in the back office are process, and which are judgement?" So here's the map we actually use, sorted into now, next and never.

The test

If you can write the rule down, the OS can run it. If you can't write the rule down — because the answer is really taste, accountability or a relationship — it stays with a human. That line doesn't move to suit a sales pitch.

Now — the jobs the OS runs today

These six jobs make up the booking and enquiry lane — the part of the back office MarsAI ships as a managed deployment today. Together they're most of what the £30k+ booking-admin role does all day.

1. Enquiry triage

Every channel — web form, email, DMs, referrals — read and normalised into one queue, scored by value and urgency. The £8,000 corporate enquiry stops queueing behind a table booking. Rules you set; enforcement you don't have to think about.

2. Drafting and sending replies

Responses in your venue's voice, in minutes, at 11pm as reliably as 11am. Routine sends run on rails; anything above your thresholds — value, discount, sensitivity — waits for your approval before it leaves the building.

3. Follow-up chasing

Most bookings die in silence, not rejection. Every open enquiry gets a timed chase sequence; stalls escalate to you instead of quietly going cold. Nothing depends on somebody remembering.

4. Logging and record hygiene

The job everyone skips at 6pm: getting the conversation into the system. The OS is the system, so logging isn't a task — it's a side effect. If it's not in the record, it didn't happen; with an OS, everything is in the record.

5. Handoffs

Enquiry to site visit, visit to quote, quote to confirmed event, event to operations — each handoff carries its context with it. No "didn't anyone tell the kitchen?" moments, because the handoff isn't an email someone forgot to send.

6. Pipeline reporting

Pipeline value, conversion by channel, at-risk deals — read live from the same record the work happens in, instead of assembled every Friday by a human with a spreadsheet and a sigh.

Next — on the roadmap, honestly labelled

These jobs pass the process test, but they read from data the booking lane has to build first — which is why they're phases on the venue OS roadmap rather than features today. We label them roadmap because that's what they are.

• Deposit and invoice chasing — payment requests raised from the booking record and chased on schedule, so the awkward money email stops being anyone's job.
• Month-end packs — per-event revenue and a clean summary handed to your accountant, instead of a shoebox of PDFs and retyped numbers.
• Marketing re-engagement — campaigns to the enquiries that went cold, built from real pipeline history, sent only with your approval.
• Stock reorder drafts — expected consumption tied to confirmed events, draft orders ready for sign-off before the big weekend.
• Rota drafts — staffing skeletons built from the events calendar, offers and confirmations chased by message, hours compiled for payroll.

Never — the executive list

Some back-office calls are dressed as admin but are actually the business. These stay human at every phase of the roadmap — not because the technology can't be pointed at them, but because they're the part where accountability, taste and relationships live:

• Final pricing on big quotes — above your thresholds, every number waits for you.
• Discounts and exceptions — margin is an owner's call, made with context the rulebook can't hold.
• Complaints and refunds — flagged with full context, decided by a human. Always.
• Showrounds and tastings — the moments that sell the venue are human moments. The OS preps them and follows them up; it doesn't attend.
• People — hiring, pay, performance. Never a system's call.

This split isn't a limitation we tolerate; it's the design. We wrote up why "fully autonomous" is the wrong goal in the human-in-the-loop post — the short version is that removing the owner from executive calls doesn't make a system more advanced, it makes it a liability.

What the "now" column is worth

Price the six jobs in the now column and you've priced the booking-admin role: £30k+ in salary, £2,900+ a month fully loaded once NI, pension, holiday and cover are counted. MarsAI runs that lane from £995 a month, most venues £1,250–£1,750 — the exact number comes out of the audit, not off a rate card. Those benchmarks are directional, not a promise of your saving: the audit builds your actual numbers, and if they say "hire a human", the written plan will say that too.

Run the map on your own venue

You can do a useful version of this exercise in an afternoon, whether or not you ever talk to us:

1. List every recurring admin task in the venue — including the ones done at home, at midnight, by you. Those count double.
2. Put honest hours against each. Not the tidy version — the real one, including the checking, the retyping, the "just quickly".
3. Ask the test question: could you write the rule down? If a competent temp could do it with a one-page instruction sheet, it's process.
4. Count the tools each task touches. Every extra tab is a tax — and a clue that a human is being used as an integration.
5. Sort into now, next, never. The "now" pile is your automatable workload. If it adds up to most of a salary, that's your business case.