Restaurant-RGI · Compounding Intelligence

Restaurant-RGI

Margin intelligence that learns your kitchen

Ten jobs, one line of your P&L — the food and beverage you buy to run the kitchen (~28–33% of sales). One engine that acts instead of advising, knows when not to act when a market breaks, and compounds as it learns. For operators: margin you can leave running. For distributors: the customer-outcome layer shipment data can’t see.

Each job runs a seeded simulation — hit Run to build the charts and hear the mechanism. Set your chain size for portfolio impact; flip the distributor (Sysco) lens for the sell-side view. Synthetic / modeled; no production customers.

~$2.1M/yr modeled margin impact across 50 unitscost side · overlap-adjusted · roadmap adds more

Economics modeled on: 50-unit chain · $450K food spend/store/yr · ~30% food cost · $110K loaded FTE · 2–5% operating margin. Adjust chain size above to rescale.

🔊 TAP ANYWHERE TO ENABLE NARRATION
Narrating…
Job 1 · order it

Order Autopilot — runs your food order like your best GM, and asks when it's unsure

Problem

Your order guide is last spring's pars — your GMs override it or spend an hour a day rebuilding it, and one strange weekend still buries the walk-in or 86s your movers. Now multiply that by every unit, every day.

What it does

Builds and places the food & bev order itself — order / more / less / skip per category, tuned to this store's covers, weather and events — and takes over category by category only as it earns it.

RGI edge

A static order guide can't adapt and a recommend-only tool still needs a hand on every line. RGI is the one that places the order and hands back only the calls it hasn't earned — ordering you can actually leave on.

Watch

Auto-placed share climbs category by category; the gated line holds while the no-leash version overfits a noisy week.

Share of the food order placed automatically & accuracy — over the order stream
order accuracy (on a leash)no leash — overfitsold order guideauto-placed share
When each category earns hands-off ordering
Job 2 · use it

Usage Truth — bought vs. should-have-used vs. actually-used

Problem

You know what you bought — the invoices are right there. You don't know, by item by store, what reached the plate vs. what died in the walk-in or got over-portioned. The P&L shows the gap a month late, as one blurry point of food cost.

What it does

Lines up three numbers your systems keep apart — bought, should-have-used (sold × recipes), and actually-used (counts) — and names the item and the store where the gap lives.

RGI edge

Inventory suites record what happened; RGI closes the loop to what should have happened and acts on the gap — the half of food cost your invoices and your POS each only half-see.

Watch

Aggregate reads a healthy 30% while one item runs over; the same leak repeats across a cluster of stores.

Food-cost % by menu item — aggregate on target, one item over
The leak across your stores — ranked by food-cost %, cause flagged
on targetwatchoverP portioning · S spoilage · T shrink
Job 3 · check what showed up

Spec Watch — catch a vendor's quiet yield change before the P&L does

Problem

A distributor quietly shrinks a pack, swaps a cut, or the case yield drops a few points. Your food cost creeps across a dozen stores and nobody can say why until month-end — if ever.

What it does

Tracks the realized yield of each item — usable product per case after trim and spoilage — across every store, and when it drifts below its learned norm names the item, the vendor and the week.

RGI edge

Nobody watches yield across stores — the leading indicator lives in your kitchens, not on an invoice. RGI catches the drift weeks before the P&L, and before the vendor admits it.

Watch

The salmon slips mid-stream; the flag fires the next week; the P&L wouldn't show it for a month — and it's the stores on one vendor lot.

Realized yield by week — the drift and when it's caught
drifting itemother items
Which stores are hit — the vendor lot, not one kitchen
Job 4 · check what you paid

Invoice Integrity — decompose the price move your contract didn’t catch

Problem

Your 11-year distributor quotes +14%, "driver shortages." It clears as "the market" — because it's the vendor you trust most — and the overcharge disappears into a food-cost point nobody can take apart.

What it does

Scores every invoice line against your contract and the learned norm, decomposes the increase — commodity market move vs. supplier markup — checks it against your contract ceiling, and drafts the credit claim.

RGI edge

Others store what you paid; RGI knows why it moved and whether your contract allows it — and claims the difference at the line, not at the P&L.

Watch

The +14% splits into a market move within contract and a markup over the ceiling — the recoverable part.

The quote, decomposed — market move vs supplier markup vs your contract
Credit recovered over the quarter — caught at the line, not the P&L
Job 5 · capture what's owed

Rebate Capture — the buying-group cashback you never file in time

Problem

You're in a buying group with cashback and rebates on lines you already buy — and a quarterly deadline you've never once hit, because matching SKUs and filing on time takes hours nobody has.

What it does

Matches your actual purchases to eligible SKUs and tiers, flags the in-group brand switches that capture cashback at no quality change, files before the window, and verifies the credit landed.

RGI edge

A rebate program is a live rule RGI holds and works, not a PDF in a drawer — and it learns which switches pay most, so capture compounds quarter over quarter.

Watch

Most of the eligible money is lost at "filed in time"; captured automatically, the rate climbs as it learns.

Eligible → captured — by hand vs automatically
Capture rate over quarters — it compounds as it learns
manualRGI
Job 6 · protect it when prices (or demand) blow up

Margin Shield — protect food cost when a price — or a weekend — goes crazy

Problem

Eggs quadruple on bird flu, beef spikes, coffee blows up — or a heat wave plus a festival blows up a weekend. Most systems keep buying to par and you eat it, or you reprice a month too late.

What it does

When a volatile item's price (or the week's demand) breaks its normal range, it stops committing that item, switches to your backup spec, and flags which menu items to reprice or pull — then holds until it settles. On a demand shock it pauses the volatile categories back to your chef.

RGI edge

Every other system must always place an order. RGI is the only one that can say "trust me less right now" and cut its own exposure when the regime breaks — the capability nothing in the market has.

Watch

Buy-to-par gets whipsawed while Shield holds flat — because it knows when not to buy forward.

Food-cost % through the shock — buy-to-par vs Margin Shield
buy-to-parMargin Shieldshock (rel.)shock window
Exposure on the item — cut at the break, restored on recovery
What Shield did during the shock
Job 7 · keep the know-how

Store Memory — open a new store seasoned; keep it when a GM walks

Problem

Every new store opens cold — the new GM over-orders for a quarter learning the room. And when a strong GM or chef leaves, the pars, vendor quirks and Friday instincts walk out the door. Across a chain, turnover and openings are a constant tax.

What it does

A new store opens already carrying what a comparable store learned — the pars, the vendor read, the daypart patterns — so the ramp is weeks not a quarter; and the judgment lives in the engine, so a departure doesn't reset the unit.

RGI edge

Rivals store order history and cost; RGI keeps the judgment and transfers it to a new store or a new GM. The continuity no competitor offers — turnover becomes a non-event.

Watch

A GM departure barely moves the line, and each new opening ramps faster than the last.

A unit's food cost through a GM departure
without Store Memorywith Store Memory
Weeks to target food cost, per new store opened
Roadmap · price it, staff it

Price It / Staff It — the same model that orders your food prices it and staffs it

Problem

Prices get reset once a year by gut while costs move weekly; and the schedule is last week's copy-paste. Both halves of margin — the menu price and the labor line — ride the same demand your ordering already reads.

What it does

Price: propose +$ on the plowhorse where elasticity says volume holds, verify contribution margin on the next PMIX. Staff: size the shift to the covers forecast, cut the overstaffed rainy Tuesday.

RGI edge

The same learned demand model that orders your food prices it and staffs it — pricing and labor aren't two more tools to buy, they're one engine turned on the revenue and labor lines. roadmap

Watch

The plowhorse takes a price it can hold; labor tracks the covers curve instead of the copy-paste.

Price — contribution margin per plate, now vs proposed
nowproposed (elasticity holds)
Staff — labor % across the week, copy-paste vs to-forecast
copy-paste scheduleto the covers forecast
Roadmap · pre-buy what you're sure of

Forward Buy — turn demand you're sure of into locked price and guaranteed supply

Problem

You order week to week and take whatever price and supply the market gives — a price-taker, exactly when prices swing most.

What it does

Because it knows how much of each ingredient you'll need and how sure it is, you commit the confident slice forward for locked price and guaranteed supply, and leave the uncertain rest to weekly buying.

RGI edge

A forecast you can't trust can't back a commitment. RGI commits only the slice it has earned confidence in — turning your demand into buying power without betting on guesses. roadmap

Watch

The committed share tracks confidence; the blended cost runs below taking spot every week.

Your demand, split by confidence — committed forward vs left to spot
committed forward (price locked)left to spot
Blended cost vs taking spot every week
all-spotForward Buy blended
The number you report up

The P&L Number — food-cost % down, and the dollars proven

Problem

The number you report up is food-cost %. Point tools give a one-time setup bump then fade — and can't prove the dollars to your CFO.

What it does

Every verified outcome sharpens the next, so food-cost % keeps trending down and recovered $ compound by source — waste, invoice, shrink, variance, rebate — each in a ledger you can hand finance.

RGI edge

A tool that runs Day-365 logic identical to Day-1 decays; RGI compounds — the gap against a static tool widens, never narrows — and every dollar is attributable, not a marketing estimate.

Watch

The cost-side line declines and holds while a generic tool drifts up; recovered $ stack by source.

Food-cost % over the season
RGI cost side+ menu pricing (roadmap)generic tool
Cumulative recovered $ — by source
The bottom line

Why Restaurant-RGI

The restaurant industry runs on 2–5% margins. Food cost is the largest controllable line — and every tool in the market runs Day-365 logic identical to Day 1.

It acts

Places the order, catches the yield drift, claims the overcharge, files the rebate. Every other tool recommends; this one closes the loop.

It knows when not to act

Cuts its own exposure when eggs quadruple or a weekend blows up. The conservation law gives it a mathematical floor; no other platform can do this.

It compounds

Every verified outcome from your kitchen sharpens the next decision. The gap against a static tool widens week over week and never narrows.

Why others can't

RGI learns from kitchen outcomes, not invoices. A learned decision geometry (140 values) reshapes from verified results; static tools have no feedback path from outcomes.

For operators

~$2.1M/yr cost-side impact (50-unit chain, $4$450K food spend/store). Every dollar attributable by source — waste, invoice, shrink, variance, rebate. Menu pricing + labor on the roadmap.

For distributors (Sysco)

The customer-outcome layer shipment data can't see: consumption signal, managed volatility, guaranteed forward demand. Customers stickier, healthier, harder for a rival broadliner to win.

One engine · Ten jobs · One line of the P&L

Provable on your own data in thirty days, read-only, before anything goes live.

dakshineshwari.net Arindam Banerji · banerji.arindam@gmail.com The material earns the next conversation.

The product — live screenshots

The Purchasing Copilot running on the same engine underneath. Cropped for size. Screenshots from the live demo, not mockups.

ORDER SCREEN

The operator selects an item — seven factors auto-compute, cost analysis runs (stockout vs waste), and the system scores the order. One button. The same engine as the 10 demos above.

Purchasing Copilot Order screen
DASHBOARD

Conservation status GREEN. 269 of 298 decisions verified. The system is accumulating evidence — it knows where it’s earned the right to act.

Purchasing Copilot Dashboard
Cropped — full screen includes par levels, weather plan, price alerts, auto-ordering controls.
PERFORMANCE

Competence curve at 0.7584 — rising. Every dollar we claim is defensible, including the $0 weeks. The proof ledger is the file your auditor opens.

Purchasing Copilot Performance
Cropped — full screen includes supplier reliability, trajectory chart, savings attribution.
Simulation on synthetic, seeded restaurant decisions — a mechanism demo. Not customer data, not a measured result. No production customers. · demo build v7 · October 2026