Hospitality Operations Consulting · Los Angeles
Most consultants study restaurants.
This one ran them.
Restaurant operators invest in great food, great staff, and great spaces — then hand critical business decisions to systems they never fully configured and compliance frameworks they inherited from someone else.
The result: labor that bleeds margin through misclassification and scheduling inefficiency. Technology stacks generating data nobody reads. Compliance exposure that surfaces only after someone gets hurt.
The gap isn't ambition. It's translation — between the tools operators have and the decisions those tools should be driving.
Each engagement is structured to get to a decision — not a deck. Clients choose a track based on their most urgent exposure. Most end up using more than one.
Your POS generates thousands of data points every shift. Your labor system, your invoice platform, your reservation software — all of it sits in silos. This track builds the connective tissue: custom dashboards, cross-platform reporting, and the operational logic that turns raw exports into decisions.
California hospitality compliance is a moving target. Tip pooling rules, break premium liability, predictive scheduling, minor work permits, classification — most operators learn about their exposure after the complaint, not before. This track puts a practitioner in your corner before that happens.
Most new venues fail in the first 90 days not because the concept is wrong, but because the operational infrastructure wasn't built before the doors opened. This track puts someone with a substantial track record of successful openings in your corner before you sign the lease on your labor model — not after your first bad payroll run.
These tracks are designed to compound. A venue opening engagement naturally transitions into the reporting infrastructure and compliance foundation that Tracks 01 and 02 build. Operators who start with a pre-launch engagement often retain ongoing advisory across all three tracks — because the systems put in place at opening are only as good as the discipline that maintains them.
These scoped one-time projects solve a specific problem and give you a clear picture of where a deeper engagement could go. Each includes a written deliverable and a debrief call. Ongoing retainer available after any project.
Every recommendation here comes from having held the P&L, managed the payroll runs, fielded the compliance calls, and sat through the board meetings where the numbers didn't add up.
This isn't a framework applied from the outside. It's pattern recognition built from years inside full-service hospitality groups — multi-concept, multi-location, with all the complexity that implies.
That context matters. Consultants who haven't run a 250-cover Saturday service don't know which shortcuts cost you later and which ones are actually fine. The difference between a policy that holds up and one that creates exposure is usually operational literacy, not legal sophistication.
30 minutes. No agenda, no pitch deck. You talk about what's actually broken or unclear. We figure out which track — or which combination — fits the problem.
Flat-fee for the audit or setup phase, clearly scoped. No retainer commitment until you've seen the work and decided it's worth continuing.
Findings, recommendations, or built infrastructure — depending on track. Everything documented, everything actionable. Not a report that sits in a folder.
Monthly retainer if you want to keep the relationship active. Same practitioner, no account-switching, no junior associate handoffs.
↓ $114,000 recovered margin per location, per year
A flagship property running 44% food cost. Not a purchasing problem — four problems layered on top of each other. Recipe costing, vendor renegotiation, staffing accountability, and kitchen leadership changes across four venues over six to eight months.
When Nicholas Hammond came in as Director of Operations for a Los Angeles hospitality group, food cost at the flagship property was running at 44%. On paper that looked like a purchasing problem. In practice it was four problems layered on top of each other: a chef whose reliability had deteriorated to the point it was affecting the entire kitchen, staff theft that had gone undetected because no one was looking for it, scheduling that hourly employees treated as optional, and a menu where prices had not been updated to reflect actual ingredient costs and zero plates had been formally costed.
No single lever was going to fix it.
The first step was information. Before anything could change, every menu item needed a real cost attached to it. Recipe costing through a dedicated invoice and recipe platform gave the operation an honest picture for the first time: what each dish actually cost to produce, where the margin was, and where it was not. That data immediately flagged pricing that had not kept pace with food costs and specials being run at a loss.
Pricing was corrected. The happy hour program was restructured. Vendors were renegotiated and in some cases replaced.
The harder work was on the people side. Staff theft was identified and those employees were terminated. Scheduling accountability was enforced. Kitchen staff went through retraining; roughly 90% adjusted and stayed. The chef, given multiple opportunities to adapt, was ultimately not the right fit for where the operation needed to go. A replacement was brought in who could execute within the new standards.
From there the same methodology was applied across three additional venues in the portfolio, each with its own variation of the same root problems.
Food cost dropped from 44% to 25% across the portfolio over approximately six to eight months. On a venue doing $600,000 in annual food revenue, the difference between 44% and 25% is $114,000 in recovered margin per year, per location. Menus were costed and priced correctly for the first time. Vendor relationships were consolidated and structured. Kitchen teams were stable and operating with clear standards.
High food cost is almost never just one thing. Operators who treat it as a purchasing problem alone rarely solve it because the dysfunction usually runs deeper: leadership gaps, missing accountability systems, and pricing that has not been revisited in years. If your food cost is above 32% and you have not done a full recipe costing audit in the last 12 months, you likely do not have an accurate picture of where the money is going.
Mise Advisory · nick@mise-advisory.com · 626-780-1982
↓ 96+ hours of manual reporting eliminated per cycle
Toast, Margin Edge, Push Operations, SevenRooms — each platform generates data that goes nowhere useful. Nicholas Hammond built an automated cross-platform reporting system from scratch, without a vendor, that delivers daily, weekly, monthly, and quarterly reports on a set cadence.
Most multi-venue operators are sitting on more data than they know what to do with. Toast has its reports. Margin Edge has its reports. Push Operations has its reports. SevenRooms has its reports. Each platform does its own thing well, but none of them talk to each other, and the picture you actually need — labor against revenue against COGS against reservation pacing against payroll — lives nowhere. It has to be assembled by hand.
For a 12-venue portfolio, doing that assembly properly would take roughly eight hours per venue per reporting cycle. That math means either you do not get the full picture, or someone is spending the equivalent of two full-time jobs just producing reports that still arrive late.
Nicholas Hammond solved this by building an integrated reporting system from scratch — without a third-party vendor and without a dedicated engineering team. The system pulls data from across the full operational tech stack: POS, payroll, invoice and recipe management, and reservation platforms. Python handles the data processing and aggregation. Windows Task Scheduler runs everything on a set cadence without human intervention. The output is formatted into clean, readable narrative reports and delivered automatically to whoever needs them.
The reporting runs at four cadences:
Manual reporting at this level of detail was not happening before because it could not. Ownership was making decisions based on incomplete data or waiting until enough information accumulated to be worth the effort of pulling it together. With the automated system in place, the same leadership team gets a more complete operational picture than they had before, delivered on a schedule, with zero production time required.
Data you cannot act on fast enough is not an asset. If your management team is still opening five browser tabs every morning to piece together yesterday's picture, the information is already stale by the time decisions get made. An integrated reporting system does not require a software vendor, a long implementation timeline, or a six-figure investment. If you are running more than two venues and still relying on platform-native reporting, you are missing the connective tissue.
Mise Advisory · nick@mise-advisory.com · 626-780-1982
↑ Portfolio-wide real-time visibility from a single platform
Micros at some venues. Aloha at others. Nothing talking to anything. Nicholas Hammond led a full 12-venue POS migration to Toast over approximately one year — operator-led, not vendor-led — and built the integration foundation that the reporting system runs on today.
When Nicholas Hammond took over operations leadership for a Los Angeles multi-venue hospitality group, the technology underneath it was a patchwork. Some venues ran Micros. Others ran Aloha. Each had its own reporting logic, its own quirks, and its own institutional knowledge baked into staff who had been using the same system for years. Nothing talked to anything else, and getting a portfolio-wide view of revenue, product mix, or labor required either a lot of manual work or a lot of guessing.
The approach was deliberate and sequential. Venues were converted one at a time at first, allowing the team to develop a repeatable installation and training process before accelerating. Once that process was proven, the remaining venues were migrated in a consolidated push. The full migration took approximately one year from first venue to last.
Toast's implementation team was involved, but the internal operations team drove the process. That distinction matters: a vendor-led implementation optimizes for technical completion. An operator-led one optimizes for the business running correctly on day one.
Front-of-house staff adapted quickly. General managers were on board. The friction came from accounting, which had built its reconciliation workflows around the legacy systems and was not enthusiastic about rebuilding them. Getting an accounting team to trust a new system requires showing them, repeatedly and specifically, that the data coming out is accurate and that their processes will be better on the other side. That took time and patience more than it took technical solutions.
A POS migration is not just a technology project. The system you run touches every transaction, every labor decision, every report ownership reads, and every integration your operation depends on. If your current POS cannot talk to your payroll platform, your invoice system, and your reservation software without manual exports, you are leaving operational leverage on the table.
Mise Advisory · nick@mise-advisory.com · 626-780-1982
↓ After-hours calls to senior leadership dropped significantly
10:45pm on a Saturday. A manager has an employee situation they've never handled and no one to call. Nicholas Hammond built an AI assistant loaded with the actual employee handbook, HR policies, and California labor law references — accessible by any manager, on any device, immediately.
Every multi-venue operator knows the call. It is 10:45pm on a Saturday, a manager has an employee situation they have never handled before, and they are either calling the Director of Operations for guidance or, worse, winging it. The first option pulls leadership into an operational fire on their night off. The second creates liability.
The problem is not that managers are incompetent. It is that no one can hold an entire employee handbook, a full set of HR protocols, California labor law requirements, and the correct sequence for documenting a workplace incident in their head at the moment they need it.
Nicholas Hammond built an AI-powered assistant specifically for this problem. The system is accessible by any manager via a link on their phone or desktop. No app download, no login gymnastics, no IT department required. The assistant is fed the operation's actual documents: the employee handbook, HR policies, internal protocols, and compliance references relevant to California labor law. It can answer any question a manager might have about those documents in plain language, immediately, at any hour.
The more consequential feature is the incident and write-up workflow. When a manager needs to document a workplace incident or issue a formal write-up, the assistant walks them through the process step by step — asking the right questions in the right order, the same way every time. The output is a completed report that can be emailed directly to HR in one tap.
Built over a few days. No vendor contract. No monthly subscription. The system costs approximately two cents per use — for a 12-venue operation, well under five dollars a month in total running costs after the initial build.
Managers who had been most anxious about incident documentation were the first to respond positively — specifically because the process no longer depended on remembering every step correctly under pressure. After-hours calls to senior leadership dropped. Managers have a resource that gives them the correct answer at the moment they need it rather than the answer they can remember or the one they get when someone finally picks up.
Inconsistent incident documentation is one of the most common and most preventable sources of legal exposure for California hospitality operators. A termination that was not documented correctly, a write-up that skipped steps, a harassment complaint that did not follow protocol — these are the situations that generate PAGA claims and wrongful termination suits. The technology to close that gap exists, it is accessible to any operator regardless of technical background, and at two cents per use it is the least expensive insurance policy in your operation.
Mise Advisory · nick@mise-advisory.com · 626-780-1982
↑ Profitable within 5 months of opening · 16.5% beverage cost
A Sherman Oaks venue needed a complete concept transition — 5-day shutdown, full relaunch, new format. Nicholas Hammond built the operational infrastructure from scratch: systems, staffing, training, and cost controls. The business hit profitability by month five.
A Sherman Oaks hospitality venue required a complete concept transition — not a refresh, but a full operational relaunch under a new format. The window to execute was five days. There was no existing infrastructure to inherit; everything from the staffing model to the cost structure to the systems configuration needed to be built before the doors reopened.
Nicholas Hammond managed the full scope of the relaunch: concept operational planning, staff recruitment and training, POS configuration, vendor sourcing, and cost structure modeling. The beverage program was built around fresh juice cocktails with a 16.5% cost — a number that requires both disciplined purchasing and tight recipe adherence from day one.
The relaunch covered a range of service formats: 40–100 nightly covers during the week and weekend brunches of 200–300 covers. Each format requires different labor deployment, different flow management, and different cost assumptions. Building a staffing model that works across both without overbuilding for one or underbuilding for the other is an execution problem, not a planning problem.
The venue reached profitability by its fifth month of operation — in a cost environment where new restaurants routinely operate at a loss through their first year. The beverage program held its cost targets. The staffing model scaled with volume without ballooning labor at the high end.
A new venue's first 90 days set the operational habits that are hardest to break later. Labor drift, cost creep, and compliance gaps that develop in the opening period tend to calcify — they become the baseline everyone defends instead of the problem everyone fixes. The difference between an opening that builds the right infrastructure from day one and one that figures it out in month six is usually a year of margin and a significant amount of staff turnover.
A repeatable pre-launch framework built across many successful openings covers systems configuration, staffing structure, vendor setup, and first-quarter operational oversight. The engagement is scoped to end before you need it to — not after.
Mise Advisory · nick@mise-advisory.com · 626-780-1982
Book a 30-minute call or send a message. No pitch decks, no junior reps.
30 minutes. Pick a time that works and it goes straight to the calendar. No back-and-forth scheduling.
View Available Times →or email: Nick@mise-advisory.com
Prefer to start by email? Tell me what you're dealing with and I'll respond within one business day.