Structural Advantage
Start 2026 with a Systems Audit, Not a Software Purchase
January is when event businesses buy new software to feel like they are modernising. The fix is rarely the tool, it is the workflow underneath it that nobody has written down. Run this four-step audit first.
The January reflex
Every January, event businesses do the same thing. Someone comes back from the Christmas break with a bit of energy, looks at the year ahead, and decides this is the year things get modern. A CRM gets shortlisted. A new proposal tool gets a free trial. Someone asks whether AI can "help with the admin."
None of that is wrong. But it is usually early.
Buying a tool before you understand the process it sits on top of is how a forty-person agency in the Midlands ends up with three CRMs running at once, each one championed by a different department, none of them trusted enough to be the single source of truth.
The tool is not the problem
Almost every event business I have sat down with has a version of the same shape underneath. A brief comes in. Someone costs it. A quote goes out. It gets won. It gets handed to delivery. The event happens. Someone reconciles the numbers afterwards, usually late, usually from memory as much as from records.
Each one of those handoffs is a place where information gets rekeyed, guessed at, or lost. New software rarely removes a handoff. It just gives the same handoff a nicer interface. If nobody has written down what actually happens at each step, the new system inherits the same gaps as the old one within about six weeks.
This is the bit that gets missed: a workflow nobody has documented is a workflow nobody can fix. You cannot improve what you have never actually looked at end to end.
A four-step audit you can run this week
This takes half a day, not a project plan. You need one job, one person who does it weekly, and a notepad.
- Pick one job that happens every week. Not the whole business. One thing: brief intake, quoting, supplier confirmation, invoice reconciliation. Pick whichever one makes people sigh when it comes up.
- Walk it end to end with the person who actually does it. Not the manager's version of how it works. The real version, including the workaround nobody put in the process doc because there is no process doc.
- Count the handoffs and the re-keying. Every time information moves from one person, system or spreadsheet to another, that is a handoff. Every time someone retypes something that already existed somewhere else, that is re-keying. Write down the number.
- Put a rough time cost on it. Not a scientific one. Ask the person doing it: how long does this take you, on a normal week versus a bad week. Multiply by how often it happens. You will have a number nobody in the leadership meeting has ever said out loud.
What this actually finds
Run this on a quoting process and you will usually find the same things. A spreadsheet that only one person really understands. A capacity figure for a venue that exists in two places and disagrees with itself. A "final" version of a proposal that gets edited after it was marked final. None of these are software problems. They are structure problems wearing a software costume.
A conference venue in the north west ran this audit on their event handover process last year and found that the same booking details were typed into four different places by three different people, and that the version delivery actually used was the one with the most typos, because it was the one that got updated last.
That is not a people problem. Nobody there is careless. It is what happens when a process grows organically for a decade with no one owning the whole shape of it.
Where AI actually fits
Once you can see the workflow clearly, AI becomes genuinely useful, because you can point it at a specific, bounded step rather than the vague hope that it will "help with the admin." Summarising a brief. Drafting the first pass of a quote from a template. Flagging when a capacity figure looks inconsistent across documents. These are small, unglamorous wins, but they are real ones, and they only work once the underlying process is clear enough to automate a piece of it without automating the chaos along with it.
Skip the audit and you get an AI tool confidently doing the wrong version of the process, faster.
This is the mistake I see most often with in-house event teams especially. Someone senior asks the whole department to "start using AI more." Without a clear picture of where the actual bottleneck sits, everyone reaches for the same generic assistant and applies it to whatever is in front of them that day. A few people find something genuinely useful. Most drift back to the old way within a month, because the tool was never aimed at the step that was actually costing time.
Fix the plumbing before you buy the tap
None of this needs a consultant, a project code, or a slide deck. It needs half a day, one honest conversation with the person who does the job, and a willingness to write down what you find even when it is unflattering.
Do that before you sign anything new this year. The tool you eventually buy, if you still need one, will be a much better fit once you know exactly what it needs to fix.
If you want a structured version of this across a whole team rather than one process, that is what a Discovery Lab is for.