vertical-restaurants

# Vertical: restaurants & hospitality — don't spec it naive Restaurants run on razor-thin margins (net 3–6%) with a hostile incumbent stack. A spec that treats a menu as a flat list of `{name, price}` or ignores who already owns the POS will ship something no operator can use. This skill loads the domain so architect/pm sound like they've worked a shift. The 4 products in this vertical: | Product | Archetype | One-liner | |---|---|---| | online-ordering | content | Own menu + checkout for dine-in/pickup/delivery — dodge aggregator fees | | reservations | booking | Bookings, tables, text-the-waitlist | | loyalty | crm | Points, offers, win-back | | shift-scheduling | booking | Rota, open shifts, swaps with coverage rules | Incumbents to position against: **Toast** (POS, ~$69–165/mo + hardware + 2.49%+ per swipe), **Square** (POS/SMB), **SevenRooms** (reservations/CRM, upmarket), **ChowNow** (commission-free ordering), **DoorDash / Uber Eats / Grubhub** (aggregators, **15–30% commission** per order). ## 1. Domain vocabulary (use these words in the spec) - **COGS / food cost %** — cost of ingredients ÷ menu price. Target ~28–35%. - **Prime cost** — food cost + labor cost; the number operators obsess over (target ≤ ~60% of sales). - **Menu engineering** — classifying items by popularity × margin into stars (high/high), plowhorses, puzzles, **dogs** (low/low). Drives what gets promoted or cut. - **86'd** — an item is out of stock / unavailable ("we're 86 on the salmo...