An operating system for a gelato maker: a web app instead of a spreadsheet and verbal hand-offs
Correct numbers for two shops, without notes on paper and follow-up questions.
A gelato maker in the US counted stock and planned production through a shared spreadsheet, word of mouth and chat messages. ODCUS is turning this into a web app in which every role has its own view and which belongs to the client.
Starting point
The business produces centrally and sells through several shops. What is left in which shop in the evening, what gets produced the next day and which flavour replaces a missing one all ran through a spreadsheet, photos of paper notes and messages between production, shop management and the owner.
Each of these handovers cost time and regularly went wrong: a shop reported too late, production planned by gut feeling, and the owner had to ask instead of deciding. The knowledge of how the business really runs sat with a few people.
The contact came through a recommendation from an earlier project. The contracting party is ODCUS AG.
Approach
- Requirements gathered from the three roles: the person serving in the shop, the person running the shop, the person who owns the business. Each role gets its own view of the same data.
- The workflows rethought from the result: what does the shop need to know in the morning, production the evening before, the owner at the end of the month?
- A web app built to carry these workflows: evening count per shop, production list for the next day, replacement flavours and recipes in one place.
What the client gets
- A web app instead of a spreadsheet and verbal hand-offs, with one view per role
- Workflows that run without follow-up questions: demand, production, handover
- Source code, data and context belong to the client. No subscription, no dependence on us
- Correct numbers for both shops, without notes on paper and follow-up questions
Tools used