Skip to content
This repository has been archived by the owner on Oct 8, 2020. It is now read-only.

Latest commit

 

History

History
23 lines (12 loc) · 1.58 KB

pitch.md

File metadata and controls

23 lines (12 loc) · 1.58 KB

EatersLab

Version number: 1.0

Authors: Krzysztof Antoniak

Changelog

  • v1.0 (2020-03-09): Initial revision (Krzysztof Antoniak)

Problem statement

Cafeterias are popular among students and office workers going for lunch or dinner. Since people tend to eat at the same time, lunchrooms are usually cramped. Customers have to wait in long queues and look for empty seats afterwards. Also, visitors have to come to cafeteria to find out what is served, how long will they wait etc. Owners have to handle customer spikes during lunchtime while cafes are empty at different hours.

Value proposition

Informing customers about cafeteria state saves them time and helps them decide whether to go for lunch at given time. They should know how many people are currently having lunch and what the menu is beforehands. With rating options, users can guide each other in search for the best dishes. Foreign visitors and disabled users can easily access all data on their devices.

Owners will benefit from analytics. Historical data and occupancy predictions help to prepare for lunch in advance, while updating customers mitigates traffic spikes. Publishing menus is a new marketing channel promoting cafe directly to interested users. Administration panel can automate posting to social media channels. Collected feedback will contribute to service improvements.

Architecture overview

System of cameras counts visitors entering and leaving lunchroom space. Central endpoint aggregates occupancy reports for owners and customers using mobile or web clients which also serve as information/feedback loop.