Run a restaurant almost anywhere in the country and summer is the good news — patios full, tourists in town, the long light doing your marketing for you. Run one in Scottsdale and Phoenix and the calendar is upside down. Here, summer is the off-season: 110-degree afternoons empty the streets, the seasonal residents are gone, and the dining room a group built its numbers on can go quiet for months. The money is made in the winter, and the summer has to be survived. That single inversion bends nearly every operating decision a Valley operator makes — and the groups that struggle are almost always the ones who built for a calendar the Valley doesn't run.
Why summer empties the Valley
The heat does the obvious part — when it's 110 degrees at 8 p.m., foot traffic and patio covers collapse, and a lot of the casual, walk-the-district demand simply stops. But the bigger driver is who leaves. Scottsdale and the North Valley run heavily on seasonal residents and winter tourism — snowbirds, resort guests, the golf-and-spa economy — and most of that population is gone by June. A dining room that felt discovered and effortless in February can feel abandoned in July, not because anything about the food or the service changed, but because a large share of the guest base physically left town. The demand didn't dip. It migrated.
Winter money has to carry the summer
That reframes the whole year. In a normal market you're trying to make every month pull its weight. In the Valley, the season — roughly November through April — is where the year gets made, and summer is a stretch you're trying to get through without giving it all back. But the fixed costs don't take summer off. Rent is the same in July as in January. The experienced GM and the sous chef you can't afford to lose are still on payroll. The question that decides a Valley operator's year isn't "how good was the season" — most groups have a good season — it's "how much of the season did the summer eat." Groups that plan for a twelve-month calendar with two very different halves hold their margin. Groups that spend the season like it's the run rate get caught every summer.
The Phoenix summer breaks operators on the labor line
The hardest line to run through the inversion is labor, and it's a trap in both directions. Staff for peak-season volume and carry it into July, and you're paying a full team to stand in an empty room — the fastest way to turn a survivable summer into a bleeding one. Cut too hard and too fast, and you lose the experienced people you need back on the floor in October, so you limp into the season understaffed and retraining while the money's actually on the table. The operators who get this right treat the labor model as something that flexes with the calendar by design — a core team protected through the trough, a flexible layer that scales down for summer and back up for the season, and a schedule built to the covers each month actually delivers, not to an annual average that never happens. A labor model tuned to the season's volume is a liability for half the year; one tuned to the summer's is a liability for the other half. The Valley demands one built for both.
Two guests make the swing worse — or better
The Valley is really two markets sharing one metro, and the seasonal swing hits them differently. Scottsdale's resort-and-wealth economy — Old Town, the Kierland and Fashion Square corridor — runs on exactly the seasonal-resident and tourist money that disappears in summer, so a Scottsdale-weighted group feels the trough hardest. Phoenix proper, and the value-driven family suburbs like Chandler and Gilbert, lean on a year-round local guest who doesn't fly north for the summer — a shallower peak, but a far more durable July. This is why a group can't read its Valley exposure off a consolidated P&L. A portfolio weighted toward resort-season checks is running a completely different risk than one anchored in year-round suburban volume, and the two need different labor models, different pricing, and different summer programming. Knowing which Valley each unit actually sits in — resort-seasonal or year-round-local — is the first move, because it decides how brutal the summer is going to be before you've done anything about it.
Build for the year, not the season
Surviving the Phoenix restaurant summer isn't about a clever July promotion, though summer restaurant weeks, locals' pricing, and leaning into the value guest all help. It's structural. It's a labor model that flexes down through the trough without gutting the team, a cash position that treats summer as a planned cost of the year rather than a surprise, a guest mix that doesn't depend entirely on the season, and — most of all — expansion math that underwrites a location on its annual number, not its February one. A group that opens a second and third unit on the strength of one great season, without proving the model survives a summer, is just multiplying its July exposure. The Valley will keep handing you a magnificent winter. Whether the year is any good comes down to what you built for the months nobody's here. Better restaurants are built, not born — and in a market that runs its calendar backwards, so is a year that holds up all twelve months.
Written by the operator behind RANGE — two decades inside multi-unit restaurant operations, P&L responsibility through the COO chair, most of it in 5-to-25-unit groups. The work, in numbers →
If this is the conversation your operation needs, bring us the problem.
Get in Touch →