Structural Advantage
Summer Is When You Fix the Plumbing
The quiet weeks between the summer season and the autumn conference run are the only time you can change how your business works without breaking a live event. Here is what to do with them.
The gap nobody schedules around
Most events businesses have a fortnight or so, somewhere between the last summer wedding and the first conference of the autumn run, where the calendar goes quiet. Not empty. Quiet.
It is the worst possible time to take a proper holiday, because everyone else has already had theirs and is asking where you are. It is also, and this is the useful bit, the only stretch of the year when you can change how the business actually works without risking a live event while you do it.
January does not work for this. In January everyone has opinions and no energy, and the first big brief of the year lands before you have finished the conversation. August works, if you use it on purpose.
Why a repeated small saving is worth more than it looks
Here is the arithmetic, done honestly rather than rounded up to make a better headline.
Say you trim twenty minutes off a task someone does twice a week, an event brief that used to need chasing three times to get the numbers right, a quote template that used to need retyping instead of adapting. Twenty minutes, twice a week, is forty minutes a week for that one person.
Now say four people in the business do a version of that same task. Forty minutes each, across four people, is two hours forty minutes a week, team wide.
A realistic working year, once you take out holiday, bank holidays and the odd quiet week, is somewhere around forty six weeks. Two hours forty minutes a week across forty six weeks is a little over a hundred and twenty two hours a year. That is roughly fifteen full working days, every year, from now on, from fixing one repeated task properly, once.
It does not feel like fifteen days when it happens. It feels like nothing happened at all, which is exactly why nobody notices it and nobody schedules time to go looking for it.
Three jobs for August, not twelve
The temptation in a quiet fortnight is to try to fix everything. Resist it. Three jobs, done properly, beat twelve started and abandoned when the autumn diary fills back up.
- Write down the quoting process, as it actually happens. Not the process on the induction slide from three years ago. The one where Dev always adds ten percent because the supplier always comes back higher, and Priya always checks availability first because she got burned once. Write down what people actually do, including the workarounds, because the workaround is usually the real process wearing a disguise.
- Decide what each CRM stage actually means. Most teams have a CRM where "Proposal Sent" means something different depending on who moved the card. Get the team in a room for forty minutes and agree, in one sentence each, what has to be true for a lead to be in each stage. Write it somewhere everyone can see it. This is unglamorous and it is the single most valuable hour most teams could spend in August.
- Build one reusable prompt per role. Not a company-wide AI policy, not a tool rollout. One prompt, written with the person who does the job, for the task they do most often and dread most. A supplier chaser. A first-draft brief summary. A debrief. Test it on a real job from this summer, not a hypothetical one, and keep editing it until the person who will use it says it is actually useful.
Three jobs. Written down, agreed, and tested against something real, by the time the first September conference lands.
Why this compounds and the shouting-loudest crowd never notices
There is a lot of noise in events right now about AI, most of it either breathless or dismissive, and almost none of it about this. The people shouting loudest about transformation are usually selling a platform, and the people rolling their eyes are usually right to be sceptical of the platform, because the platform was never the problem.
The quoting process, the CRM stage definitions, the prompt per role, none of that is a system launch. Nobody makes an announcement about it. There is no leadership offsite with a keynote. It is a fortnight of unglamorous decisions that nobody outside the business will ever see, which is exactly why the businesses that do it well look, from the outside, like they simply have less chaos than everyone else.
That is the whole advantage. Not a bigger platform. Fewer things breaking quietly, week after week, that everyone had simply stopped noticing.
Pick one and start there
If three feels like a lot, pick one. The CRM stage conversation is the cheapest to run and the fastest to pay off, forty minutes in a room this week.
If you want a second pair of eyes on where the real time is leaking before you decide what to fix, that is what a Discovery Lab is for, a set of structured conversations with the team followed by a written report showing exactly where the minutes are going. More on that here. And if the prompt-per-role idea is where you want to start, there are working examples already on Zoby OS.