Prototype built for the Supy GTM case study, not deployed or sent. ← Back to the full case study
For Khaled Fadly, CEO

$15.5M raised. 20 restaurants planned. One procurement system, or thirteen?

Ruya Private Capital's $15.5M (Nov 2024) is earmarked for exactly this: 20 dine-in restaurants across Riyadh, Jeddah, and Dhahran over the next two years, on top of the 13 delivery-only kitchens already running today. That's the strongest funding-plus-expansion signal in this entire build, and it's also the moment procurement complexity multiplies fastest, before the systems are locked in site-by-site.

Starts at your real 13 today, drag right to model the 20-restaurant plan the $15.5M raise is earmarked for.

13 today13 kitchens33, plan complete
845
days back per year, at 65/site/year
2.3
person-years of ops time, back with your team

A real result

39% to 33% food cost. 15% to 9% variance. Three months.

One Supy customer took food cost from 39% to 33%, and variance from 15% to 9%, in three months, purely from connecting procurement and inventory into one system instead of running them separately. The earlier that's in place before new sites open, the fewer sites there are to retrofit later.

Why now, specifically

KSA sourcing hit a measurably lower first-pass data-match rate than the UK in this build's own numbers, 47% vs. 74%, which tracks with what we've seen: groups here often run heavier manual reconciliation before a connected system even enters the picture. Standing that up before, not after, 20 new sites open is the cheaper order of operations.

Not a cold intro

This references your own public plan and your own quoted timeline, not a generic multi-site pitch sent to every operator in the region.

Worth 15 minutes before the next 20 sites lock in a process?

No deck, just a look at what a connected system costs to run across 13 kitchens today versus 33 in two years.

Reply to set up a call →

Personalized off the real raise, the real expansion plan, and the real kitchen count, not a mail-merge guess.