Research brief 04.06Back office

The Admin Stack: Back-Office Cost per Booking

No single line in the admin stack looks like a problem. That's the design. Subscriptions are priced to be individually ignorable, and a venue's back office is where individually ignorable goes to compound.

Published 2026-08-281,055 words~5 min readVenue Economics

Somewhere under your events runs a quiet stack of recurring charges: the booking platform, the accounting software, the e-signature tool, the phone line, the website host, the cloud storage, the payment processor's percentage of everything. None of it decorates a single event, all of it bills every month, and almost no operator can state its total, let alone its total per booking, which is the number that makes it manageable. This article is the audit.

1. Why per-booking is the right denominator

Admin costs are fixed-ish: they arrive whether you host two events or twenty. Stated monthly, they hide inside the fixed pile of the break-even algebra and feel like weather. Stated per booking, they become a price you're paying for the privilege of processing one contract: comparable directly against what that contract contributes, and against what the same function would cost done differently. A stack that costs little per booking at full calendar can quietly become the most expensive line per booking at a slow one; the denominator is what makes that visible.

2. The audit: one hour, four columns

Pull twelve months of bank and card statements and list every recurring charge that isn't rent, payroll, insurance, or utilities. For each: what it costs annually, what job it does, what would break if it vanished tomorrow, and which other line already claims to do the same job. That last column is where the money is: back offices accumulate overlapping tools the way kitchens accumulate knives, and the pairs (two form builders, the booking platform's e-sign plus the standalone e-sign, storage bought twice) cancel painlessly.

Same stack, two very different taxes on a contract, and notice which line dwarfs the subscriptions everyone argues about. The SaaS pile totals a fraction of what the payment processor collects.

3. Card fees: the stack's biggest line, and the most negotiable-by-design

Processing fees may include percentage, per-transaction, monthly, and other charges. Their total can be material at venue invoice sizes, so measure the effective rate from statements:

• Route big payments cheaply. Venue invoices are large; a final balance paid by bank transfer instead of card can cut the fee on that payment dramatically. Offer the cheap rail for balances while keeping cards for deposits, where convenience wins bookings.
• Price with fees inside. Your cost floor should carry the processing percentage explicitly. Surcharging clients is regulated differently across US states and Canadian provinces and can sour a luxury purchase. Pricing it in is cleaner than fighting about it.
• Reconcile monthly. Effective rate = fees ÷ volume, computed from the statement. Processors' quoted rates and effective rates drift apart through downgrades and add-ons; the reconciliation is how you notice.

4. Subscriptions: rules that keep the pile honest

• Annual re-justification. Every tool re-earns its line once a year in the audit; the default is cancellation, and renewal requires the "what breaks" column to say something real.
• One job, one tool. Overlap is the stack's compound interest. When two tools share a job, the better one absorbs it that month.
• Count the seats. Per-seat tools accumulate departed staff and forgotten logins. Seats are the quietest waste in the pile.
• Beware the platform ratchet. All-in-one booking platforms consolidate jobs, then raise prices, knowing your workflows are inside. The counterweight is a once-a-year honest note of what migration would cost; pay a ratchet knowingly or not at all.
• Buy back time, not features. The test for adding a tool is hours actually saved times a real hourly value, compared against the subscription. "Nice" is not a column in the audit.

5. The labor hiding beside the stack

The stack's dollars are only half the back office; the other half is administrative labor: invoicing, chasing signatures, reconciling, replying. The same audit applies: hours per booking, priced at a loaded rate, added to the per-booking figure from §2. This is where tool decisions become honest: software that costs more but genuinely deletes hours can lower the true per-booking number while raising the visible one, and the reverse, cheap tools that manufacture manual work, is more common. The per-booking admin total, dollars plus labor, belongs in your per-event thinking the same way acquisition cost does: it's part of what a contract truly costs to hold, not just to win.

6. Bookkeeping: the stack's one strategic line

Bookkeeping deserves particular care because lenders, buyers, tax authorities, and managers may rely on its output. Compare an in-house process with professional support using complexity, skill, controls, timeliness, and total cost. Software plus a periodic close by a qualified professional is one possible configuration, not a universal cheapest choice.

Whatever configuration you choose, hold it to a venue-shaped chart of accounts: deposit liabilities separated from earned revenue (the distinction that the cash-trap article is built on), add-on revenue separated from rental revenue, and event-variable costs separated from fixed, because the ledger's categories are what make the per-event, break-even, and utilization arithmetic fall out of the books automatically instead of requiring a special project every time you want to know something.

And keep the audit itself boring: same spreadsheet, same categories, every year, so the trend line means something. The interesting version of this exercise is not any single year's total. It's watching per-booking admin cost move against booking count over three years, which tells you whether your back office is scaling like infrastructure or growing like a hedge.