Most new hospitality businesses fail not because of bad food or a bad location, but because they open without the operational foundations in place. The kitchen might be ready. The menu might be great. But if the team doesn't know the opening routine, there's no cash reconciliation process, and prep standards are communicated verbally on the day, you're starting from a deficit.
Here's what you actually need before the first paying customer walks through the door.
1. A documented opening and closing routine
Every member of your team needs to know exactly what happens at the start and end of every shift — and that knowledge should exist on paper, not just in your head or the head of your most experienced staff member.
Your opening SOP should cover: unlocking, temperature checks, machine warm-up, prep tasks by station, till setup, and the visual standard check before doors open. Your closing SOP should cover: till reconciliation, waste logging, cleaning schedule, stock count, and lockdown procedure.
These don't need to be long. A single laminated page per routine, role-specific, is more useful than a 20-page operations manual nobody reads.
2. Portion specs before prep begins
The first week of trading sets habits that are extremely difficult to break later. If your team starts eyeballing portions from day one, that becomes the standard — and your food cost will be unpredictable from week one.
Before you open, write a spec card for every dish: weight in grams for key components, a photo of the finished plate, and the cost per portion. Print them, laminate them, and put them in the prep area. This is how you protect your margin before you've even started to trade.
3. A till system and cash reconciliation process
Choose your EPOS system before you open, not on the first day of trading. Set up your product catalogue with correct categories and prices. Know who has access to voids and refunds, and make sure that's documented.
Your cash reconciliation process should happen at the end of every service — not weekly, not monthly. Daily reconciliation catches discrepancies while the context is still fresh. A simple sheet or a spreadsheet is fine at the start.
4. A pre-opening checklist
The 21 days before opening are when most of the controllable problems occur. Equipment that hasn't been fully tested, suppliers who haven't confirmed their first delivery, staff who haven't been properly trained on the menu.
A dated, task-by-task checklist with a named owner for each item turns that 21-day window from a period of mounting anxiety into a structured process. It also identifies dependencies — the things that can't happen until something else is done — before they become day-before crises.
5. A soft launch before your public launch
Open for friends, family, and invited guests before you open to the public. This is not an optional nice-to-have — it is the most effective way to discover operational problems in a low-pressure environment.
Run two or three soft launch services with a deliberately reduced menu. Observe your team, time your tickets, note everything that goes wrong. Fix it before the reviewers come. The operators who skip this step often spend their first public week correcting problems that a single friends-and-family service would have surfaced.
6. A KPI framework for week one
Before you open, decide what you're going to measure. You don't need ten metrics. You need five:
- Average transaction value — are guests spending what you projected?
- Covers or orders per hour — is your throughput close to your capacity model?
- Ticket time — how long from order to delivery, and is it consistent?
- Food cost % — calculated weekly from day one, not when you feel like it
- Review volume and rating — start generating reviews from week one
These five numbers tell you whether your launch is on track. Without them, you're navigating by feel.
The week-one correction cycle
No matter how well you prepare, the first week will surface things you didn't anticipate. That's not failure — it's the function of a soft launch and a week-one review.
At the end of week one, sit with your team and work through: what went wrong, why it went wrong, and what changes. Document the changes. Implement them before week two. This cycle — observe, diagnose, fix, repeat — is what separates operators who stabilise quickly from those who spend six months firefighting.
The most common thing I hear from operators after a difficult launch: 'We knew we weren't ready, but we felt like we had to open.' The solution isn't to delay indefinitely. It's to use the time you have before opening as well as possible.
The Launch Smart package is built around exactly this — 4 weeks of structured pre-opening and early stage support for independent UK operators.