If you run a seasonal business in Santa Cruz, you already know the rhythm. Somewhere around late May, the town shifts. Traffic on 17 backs up earlier. The parking lot at Natural Bridges fills by 10am. And your calendar, which was comfortable in April, turns into a fire drill that does not let up until Labor Day.
Then October arrives, and the town exhales, and your schedule has a silence in it that feels like the power went out.
This is the operational reality of running anything here that catches summer traffic or UCSC flow. The revenue graph looks like a wave, not a line. And most of the business problems seasonal owners wrestle with are not really seasonal problems. They are design problems. The operation was built for one of the two seasons, not both.
The two-season trap
The pattern looks like this. Summer hits, you are suddenly doing 30 to 40 percent more volume than your systems were designed for. You run hot. Quality slips in the places nobody is watching. The team works longer hours because there is no way to shortcut the work. You make more revenue, but you also burn a lot of it on overtime and mistakes.
Then fall lands. Revenue drops. You cannot carry the staff you hired for summer. Some of them leave. The ones who stay are underworked, which is its own problem. Cash flow gets tight. You spend the winter rebuilding the runway you should have built in August.
Next May, you scramble to hire. You train green people in the middle of the rush, which makes the rush worse. And you run the loop again.
You are not doing anything wrong in that loop. You are running a system that was built for steady volume and taking the hits every time the wave comes in or goes out.
What a system that actually flexes looks like
The Santa Cruz operators I see handling this well did not invent anything exotic. They just designed for the wave instead of fighting it.
They keep a core team year-round, sized for winter revenue plus a small buffer. That is the baseline. Then they layer seasonal staff on top for the rush. The core team is the institutional memory. They know the systems. They can train the seasonal hires without it derailing the business, because they are not also trying to learn the job themselves.
They do the systems work in winter. Documentation, process cleanup, tool changes, onboarding materials, the SOPs everyone said they would write and never did. This is what winter is for. If you spend the slow months just trying to survive, you will hit next summer with the same half-built operation and the same outcome.
They pre-build the summer onboarding before summer arrives. Training decks, checklists, the first-week walkthrough for a seasonal hire. When May comes and you are interviewing, you want to hand a new person a clear plan, not a shrug and "you will pick it up." Deming used to say you should never send anyone into a job without the training to do it well. That applies double to seasonal staff, because you do not have the months to let them figure it out.
And they manage cash like the wave is real, because it is. A rough rule I see work: during the peak months, move 20 to 30 percent of revenue straight into a separate account the business does not touch. That is the cash that carries you through the slow side. It is not profit. It is runway.
The Lean piece
Toyota built the Production System to handle variable demand without breaking the line. The core idea is that the system has to flex without losing quality, which only works if the work is standardized enough that you can onboard new people fast and catch defects quickly.
For a seasonal Santa Cruz business, the same idea applies. If every summer hire has to learn a different version of the job depending on who trains them, quality will slip during the rush, and clients will notice. If the work is standardized, a good seasonal hire can be doing useful work by the end of week one instead of week three.
Standardization here does not mean making everything rigid. It means making the pieces that have to be consistent, consistent. What the client experience is supposed to feel like. How a common question gets answered. What "good" looks like on a standard piece of work. The rest can stay loose.
The common mistake
The move I see people regret most is staffing up for summer without a plan for October. You hire people who have bills to pay, and you tell yourself you will find a way to keep them year-round. Then the revenue math does not work in November, and you end up cutting hours or letting people go, which burns the goodwill you built with them in July. Next year, the ones who felt burned do not come back, and you are training a new cohort from scratch.
Design the staffing model around the full year, not the peak. Hire your core team for winter volume. Be transparent with seasonal hires that the role is seasonal. Some of them will want exactly that. The ones who are good and who also want year-round work are the ones you promote into the core team next spring, which is the healthiest hiring pipeline you will ever have.
Monday
Open a blank doc. Put two columns: summer month and winter month. For each, list the revenue range, the headcount you need, the hours the team works in a normal week, and the three things that break when you run that pattern.
That is your diagnostic. The gaps between the two columns are where the system does not flex. Pick the biggest gap. That is what you work on this month.
If it is staffing, start with the pipeline. If it is cash, start with the reserve account. If it is quality under load, start with the SOPs for the two or three tasks that get hammered during the rush.
One gap at a time. One season at a time. In a year you will not recognize the operation.
The point
Seasonality is not a problem to solve. It is a shape to design around. The businesses that thrive through both sides of the wave are not the ones that pretend it is not happening. They are the ones that built an operation that flexes on purpose, with a core team that stays, a seasonal layer that scales, and a cash pattern that uses the peak to fund the trough.
If you want help mapping where your operation is rigid when it needs to be flexible, a Flow Check is a two-week diagnostic designed for exactly that. You come out with a clear picture of which systems break under seasonal load and what to build first so next summer does not flatten you.