Shawarma Palace
Regional QSR chain (Middle Eastern / shawarma) · Ottawa, Eastern Ontario
Your site says a mobile app is 'in development' - with 10 Ottawa locations already live, want to talk about the ops dashboard that should ship alongside it?
Why they need it
Shawarma Palace has grown to 10 Ottawa-area locations since 1997 under owner Abbas Sobh, taking orders through a mix of their own web ordering site and UberEats, with a note on-site that a dedicated mobile app is still 'in development.' At 10-location scale, the real opportunity isn't just a customer app - it's the back office behind it: a multi-location operations dashboard giving Abbas one view of sales, online order volume and delivery-fee spend across all 10 stores instead of checking each location's UberEats and web-ordering numbers separately, plus inventory/prep-par tooling so each store manager isn't reordering by phone call. Finishing the customer-facing app alongside a proper ops layer would let Shawarma Palace own more of its ordering relationship (and margin) instead of ceding it to Uber, while giving Abbas the multi-store visibility a 10-unit chain needs but currently lacks.
Tech gaps
No live mobile app yet despite 10 locations (one is in active development per their own site); no visible multi-location inventory, staffing or sales dashboard; email obscured behind Cloudflare protection with no direct address published
Current tech
Own online ordering site (new.shawarmapalace.ca) plus UberEats; site notes a dedicated mobile app is 'in development'; catering/food-truck booking handled off-site
Selling a portal + ops tool
PlaybookA customer-facing portal and the internal tool behind it, built together so the data is entered once.
- Lead with whichever side hurts more today; the other side is phase two.
- One data model means the customer sees exactly what the office sees.
Objections (1)
- “That is a big project.”
- It is two small ones in a row. You see the first working before you commit to the second.