Three answers every week from the Restaurant365 data you already have. Each one with the evidence, a label, and an owner.
Seven business days from data access. No success fee. You approve every finding.
The three questions
Restaurant365 records what happened. PeakOps tells you what deserves investigation, which findings are trustworthy, and whether the fix worked.
Price steps on your top 25 purchased items the week a distributor moves, matched store by store so a change in who bought is never mistaken for a change in price. Regional parity on the same items, compared only in weeks where both regions bought.
The same ribeye cost one region $1.23 a pound more than another, worth $24k to $70k a year.
Theoretical versus actual by store over four weeks, count-adjusted where inventory counts exist. Stores that cannot be measured are named, with why, instead of being averaged in.
Food cost ran 0.45 points above theoretical across one group, about $200k a year, concentrated in four stores. Six of ten stores did not count.
Unmapped items, missing counts, booking rows, stale recipes and commissary flows, each with the person who can fix it in Restaurant365. The cleanup list is what unlocks the first two answers.
Fifty booking rows to review and five menu items with no recipe, worth $62k of sales a month, invisible to theoretical cost.
Step one
One report, delivered within seven business days of usable data access, and a 45-minute readout with finance and operations in the room to agree up to three priority investigations.
$7,500 for 11 to 25 locations. Credited in full against your first quarter of the weekly service if you continue within 30 days of the readout.
Which of the three questions your data can answer today, and the cleanup list that unlocks the rest.
Price steps on the top 25 items over 90 days. Cross-region and cross-distributor parity on the top 10, priced per year.
Food cost by store over the trailing four weeks, with the stores that cannot be computed named and why.
The booking-error list with owners, and what your credit memo flow already shows about each vendor.
Step two
After the audit, the Margin Integrity Monitor delivers the answers inside the weekly email your controller already reads. Open items come back at the top of the next brief until they close.
The first eight weeks are calibration. For a ten-location group that is $12,000 a year against the controllable gaps the audit found. No contract until you have seen eight weeks of answers.
A detector-calculated amount that still lacks decisive evidence. Shown as a range or a point, never as savings.
A person checked the source invoice, the agreement and the arithmetic. Only a person can set this label.
The vendor billed correctly. The fix is an entry in Restaurant365, and it is assigned to whoever keeps your books clean.
If an agreement later shows a vendor billing above contract, that goes to your AP team with the evidence attached. It is not a PeakOps service.
It does. Ask when your team last opened it, and what they did next. PeakOps delivers the answer every week, with the cleanup list attached and an owner on each line, inside the email your controller already reads.
The first thing the audit tells you is which stores the report can be trusted for. Usually it is not all of them.
A fit call covers your Restaurant365 setup, your regions and distributors, and who on your team would act on a cleanup list. If it fits, the audit starts the week you grant data access.
