Skip to content
RANGE

Jon PeckDevelopment & ExpansionJuly 13, 20264 min read

The first 90 days of a new restaurant produce more bad decisions than any other stretch of a concept’s life, because operators treat them as the verdict when they’re the data. Every number in that window is still moving: the staff is new, the kitchen hasn’t found its rhythm, and the guest base is skewed toward first-time and curiosity traffic that thins out long before the real trade area settles in.

The discipline that separates groups that open well from groups that open lucky comes down to three rules: observe like a scientist for ninety days, build the critical path before the crowd shows up, and refuse to judge the opening (good or bad) until a full year has run.

Ninety days of watching

The most useful posture in a new restaurant is to observe. Not fixing everything in real time. Watching, almost to a fault: where guests gravitate, which seats get requested and which section dies, where the flow of the room snags, how the lighting behaves at 8pm versus the walkthrough, what gets sent back and what gets photographed.

Numbers move fast in the first ninety days and settle slower than anyone wants; a single bad Saturday means nothing, but the same pattern showing up four Saturdays running is the system telling you something real. Nitpick everything; change carefully. Some of what looks broken in week three is merely settling; the operator who starts ripping out the concept in month two is often destroying the parts that were about to work. Log it all. Fix in sequence, not in panic.

Tell us what’s breaking.

The fastest way to find out whether RANGE can help.

Book a call with Jon (opens in a new tab)

The log is one page, filled in every shift

Five columns, filled in before anyone goes home:

  • Ticket times by station, not the kitchen average, which hides the one station dragging every ticket behind it.
  • Comps and voids by shift, with the reason: the earliest read on what the kitchen and the dining room are getting wrong.
  • Table-turn times against the reservation pace: the number that says whether the book you’re building matches the room you have.
  • Quoted wait versus actual wait: the gap is the promise you’re breaking at the door, and it compounds into reviews faster than anything on the plate.
  • Seat requests and seat refusals: where guests want to sit and where they won’t is the room telling you which sections are mispriced, mislit, or dead.

The critical path starts before the doors do

Most of what breaks in week one was decided months earlier. Groups that open cleanly build a critical path that sequences hiring, training, and systems backward from opening night. Not a checklist run in parallel with construction, but a schedule where each piece has to be done before the next one can start.

Key managers hired and trained early enough to help run the opening, not still learning their own job during it. Line checks, prep pars, and open/close routines built and drilled before the first paying guest, not improvised in week two because nobody had time before. A staffing plan padded for the inevitable (no-shows, early-week burnout, a trainer who has to leave the floor to fix a problem) instead of scheduled to the bone on the assumption everyone shows up and performs like a veteran.

Groups that skip this usually get through opening week on adrenaline, and spend the next two months paying the interest.

The kitchen will fight you. That’s normal.

The first few months of food and kitchen execution are difficult for every opening, every time. And anyone who claims otherwise is lying. Getting the kinks out of a kitchen (line flow, fire times, consistency across a full crew of people who’ve never worked a service together) is the hard part of the trade.

Ticket times that looked fine on a training-week walkthrough with six covers an hour come apart at forty. Dishes a chef nailed a dozen times in prep drift the moment two stations are firing under real pressure.

Plan for it: extra senior coverage on the line through the first month, not just the first weekend; a menu that opens tighter than the ambition, with the complicated builds phased in once the brigade can hold a full room; and chefs given room to fix rather than defend, because a kitchen leader protecting his ego instead of his ticket times will hide the exact problems that need fixing fastest. The mistake isn’t having kitchen problems in month one; it’s the opening budget and staffing plan that pretended you wouldn’t.

No verdict for a year, in either direction

The under-appreciated half of the one-year rule is the hot start. A restaurant that opens packed is the most dangerous kind, because everyone around it starts celebrating, and the improvement work stops without anyone deciding it should, and the slide that follows buzz is slower and harder to reverse than a soft launch.

Most new units need something like twelve to eighteen months to reach a stabilized run rate, and the road there is rarely a straight line: an opening spike from curiosity traffic, a dip once the first-timers stop coming and the real trade area shows up, then a slower climb as word of mouth and repeat visits build the base the concept will run on.

Read the wrong month as the verdict and you’ll either cut a program that was about to work or pour more into one that was only ever a honeymoon. The best operating answer to “it’s going great” is: we’ll see in a year. Until then, both the highs and the lows are noise. The ninety-day log and the ramp curve are the signal; the mood in the room on any single week is not.

Openings reward temperament as much as capital. The groups that scale openings aren’t the ones that open perfectly. Nobody does. They’re the ones with a system for what happens after the doors open, and the patience not to grade the test before the year is over.

Written by Jon Peck, founder of RANGE: two decades inside multi-unit restaurant operations, P&L responsibility through Chief Operating Officer.