Seasonal businesses have about eleven weeks, and they are not the weeks that matter

Almost all business advice assumes you have next month

The standard advice for improving a business assumes a steady state. Test something, measure it, adjust, run it again. That works when there is always another month.

In a compressed year there is no another month. You get one run at it. A test that takes six weeks to read consumes half your season, and by the time you have the answer the conditions that produced it are gone for a year.

• Iteration is a luxury you do not have. Anything that needs several cycles to tune has to be tuned before the season, on last year's data, or not at all.
• Mistakes do not get corrected, they get carried. A bad decision in week two of a season is lived with for the remaining nine and then remembered inaccurately by the time next year is planned.
• Your busiest weeks are your least capable weeks. The moment you most need to be sharp about the business is the moment nobody has a spare hour, which is exactly backwards and entirely structural.
• Averages describe nobody. Monthly numbers are meaningless in a business where two months carry the year. Anything measured has to be measured against the same point in a previous season.

The season is decided before it starts

This is the part that gets missed, and it is the reason a seasonal business is not simply a normal business with a shorter opening.

The work that determines how the eleven weeks go happens well before them. Bookings for a summer camp are made in February. A wedding supplier's season is largely sold the previous autumn. A snow contract is signed in September. A tour operator's international guests are planning months ahead, from a different time zone, in the evening.

So the enquiry volume is not shaped like the revenue. It arrives earlier, often much earlier, and it arrives at a point in the year when the business is least staffed to handle it.

You cannot hire your way through a peak

The obvious answer to a compressed year is temporary staff, and everybody tries it, because it is the only lever that is visible.

It works for the parts of the job that can be learned in a day. It works badly for everything else, and the reason is arithmetic rather than attitude. Somebody hired for a short season reaches competence somewhere near the middle of it and leaves at the end. You pay the training cost every single year and you never get the compounding.

• The training burden lands on your best people. During your busiest weeks. This is the hidden cost that never appears in the calculation.
• Judgement cannot be hired seasonally. Knowing which enquiry to prioritise and which customer to call back first is the accumulated knowledge of several seasons.
• The front door is the worst place to put an inexperienced person. It is where the year's revenue arrives, and it is usually the first job handed to whoever started on Monday.
• Seasonal staff are hardest to find in exactly the industries that need them most. Because everyone in the region is hiring for the same weeks.

What a seasonal business should actually build

The systems worth building for a compressed year are not the same ones a steady business would prioritise, and the difference is worth being deliberate about.

1. The front door, first and always. Enquiries answered at the hours they arrive, in the months they arrive, including the quiet ones when nobody is watching the phone. This is the single highest value thing a seasonal business can automate, because the enquiry that decides your July arrives in March.
2. The long follow-up. A booking decided months in advance needs contact across that gap, and manual follow-up over four months is precisely the thing that does not survive a busy week. It is also what stops a deposit turning into a cancellation.
3. Pre-arrival and preparation collection. Documents, details, forms, consents, sizes, requirements. All due before a date, all currently chased by hand in the fortnight when you can least afford it.
4. Capacity visibility against the curve. Not how many bookings you have, but how many you have compared to this point in previous seasons. This is the number that tells you to act while acting is still possible.
5. The wind-down capture. A structured way to record what went wrong while it is still fresh, because by the time you plan next season nobody remembers accurately.
6. Off-season contact. The list you built in July, spoken to in January, when people are actually planning. Most seasonal businesses have this list and have never once used it.

What to switch off, and what to leave running

A fair objection to all of this is that it is a lot of machinery for a business that is closed half the year. It is worth answering directly.

Some of it should be seasonal. Campaigns, promotional sequences and anything tied to a specific offer get scheduled to the season and stop outside it. There is no reason to be messaging people about something that is not running.

Most of it should stay on. Enquiry answering, record keeping and follow-up cost close to nothing to leave running, and the entire argument of this piece is that the off-season enquiry is the one that decides the season. Switching off the front door in February is switching it off at the moment it matters.

• Leave on: anything that answers a person. The cost of it running through a quiet month is negligible and the cost of missing one enquiry is not.
• Leave on: anything that records. The data you collect out of season is what makes the in-season comparisons possible.
• Schedule: campaigns and offers. Tied to the season, off outside it.
• Adjust: the wording, not the system. Out of season the honest message is when you open and how to book ahead, which is a change of copy rather than a change of machinery.

The mistake almost everybody makes

They decide to fix it during the season.

It is completely understandable. The season is when the problem is visible, when the pain is acute and when the motivation exists. It is also the worst possible time, for a reason that has nothing to do with the vendor.

Building anything requires your attention: answering questions about how the business actually works, deciding what the system should say, testing whether it behaves correctly. During your peak weeks your attention is the most valuable and most scarce resource in the business. Spending it on a project means either the project gets a bad version of you, or the season does.

If you are reading this in your quiet months

Then this is the window, and it is worth being direct about what to do with it.

Start with the front door. Enquiries answered fast, at the hours they arrive, all year. It is a short project and it is the one that pays for the rest.

Write down the answers while you have time. The forty questions customers ask and the answers to them. It is the prerequisite for everything else and it is genuinely pleasant to do in February and impossible to do in July. The format is in the context sheet.

Work out which job is actually worst. The automation scanner ranks them against how your week runs, and for a seasonal business it is worth answering as your season looks rather than as this week looks.

Then build one thing properly. The staged version, with a test for when each stage is done, is in the ninety day roadmap, and ninety days from a quiet month lands you before the run-up, which is the entire point.