05 / Product exploration / 2026
RevuBot
An ongoing exploration of turning restaurant feedback into weekly operator action.
Summary
Guests keep praising the kitchen and keep flagging the wait at peak service.
Recurring complaints
- Wait time at peak34%
- Order accuracy22%
- Noise in main room16%
- Card machine issues11%
Sentiment trend
This week, do these three
- 01Add one runner Friday and Saturday, 20:00 to 22:00
- 02Re-brief the pass on ticket read back
- 03Move the two window tables away from the speaker
Illustrative concept interface
- Role
- Product concept, positioning and early direction
- Scope
- Product concept / Restaurant industry insight / Positioning and messaging / Landing page experiments / Early product direction
- Live
- Concept
Context
Restaurants sit on years of feedback that no operator has time to read. Existing tools tend to bury the signal inside another dashboard. Coming from the restaurant side myself, I wanted to see if the answer could be smaller and sharper.
Approach
I ran a series of positioning and landing page experiments, different angles, different promises, different tones, to find the wording that made restaurant operators lean in. The through line: fewer charts, more concrete actions for the coming week.
Decisions
- Weekly actions as the primary output, not dashboards.
- Language written for operators, not for investors.
- Multiple positioning tests before committing to a single product shape.
- A concept that respects how little time restaurant teams have.
Delivered
- Product concept and positioning
- A series of landing page experiments
- Early direction for a lean MVP
Outcome
An open exploration of how restaurant feedback could become clear operational action instead of another dashboard. Presented here honestly as a concept, not a launched product.