Service starts blind
Teams walk into lunch and dinner without one shared view of covers, prep, staffing pressure, and pending fires.
Independent public microsite
Turn service chaos into a readable control loop.
Magic is a standalone concept site for a restaurant operating system that keeps prep, floor, and close aligned without making operators live inside another dashboard.
The current gap
Restaurants do not need more software. They need fewer blind spots.
Handoffs collapse under pressure
Kitchen, floor, and owner updates happen in fragments, so the same questions repeat while margin leaks.
Post-shift learning never compounds
What went wrong stays trapped in chat, memory, and paper notes instead of becoming tomorrow's operating rule.
System design
A small operating loop for the whole shift
See the floor
Magic gives every shift a single view of reservations, prep readiness, constraints, and service risk.
Direct the next move
Instead of a heavy dashboard, the interface prioritizes the next action that protects service and margin.
Capture the pattern
Useful decisions survive the shift and become reusable playbooks for open, service, and close.
Signal flow
What the product would surface, in order
From reservation book to close notes
The system is designed to start at forecast and staffing pressure, move into prep readiness and service pacing, then end with reusable notes for the next shift. Each step narrows the team's attention to the next operational decision.
- Built as a separate public site, not attached to an existing personal domain or design system.
- Content lives in small data modules so product framing can change without rewriting the page structure.
- Responsive by default, with explicit overflow guards and bottom-of-page validation on mobile and desktop.
Core modules
Four focused surfaces instead of one bloated admin wall
Shift Pulse
A calm command surface for covers, pacing, labor pressure, and bottlenecks before they hit the pass.
Prep Map
Prep progress becomes visible by station so teams stop chasing status and start correcting drift early.
Handoff Notes
Important context moves forward in clean, scannable operational notes instead of disappearing into chat noise.
Close Review
A short post-service review turns broken moments into the next night's guardrails and checklists.
Launch pattern
Roll out in three constrained moves
Week 1
Instrument one service
Start with a single lunch or dinner pattern and make signal quality more important than feature quantity.
Week 2
Lock the handoff ritual
Preserve the moments that matter between prep, floor, and close so every shift begins cleaner.
Week 3
Publish the playbook
Turn repeated interventions into reusable operating rules that new staff can follow without folklore.
Why this site exists
Built as a clean, separate public surface for the Magic concept.
This project lives in its own directory, uses its own future Pages target, and stays detached from any existing personal domain or production app until the product direction is proven.
Back to top