Structural Advantage
Your CRM Is a Graveyard, and That Is a Data Problem, Not a People Problem
Fields that mean different things to different people, duplicate venues, notes buried in WhatsApp. AI built on top of a messy CRM just gives you confident nonsense faster. Here is how to fix the structure, not buy a new system.
Every events business has one
Open most CRMs at an events agency or a venue and you will find a graveyard. Contacts nobody has touched in three years, still marked "active." Three versions of the same venue, one spelled slightly differently, none of them holding the full picture. A "notes" field with the only record of a conversation that actually mattered, buried under forty other notes that did not.
This is not a rare, badly run business problem. We see it almost everywhere we look, including at businesses that are otherwise sharp, well run and growing. A CRM does not become a graveyard through neglect. It becomes one because nobody ever agreed, in writing, what the fields were actually for.
The root cause is not the system
Swap the CRM out for a shinier one and the graveyard usually follows you within a year, because the tool was never the problem. The problem is that "stage" means one thing to sales, another to finance, and a third to whoever is filling it in on a Friday afternoon trying to clear their inbox before the weekend.
A field with no shared definition is worse than an empty field, because it looks like data. Someone will build a report off it. Someone will make a decision based on that report. The decision will be wrong in a way that is very hard to trace back to its source, because on the surface, everything looked filled in and tidy.
Duplicate venues and the WhatsApp problem
Two patterns show up constantly. The first is duplicate venues: the same venue entered separately by two different people, at two different times, with two different capacity figures, neither one confidently more correct than the other. Nobody notices until someone quotes off the wrong one.
The second is what we call the WhatsApp problem. The actual, operational truth of what was agreed with a supplier or a client often lives in a phone, in a thread, not in the system that is supposed to be the record. The CRM holds the tidy version. The group chat holds the real one. Anyone relying purely on the CRM is working from a summary that quietly leaves things out.
Why AI makes a messy CRM worse, not better
This is the part that catches people out. AI does not fix a messy foundation, it builds on top of it, confidently. Ask an AI assistant to summarise your pipeline, draft a client update, or flag which events are at risk, and it will do exactly that, using whatever is actually in the fields it can see.
If "confirmed" means three different things across your team, the AI will not notice, because it has no way to know that. It will produce a clean, well written, entirely confident summary built on a definition that does not actually exist. That is a genuinely worse outcome than a human quietly ignoring the field, because it looks authoritative. Structure has to come before automation, not after it, or you get nonsense with better formatting.
We have seen this play out with a supplier database at a forty-person agency in the Midlands. Two suppliers had been entered under near-identical names, one with a note about a pricing issue from two years ago, the other clean. An AI-generated shortlist for a new event pulled the clean record, because nothing in the data told it they were the same company. The formatting was excellent. The recommendation was wrong for a reason nobody could see just by reading it.
Fix the structure, not the software
None of this needs a system migration. It needs an afternoon and some discipline.
- Define five stages, one sentence each. Not fifteen. Five, written down, agreed by sales, finance and delivery in the same room, so "confirmed" means the same thing to everyone who types it.
- Pick the ten fields that actually matter. Not the forty that exist. Ask what a report genuinely needs to be trustworthy, and archive the rest rather than deleting it, so history is not lost, just no longer cluttering the view.
- Run a thirty-minute weekly hygiene ritual. One person, one CRM view, thirty minutes. Close duplicates, chase blank required fields, move stale records out of the active pipeline. It is boring. It is also the single highest-leverage half hour most teams could spend.
Start with what "in the CRM" is supposed to mean
Before you touch a single field, agree one thing as a team: what belongs in the CRM, and what does not. Not every message with a supplier needs to be logged. But the outcome of that message, the price that was agreed, the date that was confirmed, does. Draw that line clearly and the WhatsApp problem shrinks on its own, because people stop treating the CRM as optional paperwork that happens after the real conversation, and start treating it as the record the real conversation was always meant to produce.
This is not an argument for a new CRM
We are not telling you to rip out your system and buy another one. Most of the CRMs event businesses already own are perfectly capable of holding clean data. What they are missing is agreement, not features.
Do the five-stage exercise this month, before you let anyone build an AI workflow on top of what is in there now. If you want help finding exactly where your data is quietly lying to you, that is a core part of what comes out of a Discovery Lab.