Live 86 board for restaurant kitchens and servers
The idea
Every restaurant runs out of dishes mid-service, and the state of the art for telling the floor is someone shouting across the pass. Every miss is real money: a server sells the last braised short rib that does not exist, the table waits, the appetiser gets comped, sometimes the table walks. POS systems technically support 86ing, but it is buried in menu-management screens nobody opens during a rush.
The wedge is ruthless simplicity: one tap at the pass, every server phone updates in under a second, everything clears at close automatically. It does one thing the POS does badly and does it at the speed of service. The morning report (what 86’d and when) is a quiet second product for owners doing purchasing.
Who pays
The owner or GM pays 19 dollars a month per location, an impulse price justified by a single avoided comp. It sells bottom-up: one server or chef who used it elsewhere pushes the next restaurant to adopt it, so the join-code onboarding must take under a minute. Distribution through restaurant subreddits, KitchenConfidential-style communities, and local restaurant Facebook groups where staff already vent about exactly this.
MVP scope
- Kitchen tablet board with tap-to-86 and limited-count items
- Server PWA joined by code, realtime updates with vibration on change
- Auto-clear at configured close time
- 30-day morning report of what 86’d and when
- Skip for v1: POS integration, multi-location dashboards, inventory counts, role-based permissions
Build EightySixed, a live 86 board for restaurants. Stack: Next.js (App Router) built as an installable PWA, Supabase for Postgres with Supabase Realtime channels for live sync. Core flow: a manager creates a location and pastes or types the menu as a flat item list grouped by section (apps, mains, desserts, specials). The kitchen view runs on a tablet by the pass: the full menu as large touch targets, tap an item to 86 it (it goes red and jumps to the top), tap again to bring it back; a long-press sets a limited count (e.g. 4 left) that anyone can decrement. Servers open the same location on their phones via a join code, no individual accounts, and see only the 86 list plus limited-count items, updated within a second via a Realtime subscription. When something changes, flash the changed row and fire a vibration on server devices. Pages: / (marketing plus login), /kitchen/[location] (tablet board), /board/[location] (server PWA view, joins via 6-character code), /settings (menu editor, close time), /history (morning report: what 86'd, at what time, for how long, over the last 30 days). Implementation details: auto-clear all 86s at the configured close time via a scheduled job so Tuesday never starts with Monday's list; design the server view for a locked phone in a apron pocket, meaning it must survive backgrounding and resubscribe on focus without a reload. Pricing: 19 dollars/month per location, first location free for 30 days, Stripe checkout.
// More B2B ideas
-
Compliant labels for cottage food producers
Home bakers and small food producers hand-make labels that violate state cottage food rules; this generates compliant labels with allergens per state.
B2B weekend -
ATS duplicate checker while sourcing on LinkedIn
Agency recruiters waste outreach on candidates already in their ATS; this extension flags known profiles and past contact history as they browse.
B2B Chrome extension 1 week -
Belt testing and curriculum tracker for martial arts schools
Martial arts school owners track student stripes and testing eligibility on index cards; this tracks progress, flags who is ready, and runs test day.
B2B 1 week -
Bait station scanning for pest control routes
Pest control techs hand-log rodent station checks that commercial clients audit; this scans station QR codes and builds the service report on site.
B2B Mobile 1 month