Skip to main content
MagicMenu
Our approach
Who it's for
  • Senior living
  • Skilled nursing
  • Camps & retreats
  • Distributors & partners
TechnologyEconomics
Sign inStart a conversationTalk to us
MagicMenu
  • Our approach
  • Who it's for
    • Senior living
    • Skilled nursing
    • Camps & retreats
    • Distributors & partners
  • Technology
  • Economics
  • Our story
  • Investors
Sign in
Start a conversation
CyclesModelProcurementWhat you payEvidence

The economics.

Know what you pay. Then measure what comes back. Software is $149/month per site after your design partnership. Managed procurement is included with a 0.9% fee on purchasing routed through MagicMenu.

Get your own baselineUnderstand the costs ↓

Your ongoing software cost

$149/month per site

Plus 0.9% of routed purchasing, including managed procurement.

See how fees work ↓

Projected · 140-person assisted living scenario

$73,841 / year

Net annual value after software and procurement fees; before the separately quoted design partnership. Includes the value of staff time released, not just cash savings.

23.8×

Projected annual value ÷ ongoing fees. Not first-year ROI or a payback estimate.

Calculation and assumptions

Mid-market assisted living model scaled from 62 to 140 diners: $229,950 annual food spend; 70% routed purchasing; $77,077 gross annual value less $3,237 annual fees. This illustrative scenario is not an industry average or measured result.

What you pay.

Three costs to understand up front.

1. Design partnership

A three-to-six-month engagement, scoped and quoted in writing before you start. This is separate from the ongoing subscription.

2. Software

$149/month per site after the design partnership. The 0.9% routed-purchasing fee is additional.

3. Transactions & managed procurement

Managed procurement is included in the 0.9% fee on purchasing routed through MagicMenu. Any separate settlement service is scoped in writing.

How procurement fees work

Managed procurement is part of the 0.9% routed-purchasing fee. The fee applies to purchases routed through MagicMenu, not your entire food budget. Your separately quoted design partnership covers implementation.

  1. Purchasing & settlement

    Transaction revenue is tied to purchasing and settlement routed through MagicMenu.

  2. Fees, made clear

    Every fee is disclosed before the first routed order. Product rankings never see those fees.

  3. Your value, checked

    You should be better off after fees, measured against your kitchen’s own baseline.

Start with a design partnership. Three to six months in your kitchen, scoped and quoted in writing. Then $149/month per site.

Beyond the FairShare settlement test, transaction revenue is modeled, not earned.

Where the hours come from.

Time back, cycle by cycle.

Compare seven residential-kitchen workflows, today and with MagicMenu. Most time comes from daily meals and diet-order changes. The model projects 16 to 40 hours a week for a 140-resident kitchen; plan conservatively around 11.9 to 25.4 staff hours a week. Select a workflow for the steps.

014 h / week
Daily meal cycle6–14 h

Cadence: Per service; typically 21 services a week · Today: 265–495 minutes across roles per service · With MagicMenu: 197–360 minutes across roles per service

The biggest weekly pool. The tray cards, station cards and production sheets are generated from one source of truth instead of printed, sorted and corrected by hand.

StepTodayTimeWith MagicMenuTimeTime saved
Order takingSelections collected tableside against a printed diet list.25–45 minSelections captured against each resident's live profile; invalid choices caught at the table.15–25 min10–20 min
Tray cards and production sheetsPrinted from the dietary system, hand-sorted by room, corrected in pen.15–30 minGenerated from the locked plan, sorted by station and route, versioned.2–5 min13–25 min
Prep and mise en placeRecipes scaled by hand to the batch size for each variant.60–120 minStation sheets show the base and its controlled variants, already scaled.45–90 min15–30 min
CookingAllergen isolation between variants juggled on the line.60–120 minThe branch model drives the sequence; clean-down steps inserted where shared equipment would carry contact forward.50–100 min10–20 min
PlatingPortion, texture and allergen matched by reading the card and the sheet.30–60 minThe card states the exact plated spec, texture level included.25–50 min5–10 min
VerificationPlates spot-checked against the diet roster before they leave.15–30 minPre-verified at the artifact: the card itself is the check; the chef sees exceptions only.5–10 min10–20 min
ServingReturns and re-fires when the wrong plate reaches the table.60–90 minFewer returns because the variants are deterministic and the card travels with the plate.55–80 min5–10 min

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Diet order change cycle4.7–9.3 h

Cadence: Ad hoc; a 140-resident community sees 5–20 a week · Today: 43–93 minutes across roles per change · With MagicMenu: 15–37 minutes across roles per change

The clinical order stays with the provider. What changes is that the order propagates to the profile, the tray card and the production sheet without a paper slip.

StepTodayTimeWith MagicMenuTimeTime saved
Order issuedThe provider updates the order in the clinical record.5–10 minUnchanged — clinical authority stays with the provider.5–10 min0 min
Clinical reviewNursing verifies the order.5–10 minUnchanged, and no longer a blocker for what follows.5–10 min0 min
Communicate to diningA printed slip, a verbal note, a paper hand-off.5–15 minThe order flows from the clinical record to the resident's profile.0–2 min5–13 min
Dietitian verificationThe change interpreted into a therapeutic-diet spec by hand.10–15 minAn impact report: which upcoming items, variants and services change.3–7 min7–8 min
Profile and tray cardCard updated by hand; the old one removed from the sorter.10–20 minA new card issued at the next snapshot.0–2 min10–18 min
Production sheetsVariant counts incremented by hand for upcoming services.5–15 minRecomputed automatically at the next snapshot.0–2 min5–13 min
Staff briefingVerbal, especially critical for high-severity changes.3–8 minThe briefing stays; the delta is highlighted for it.2–4 min1–4 min
First service under the new orderThe gap between order and tray card is where errors live.error exposureThe first service already carries the change.error eliminatedNot timed

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Substitution cycle0.75–4.8 h

Cadence: Ad hoc; typically 1–3 events a week · Today: 65–140 minutes across roles per event · With MagicMenu: 18–42 minutes across roles per event

The truck brings something different. Today that is a hallway decision and a phone call; here it is a twenty-second check with a logged approval.

StepTodayTimeWith MagicMenuTimeTime saved
Shortage identifiedNoticed at delivery or, worse, at prep.5–10 minFlagged at receipt and linked to every affected dish.1–3 min4–7 min
Impact assessmentThe chef traces which items, services and residents are affected from memory.10–20 minComputed from the graph: ingredient node → every downstream recipe and variant.2–5 min8–15 min
Candidate substitutionA hallway decision from memory of the catalog.10–20 minPre-approved alternatives ranked by availability and fit.3–7 min7–13 min
Dietary validationChecked by hand against each affected resident's restrictions.10–20 minRe-evaluated against the full roster with the same deterministic allergen logic.1–2 min9–18 min
Dietitian approvalA phone call or an email, often the same day at best.10–20 minA routed approval with the validated comparison attached; the decision is recorded.5–10 min5–10 min
Update sheets and cardsHandwritten corrections on printed sheets and cards.10–25 minA new locked snapshot; every artifact regenerated.3–8 min7–17 min
Communicate to kitchen and floorA verbal huddle; information decays across shifts.5–10 minThe huddle stays; the artifact carries the change and the delta is highlighted.3–5 min2–5 min
Log for complianceA paper log after service, if at all.5–15 minLogged automatically with timestamp, reason and approving authority.0–2 min5–13 min

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Weekly order-build cycle1–4 h

Cadence: 1–2 orders a week · Today: 95–200 minutes per order · With MagicMenu: 35–75 minutes per order

The largest recurring per-week wedge: the shopping list is generated from the plan, the counts and what is on hand.

StepTodayTimeWith MagicMenuTimeTime saved
Inventory walkCooler, freezer and dry storage walked with a clipboard.20–40 minException-oriented: par-level alerts and usage history; only exceptions need a look.10–20 min10–20 min
Reconcile menu, on-hand and usageMental math across what the menu needs and what is on the shelf.30–60 minDraft need computed across every variant for the window.10–20 min20–40 min
Real-world adjustments“We always need extra of this.”15–30 minOverrides captured once as reusable per-item rules.5–15 min10–15 min
Build the orderNeed translated into cases across the distributor's item numbers by hand.20–45 minThe order generated vendor-ready from the approved menu, the variant set, the census and inventory.5–10 min15–35 min
Send and handle the replySent through the distributor's system or by email; shortages handled later.10–25 minOne click for supported vendors; likely shortages surfaced before the send.5–10 min5–15 min

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

New resident admission2.1–3.8 h

Cadence: Ad hoc; typically 1–3 a week · Today: 85–160 minutes across roles per admission · With MagicMenu: 21–47 minutes across roles per admission

The first meal after admission is the riskiest meal a kitchen serves. Here it runs through the same plan as every other.

StepTodayTimeWith MagicMenuTimeTime saved
Intake receivedCare plan and diet order arrive from admissions on paper.15–30 minThe resident record flows from the clinical system; dining verifies.2–5 min13–25 min
Preferences capturedInterviewed and written on a card.15–30 minThe same interview, captured into a structured profile.10–20 min5–10 min
Allergen profileWritten on the diet card, communicated verbally.10–15 minCoded to the nine-allergen schema with severity.3–7 min7–8 min
Meal plan configuredThe chef and dietitian work out which items fit, by hand.20–40 minEvery upcoming item evaluated against the new profile; the dietitian reviews.5–10 min15–30 min
Tray card generatedPrinted and inserted into the sorter.10–15 minGenerated at the next snapshot.1–3 min9–12 min
Production sheetsVariant counts incremented by hand.10–20 minRecomputed for every upcoming service.0–2 min10–18 min
Census updatedFlows to the next order only if someone remembers.5–10 minPropagates to the next draft order automatically.0 min5–10 min
First mealHighest-risk meal of the stay.error exposureAs reliable as any other because it came through the same plan.error eliminatedNot timed

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Receiving and inventory feedback1.25–2.7 h

Cadence: Every delivery; typically 2–3 a week · Today: 55–100 minutes per delivery · With MagicMenu: 26–46 minutes per delivery

Modest on its own; it compounds, because what arrived and what was used feed next week's order.

StepTodayTimeWith MagicMenuTimeTime saved
Delivery receiptChecked against the purchase order line by line.15–25 minThe unload is unchanged; the checklist is pre-populated and only exceptions are flagged.15–20 min0–5 min
Invoice scan and matchFiled and reconciled against the order by hand.10–15 minCaptured and auto-matched; only mismatches need a person.3–8 min7 min
Inventory updateReceived quantities keyed in item by item.5–10 minInventory increments from the matched invoice; unit conversions handled.1–3 min4–7 min
Post-service depletionReduced by theoretical usage; leftovers rarely logged.10–20 minDepletion computed from what was actually produced, variant by variant.2–5 min8–15 min
Drift detectionSpotted ad hoc, usually after a shortage.15–30 minRepeated mismatch patterns surfaced automatically for review.5–10 min10–20 min

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Approved menu cycle0.75–1.75 h

Cadence: Every 4–6 weeks; seasonal refresh 2–4× a year · Today: 4.75–10.5 hours per cycle · With MagicMenu: 3–7 hours per cycle

The roster is reconciled against every menu item at approval — a step the baseline workflow never has time for.

StepTodayTimeWith MagicMenuTimeTime saved
Cycle menu creationChef creates or pulls forward a cycle menu from memory and files.2–5 hPrior menus re-ingested with their structure intact; recipe-to-ingredient links surface constraint conflicts as the chef works.1.5–4 h0.5–1 h
Dietitian reviewNutritional adequacy, diet appropriateness and compliance, reviewed by hand.1–2 hThe menu arrives pre-validated against therapeutic-diet parameters; the dietitian reviews exceptions.0.5–1 h0.5–1 h
Roster reconciliation and variant optimizationNot a discrete step; the cost surfaces later as ad-hoc special plates.0.25–0.5 h (partial)Every resident's constraint set checked against every item; the fewest safe variants of each dish designed here, not at the pass.0.25–0.5 h0 h
Cost and supplier realism checkPer-person-day targets and availability checked from memory and the last invoice.1–2 hInvoice and order history pre-flag items outside target or likely short.0.5–1 h0.5–1 h
Finalization and publicationCompiled and distributed to the kitchen, the dietitian's file and compliance.0.5–1 hA locked snapshot is the source record for ordering, production and the tray cards downstream.0.25–0.5 h0.25–0.5 h

Modeled time saved per step: lower estimate minus lower estimate; upper minus upper. “Not timed” marks outcomes without a duration estimate.

Selected total across these workflows: 16.5 h / week.

Projected savings model.

Annual value for a reference kitchen, using fixed midpoint labor assumptions. Choose an operation to see its benchmark.

Assisted living — premium · 88 daily diners · 24 special diets a service · $208,780 food spend a year

Per site, before the design-partnership fee and $149 per month software cost.

From gross value to what you keep

  1. Labor+ $46K
  2. Food waste+ $14K
  3. Compliance+ $12K
  4. Verified procurement+ $4K
  5. MagicMenu's share−$1K
  6. You keep= $74K
The arithmetic
Menu-planning + procurement hours a week today21
Compliance-documentation hours a week today14
Special diets per service24
Hours recovered a week20
Blended loaded rate$43.87/h
Labor savings a year$45,646
Food-waste pool a year (spend × waste %)$91,863
Food-waste savings a year (15% of the pool)$13,779
Compliance hours recovered a week4.6
Compliance savings a year$11,996
Food spend routed (70%)$146,146
Verified procurement savings (3.0% of routed)$4,384
MagicMenu's share (30%)−$1,315
You keep of the procurement savings$3,069

Fixed cycles (menu planning, procurement) and variable cycles (diners × diets) are indexed to the reference profile (140 residents, 24 diets, 21 planning hours a week); loaded rates are hours-weighted across dining roles at BLS wages with a 30 percent benefit burden; the routed share and the verified-savings rate are the model's base case. Very large kitchens run past the model's reference; read them as direction, not a number.

Quick estimate · including seasonal camps
12–25 hkitchen staff hours per operating weekabout 0.3–0.6 of a full-time position
$52K–$85Ka year, before feeslabor recovered + waste avoided + compliance hours

Mostly from the Daily meal cycle and the Diet order change cycle.

Anchored to 11.9 to 25.4 staff hours a week at a 140-resident assisted-living community; residents scale the hours sublinearly and stop at 500. Modeled, not measured.

Illustrative camp scenario, not measured results. Extrapolates the care time model using the camp archetype’s planning workload, wages and food budget; assumes a 20-week reference season. Set your operating weeks. No RD savings assumed. Your baseline replaces these assumptions.

Managing procurement.

  1. Match products

    Review ingredients, pack sizes and approved substitutions against the menu.

  2. Plan the order

    Connect meal counts and quantities to the products your kitchen needs.

  3. Check what arrives

    Review substitutions and invoice differences; flag issues for follow-up and credit.

Connect the menu to what you buy.

Nine levers that save and three that cost, on the spend you route — contract utilization, invoice recovery, pack-size and substitution checks. Net, 3.75 percent of routed spend at full maturity, before MagicMenu's share.

One real catch: a distributor substitution on Annunciation Heights's invoice, 12 percent over the item it replaced — caught, blocked before the pull list, and flagged for credit.

The twelve levers

  • Contract utilization +0.60%

    Activating and using the contracts you already have.

  • Invoice and contract-compliance recovery +0.50%

    Cash recovery and prevented overcharge.

  • Distributor pricing and service terms +0.70%

    Volume, prompt-pay and delivery-size mechanics distributors already publish.

  • Cooperative or GPO switch (tier-adjusted) +0.30%

    Only where eligibility and lost tiers allow it.

  • Multi-supplier optimization +0.40%

    Broadline, regional and specialty competition on the same specification.

  • Retail and same-day fill-in +0.10%

    Small-quantity and minimum-order exceptions.

  • Order timing, delivery size and payment behavior +0.40%

    Fewer, fuller drops; paying the way the terms reward.

  • Product standardization and approved equivalents +0.50%

    Requires culinary and safety approval; ranked compensation-blind.

  • Aggregated network contracts +0.70%

    Scales with routed volume; a later rung.

  • Friction: freight, minimums, split cases −0.15%

    Added back to the optimized cost.

  • Friction: lost rebates, tiers and credit value −0.20%

    Added back to the optimized cost.

  • Friction: service, switching and working capital −0.10%

    Added back to the optimized cost.

For illustration: every $100,000 of routed purchasing would yield about $3,750 in net purchasing savings before MagicMenu's share — a modeled percentage at full maturity, not a guaranteed return.

How we know.

  • Verified A public source you can open — identified beside the figure.
  • Company-reported Counted by us in a real kitchen; with source details attached to the figure.
  • Modeled from a 140-resident reference; being validated in live kitchens; replaced by your own baseline in the first phase.

Source details remain attached to the figures. Projections are not measured results.

What "your own baseline" means

Homepage role splits and seasonal camps

The six homepage bars divide existing modeled pools: by default, kitchen labor is 40% chef, 20% front of house and 40% back of house. The separate documentation pool is split equally between RD and admin. These are allocation assumptions at blended rates, not measured savings for each role. Camps assume no RD recovery.

The camp scenario extrapolates the care time model using the existing 220-guest seasonal camp archetype: 13 planning/purchasing hours versus 21 in the care reference, $29–$31 loaded labor rates, and a $180,000 food-budget scenario. A 20-week reference season is an explicit planning assumption; changing operating weeks scales seasonal value. Population scales hours sublinearly (exponent 0.8). It is not camp outcome evidence.

In the first phase we digitize your invoices, rebuild your recipes from your menus, count a week of service and weigh what comes back. Food cost per served meal, waste, labor minutes, substitutions and rework — each labeled by how it was measured. The projections on this page are then replaced by your numbers, and the after is measured the same way.

Get your own baseline

All savings on this page are projections from reference kitchens, not measured results. Your own baseline replaces these assumptions.

Get your own baseline.

Thirty minutes with Dusty. Bring your dietitian to the first call if diets are clinical.

Start a conversation
MagicMenu

Complex needs.
Simpler kitchens.

dusty@magicmenu.ai

Explore

  • Our approach
  • Who it's for
  • Examples
  • Technology
  • Sources

Your setting

  • Camps & retreats
  • Senior living
  • Skilled nursing
  • Distributors & partners
  • Reunions & group trips

More

  • Our story & team
  • Savings
  • Investors
  • Press
  • Contact

MagicMenu provides operational and informational support, not clinical, medical, or nutritional advice. Allergen-screened menus are built from ingredient screens against currently available product data; unknown data never passes a plate. They are subject to verification, and to the operator's own cross-contact controls, which reduce but cannot eliminate risk. Final ingredient, service, and guest-safety decisions rest with the operator. Guest information is handled under written agreements and appropriate privacy safeguards.

Illustrative people, food and kitchen images are concepts. Actual photographs and product outputs are identified in their captions.

Schedule a conversation

© 2026 MagicMenu, Inc. · Denver, ColoradoPrivacyTerms