← Our portfolio·Case study
Le Boké — three and a half hours reclaimed on every themed day
How a custom web app replaced Messenger, a notepad and a phone follow-up with a pre-order in 8 clicks.
- Project type
- Full web application
- Industry
- Restaurant
- City
- La Tuque, Quebec
- Delivered
- July 2026
- Application
- leboke-sushi.vercel.app ↗
1 · Context
A family restaurant, and days that pack the place
Le Boké is a family restaurant in La Tuque. About once a month, the team runs a themed day — the famous sushi days, among others.
These days draw a big crowd. To avoid stock-outs and long waits at the counter, the team takes pre-orders over 3–4 days beforehand. It's popular — too popular to be managed by hand.
2 · The problem
Messenger, a notepad, a manual follow-up
Before Masko, every themed day went like this:
- Customers sent their orders through Messenger.
- Patrick took notes on a notepad as they came in.
- In the evening, he compiled everything by hand: who, how much, which piece, which pick-up time.
- He called back some customers to clarify an incomplete order.
- Sometimes, an order slipped through the cracks — a customer showed up at the counter, their order was missing.
Roughly 4 hours of administrative work per themed day. Plus a continuous mental load during the 3-to-4-day pre-order window.
3 · The solution delivered
An application built for the way the team actually works
Pre-order widget
Embedded on leboke.ca. Customers pick their pieces, their pick-up time, pay by card via Stripe. Eight clicks and the order is confirmed — no human intervention needed.
Admin panel
Patrick sees every order in real time, filtered by pick-up slot. He can mark an order "prepared", "picked up", "no-show" in one click.
Automated emails
Confirmation email at order time, reminder one hour before pick-up closes, message if an item is no longer available. The customer doesn't call anymore — they're already informed.
Scheduled pick-up
Every customer picks a 30-minute slot. Result: no more crowd at the counter, the flow is spread out across the day.
End-of-day report
Patrick automatically receives two Word files: the full list with prices and taxes for his bookkeeping, and the same list without prices for his prep team.
Everything is hosted on Patrick's own accounts (Vercel, Stripe, database). His order and customer data is his own, exportable at any time. Continuity clause active from day one.
4 · Results
Hours, not dollars
Before
~4 h
of administrative work per themed day
After
~30 min
to set up the event in the admin panel
Saved
~3.5 h
reclaimed per event
Across a year of about a dozen themed days, that's around forty hours returned to the kitchen and the floor, instead of spent on notes and follow-ups.
And beyond time — zero orders lost since launch. The mental load of the 3-to-4-day pre-order window is absorbed by the application.
5 · Takeaway
A tool built for you, not against you
The technology didn't need to be revolutionary — a form, a cart, an email. What matters is that it matches exactly how the restaurant works, not the other way around.
An SMB doesn't need a generic "online ordering platform" — expensive, with a commission per transaction. It needs its own tool, one that speaks its language and respects its habits.
The same approach works for other businesses that run recurring events: caterers, food trucks, cooking classes, open house days. Each case keeps its DNA, no identical resale — see our approach.
Do you run recurring events?
We can build the tool that returns your hours to you — not a template we bend to fit you, a tool that speaks your language.