Own product
DeuQuantas — The right bill, no fights
An app that ends the argument over splitting the bill at the bar. Everyone pays for what they had, the owner photographs the menu to update prices, and a ready-made report arrives at the end of the week.
- 3
- 2024
Problem.
Closing the bill at a bar or restaurant is a source of errors and friction: manual splitting, forgotten items, outdated menus, and zero visibility into what happened during the week.
Solution.
A complete platform — app and web — with automatic bill splitting, menu updates by photo, and a weekly report ready for the owner, with onboarding via WhatsApp.
Result.
Product live at deuquantas.com.br signing up venues. In the partnership, design and engineering, from prototype to deploy, are mine.
The hard part.
Every project has a point where the obvious solution doesn't cut it. Here, it was these.
Splitting a bill is a rules problem, not a math problem
Adding up and dividing by N is trivial. The hard part is the real world: an item shared by three out of five people, someone who arrived late, a round on the house. The modeling had to treat consumption as a relation between item and person, not as a column of values.
Menu updated by photo
Asking the owner to register item by item would kill adoption before it started. They photograph the menu and the system does the rest — onboarding friction is what decides whether a product like this lives or dies.
What I did.
- Product definition: which problem to solve first and what to leave for later
- Backend, app and website — architecture and implementation
- Onboarding via WhatsApp, the channel where bar owners actually reply
- Visual identity and interface, from prototype to published version
Stack.
Have a similar project?
Tell me the problem — I answer personally.
See it live.
Public pages of the product, open to anyone.