Design partnership
Hands-on setup. A separate price, quoted for each project.
MagicMenu / Investors
One connected system
for busy kitchens.
MagicMenu helps teams plan meals, buy ingredients, cook and serve.
AI suggests a plan. Rules check it. The kitchen team approves it.
How the business grows
Make daily work easier.
Build repeat business.
Start with meals for people who have special food needs. Then earn a lasting place in the kitchen’s daily work.
- 01Start with a kitchen.
Work with its team to build a plan that fits.
- 02Connect the daily jobs.
Help the team buy, cook and serve from the same plan.
- 03Earn as kitchens use it.
Paid setup, a monthly fee and small fees on agreed transactions.
The system we’re building
PeopleFood needs
Meal counts
Meal counts
MenuRecipes
Portions
Portions
SuppliesFood in stock
Suppliers
Suppliers
MagicMenuOne checked kitchen plan
AI suggests · Rules check · Your team approves
BuyOrder what
the kitchen needs
the kitchen needs
CookPrepare food
with a clear plan
with a clear plan
ServeGet each meal
to the right person
to the right person
↻ Record what happened. Improve the next plan.
Purchasing feesPlanned revenue
Shared-bill paymentsFairShare tested once
01 / The business model
How MagicMenu
can earn.
A kitchen pays for help getting started, then for the software and agreed services it keeps using. This model shows how those fees add up.
Software
$149/month per site after the design partnership.
Purchasing
0.9% of routed purchases, including managed procurement.
Other agreed fees
FairShare shared-bill payments or other contracted services.
Illustrative revenue model
Build a yearly example.
Change the kitchen count, food spending and setup fees. See each part of the total.
FairShare & other fees Optional inputs +
Use a separate settlement amount that is not already counted as purchasing above. The rate here is your scenario, not a quoted FairShare price.
For separately priced work, excluding services already included above.
Enter a valid, non-negative number in each field. Kitchen and project counts must be whole numbers.
Your yearly example
Total fees
$33,000Before the costs of doing the work.
- Software
- $17,880
- 10 kitchens × $149 × 12 months
- Purchasing fees
- $15,120
- $1,680,000 routed / year × 0.9%
- Design partnerships
- $0
- Enter a fee to include these projects.
- FairShare & other fees
- $0
- Optional amounts not entered.
Monthly from ongoing kitchens$2,750
Software + purchasing fees. Setup and optional fees are separate.
Design fees are not included yet. Enter a fee per project to include them.
What makes a transaction billable?
A contract must define the payer, service, eligible volume, completed event, rate, exclusions and credits. Reviewing a product or influencing an order does not create a right to a fee.
| Service | Payer / basis | Evidence status |
|---|---|---|
| Design partnership | Operator / separately quoted setup project | Scoped and quoted in writing; fee is not assumed by the model. |
| Software | Operator / active site | Monthly fee per site after the design partnership; commercial terms confirmed per agreement. |
| Purchasing | Operator or contracted partner / eligible completed purchase | Planned. No scaled procurement-fee revenue demonstrated. |
| Reconciliation & service evidence | Contracted customer / accepted work or recovery | Some invoice work demonstrated; separate fee terms unresolved. |
| FairShare | Group, household or operator / completed settlement, as agreed | One reported revenue-generating deployment. |
Fees must be confirmed under individual commercial agreements. Longer-term partner economics remain hypotheses.
02 / Trust is part of the model
The right product.
For the kitchen.
A SKU is a specific orderable product. Dietary, quality, operational and contractual requirements determine what qualifies; the operator’s overall outcome determines the recommendation.
Our design principle: MagicMenu’s own compensation must not influence eligibility or ranking. Partner relationships can coexist with neutral recommendations when fees are disclosed and operator rebates remain visible.
Explore the technology1
Choose for the operator
Eligibility → total cost → service requirements
Dietary needsQualityExisting contracts
MagicMenu compensation stays
outside the recommendation
outside the recommendation
2
Calculate the disclosed fee
Completed service → agreed terms → settlement
Design commitment. Implementation and independent testing remain proof milestones.
03 / The evidence so far
A real kitchen. A first transaction.
A focused next market.
Company-reported · September 2026 record
Operating proof01
≈260Accommodated meals
Served in one August retreat week at a working camp kitchen. A pro bono deployment supplied early operating evidence.
See the scope
more than 2,700 products organized with allergen columns; eight invoices, 156 line items digitized. Catalog size is not purchased volume.
Transaction test02
FirstFairShare revenue
A September reunion tested cost allocation and settlement. This demonstrates one transaction use case; procurement revenue remains planned.
See the scope
first transaction revenue in September 2026. The reported settlement test does not establish a repeatable procurement business or its margins.
Paid focus03
NextSenior living
Recurring meals and concentrated dietary complexity make senior living the paid design-partner focus. A first paid deployment is still a milestone to achieve.
Why senior living04 / How the business can grow
More kitchens.
More recurring flow.
Revenue can grow through more active kitchens, a larger share of eligible purchasing, repeat use and additional contracted services. Each depends on value the operator chooses to keep.
Reusable product records, recipes and invoice mappings could make the next site easier to launch. The proof is faster onboarding, fewer manual exceptions, retained purchasing and positive customer value after fees.
- 01
Adopt
Win paying kitchens with a workflow they use.
- 02
Route & retain
Complete more eligible purchases, repeatedly.
- 03
Earn & repeat
Collect contracted fees while reducing service effort.
Built from the kitchen outward
Dusty Dequine
Founder · MIT-trained aerospace engineer
Engineering experience at Boeing, Lockheed and Apple, followed by hands-on work on a camp’s accommodated dining line.
Meet the founderAbout the evidence and this model
Evidence is company-reported from the September 2026 record. Savings estimates and transaction economics beyond the FairShare test are modeled, not earned. Source basis: Current Direction and Decision Log, September 21; strategy synthesis; Transaction Revenue Strategy; SKU-Neutral Financial Model research. Full assumptions and commercial terms are available in the investor conversation.
MagicMenu reports eight provisional patent applications. These are unexamined applications, not issued patents. The procurement model, neutrality controls and cost to support each site require further operating evidence.