Loading
Loading
Proven at scale
14+
Locations in live operations
8,000+
Meals per day context
90
Day implementation arc
Phases overlap in real life. The order below is how work stacks so each layer sticks before the next one lands. Tools like MarketMan are examples - what ships depends on what you already run.
Weeks 1-2
Full cost structure review across units - food cost, labor, procurement gaps, and quick wins you can act on immediately.
Weeks 3-5
Production planning overhaul, waste tracking, portion controls, and a practical framework for supplier conversations.
Weeks 5-7
Scheduling workflows rebuilt around real volume patterns, overtime discipline, and efficiency targets that fit each site.
Weeks 6-9
Centralized procurement, par levels, and real-time inventory visibility - often built or tuned around tools such as MarketMan or your existing stack.
Weeks 8-11
Documented SOPs for critical processes, with unit-level managers trained to own execution without you standing over every shift.
Week 12
Live reporting so you can track food cost, labor percentage, and revenue performance by site - without needing someone on the floor every day to interpret it.
Every operation is different. These are the kinds of movements that show up when audit, systems, and follow-through actually match the floor - not guarantees, but the target shape of the work.
Waste & production
Meaningful waste reduction when production planning, portions, and tracking finally match how the kitchen actually runs.
Labor
Efficiency gains when schedules follow volume instead of habit - often in the mid-single digits when the baseline was broken.
Revenue & execution
Stronger revenue per unit when menu, execution, and coaching line up - without betting everything on another marketing push.
Audits start at $12,500. Two to four weeks, fixed scope. You leave with a written list of what is broken and what to do about it.
90-day engagements start at $45,000. The number depends on site count, the state of your stack, and what holds at the end. The final number comes after the audit.
No tiers. No menu. The work fits the operation, not the other way around.
Founding client pricing for the next three engagements.
A fixed-scope, implementation-first engagement across your multi-site food operation. Audit in weeks 1-2, food cost system in weeks 3-5, labor scheduling in weeks 5-7, ERP and inventory integration in weeks 6-9, SOPs and reporting by week 12. No strategy deck. Real workflows, on your clocks.
Multi-unit restaurant groups of roughly three to twenty-plus locations, hotel and resort F&B operations, catering companies under margin pressure while scaling production, and PE-backed acquisitions that need professionalized day-to-day operations. If heroics are no longer fixing your food cost or labor pain, this is for you.
Single-location operators who need a line cook, not a systems rebuild. Groups looking for a strategy deck instead of implementation. Anyone who wants a marketing or menu refresh without touching food cost, labor, or reporting discipline.
A consultant leaves you a plan. I leave you a system that runs. Workflows, standards, reporting cadence, and managers trained to own execution. Implementation, not theory.
Pricing is set after the audit call. Every site is different. Volume, tool stack, and scope move the number. I keep a limited number of active engagements so the work stays hands-on.
No. I often work within your existing stack. Tools like MarketMan, or whatever you have. I build or tune around it. If XenoSoft Solutions tooling fits later, that conversation happens after the workflow works.
You own the system. Your managers run it. A KPI handoff and quarterly check-in are available if you want continuity, but the engagement is designed to end cleanly without creating dependency.
I keep a limited number of active engagements so the work stays hands-on. If this matches your reality, lead with facts: volume, owners, what broke, and what “done” looks like on your P&L and on the line.
Want proof before you reach out? Case studies and the hub go deeper on specific problems.