Current wedge
Premium menu object
Validate the leather bound menu object, read only guest experience, and staff preparation flow.
Future
The first product must prove the later roadmap.
Future software only matters if the first menu object becomes useful in real service. Until then, roadmap items are assumptions to test, not promises.
Near term
Content control layer
Add language, templates, menu states, and controlled update workflows.
Operational layer
Service aware workflows
Support outlets, service timing, team roles, and repeated operating patterns.
Long term
Hospitality intelligence
Explore inventory, pricing, and integrations only after the core workflow is trusted.
Roadmap discipline
What is current, what is next, and what is not MVP.
The first version focuses on the object and staff workflow. Later layers should only be built when they solve a confirmed venue problem.
CurrentBuilt towardExploringOver timeFuture layerNot yet part of MVP
Current wedge
A physical menu object controlled by staff and read by guests without touch interaction.
Near term software
Language handling, menu upload, reusable templates, and service state scheduling.
Operational layer
Outlet controls, team permissions, timing rules, and consistency across services.
Long term intelligence
Inventory links, pricing suggestions, and integrations only after venues trust the core workflow.
Pilot conversations
Useful feedback needs a real venue context.
Reach out with the service setting, menu workflow, or pilot constraint you would want TailorTaste to solve.