Profitable Restaurant Boss

Specific Pain Points in Restaurant Operations

Restaurant owners typically grapple with thin or negative profit margins due to imbalanced cost structures (e.g., excessive food, labor, or rent percentages), suboptimal menu design suppressing gross margins, broken customer acquisition and retention funnels, and operational inefficiencies (like low table turnover or slow service). Traditional consulting often lacks actionable, data-driven insights, leaving owners unable to pinpoint profit leaks.

How the Skill Works: Core Capabilities and Workflow

This skill emulates a practical profit consultant, anchored by the profit-diagnosis-framework and five key levers: menu-engineering, cost-control, marketing-playbook, operations-kpi, and financial-model. The workflow follows a closed-loop four-step process:

1. Diagnostic: Gathers business profile, scale, and critical data (e.g., monthly revenue, food cost rate, table turnover). Missing data triggers industry benchmark assumptions with clear annotations.
2. Localization: Uses financial-model tools to calculate break-even points and identify which lever has the most severe cost deviation from benchmarks.
3. Solution Design: Pulls specific tactics from reference files (e.g., menu-engineering.md), prioritized by low investment and quick ROI, with quantified expected profit improvement ranges.
4. Implementation & Review: Provides scripts like profit_calculator.py for quick calculations and templates (e.g., cost-structure-template.csv) for immediate use, setting 2-4 week review nodes.

Applicability and Key Considerations

The skill targets all Chinese restaurant formats (full-service, fast-food, tea, hotpot, etc.) but relies on accurate store data input. Outputs always lead with numbers, pairing every conclusion with key indicators (e.g., gross margin, payback period) and transparently marking assumptions. Red lines are non-negotiable: food safety, compliance, and cash flow security are底线, ensuring solutions are executable (specifying "who does what, how, and timeline"). Not suitable for scenarios with severely missing data or lack of operational willingness.