Why Tossed Leaf can become an intelligent food operating platform.
Investor discussion draft
Food × wellness × operating software
Personalized food, built as a scalable system.
Tossed Leaf combines made-to-order food, TL-AI wellness guidance, direct customer ownership, partner distribution, kitchen operations, delivery tooling, loyalty, and payments in one controlled platform.
Lebanon launchUAE scale-upGCC expansionLondon + USA options
TOSSED LEAF
PersonalizeOrderOperateLearnRetainExpand
10Built-in meal categories
1–14Meals per personalized plan
4 → 80Illustrative five-year locations
25Investor dossier chapters
02 / 25
Executive summary
The business, the opportunity, the plan, and the funding logic.
Investor discussion draft
The opportunity
Consumers choose between broad delivery marketplaces, rigid meal-prep subscriptions, and restaurant apps with little useful personalization. Tossed Leaf is designed to own the direct relationship and turn each order into better preference, nutrition, operations, and retention data.
The operating answer
Launch asset-light cloud kitchens and selected company-operated flagships, add partner kiosks and embedded ordering surfaces, then scale with a controlled partner model. Every format runs on the same menu, customer, reward, payment, availability, and order lifecycle.
$4.5MIllustrative first institutional round24-month staged deployment
Why now
Digital ordering is habitual, customers expect transparency, and restaurants need first-party economics. Generative AI improves relevance, but only when constrained by real inventory and verified portions.
Why this platform
The current product already spans ordering, nutrition, operations, partner kiosks, delivery, payments, PWA notifications, rewards, affiliates, and weekly wellness programs.
What must be proved
Repeat purchase, verified food cost, on-time preparation, CAC payback, subscription retention, AI acceptance, safety compliance, and profitable mature-site contribution.
03 / 25
Problem and market gap
Why ordering, nutrition, loyalty, and restaurant operations remain disconnected.
Investor discussion draft
01
Marketplace dependency
Marketplaces supply discovery and logistics but usually intermediate the customer relationship, standardize the experience, and add commission pressure. A restaurant can grow orders while weakening first-party retention economics.
02
Personalization without operational truth
Generic wellness apps may suggest meals that are unavailable, structurally incomplete, commercially irrational, or disconnected from a kitchen’s real portions and allergens.
03
Rigid meal subscriptions
Traditional meal plans can feel repetitive and inflexible. Customers want variety, swaps, transparent nutrition, one-off ordering, and plans that adjust with preferences and availability.
04
Fragmented restaurant software
Ordering, loyalty, delivery, kitchen boards, partner commissions, affiliates, payments, and notifications often live in separate tools with duplicated records and inconsistent states.
Value lost in a fragmented order
Ad clickpaid acquisition
→
Marketplacelimited identity
→
Generic menulow relevance
→
Kitchenseparate system
→
Deliveryseparate status
→
Customer leavesweak learning
Tossed Leaf converts the same order into a learning loop
Direct discoverysource known
→
Account + profileconsented context
→
Validated meallive menu truth
→
Operationscapacity-aware
→
Fulfillmenttracked status
→
Rewards + repeatretention loop
04 / 25
Solution and positioning
A personalized healthy-food platform with an AI nutrition companion.
Investor discussion draft
Not merelya food-delivery appA personalized healthy-food platform with an AI nutrition companion
Prepare under local cash policy; reconcile at shift end
No-show/cash handling
Generic provider
Admin verification unless signed integration exists
A browser redirect is never proof of payment
False success/chargeback
USDT/USDC
On-chain confirmations
Prepare only at configured payment state; monitor partial/underpaid/expired
Network fee, wrong chain, compliance
Reward points
Atomic server deduction
Full or partial discount; restore on failure/cancellation/refund
Liability and abuse
10 / 25
Partner and affiliate network
Kiosks, embeds, location reservations, commissions, and distribution.
Investor discussion draft
Partner locations
Public map shows available and taken opportunities, supports search and Near Me, and reserves a selected location during application review to prevent conflicts.
Touchscreen kiosk
Secure location session, shared live menu, Health Wizard, nutrition, payments, mixed orders, WhatsApp receipt, attribution, full-screen touch interface.
External embed
A secured Web Component places the kiosk on approved non-WordPress partner domains without an iframe, using a location site key and origin controls.
Partner reporting
Order history, search, filters, customer and fulfillment detail, nutrition, payment state, sales, pending/paid fees, and CSV export.
Affiliate program
Application and approval, anonymous referral codes, signed attribution cookie, direct-order commissions, hold period, payouts, consent and privacy records.
Commission integrity
Only eligible paid/completed orders mature. Failed, expired, cancelled, and refunded transactions void or flag commissions without rewriting payout history.
Distribution flywheel
1Partner site, gym, office, hotel, creator
2New customer enters a branded ordering surface
3Central menu and operations fulfill consistently
4Attribution and commissions remain auditable
5Customer joins direct account, rewards, and wellness
6Repeat demand improves partner and kitchen economics
Channel
Best use
Economics
Control
Direct web/PWA
Highest-value retained customer
No marketplace commission; CAC required
Highest
Partner kiosk/embed
Contextual distribution
Configurable referral/commission
High menu and order control
Affiliate
Performance acquisition
Pay on eligible conversion
High attribution control
Marketplace
Incremental discovery and logistics
Higher variable fee
Lower customer ownership
Corporate plan
Recurring volume
Contracted price and schedule
High forecastability
11 / 25
Business model
Revenue streams, operating formats, and the hybrid owned/partner structure.
Investor discussion draft
Revenue engine
55% Company-operated food sales
22% Partner royalties/commissions
10% Weekly programs and corporate plans
6% Delivery/service contribution
4% Technology/service fees
3% Other approved revenue
Illustrative mature revenue mix. Actual accounting treatment depends on principal-versus-agent analysis, contracts, and jurisdiction.
Stream
Customer/payer
Mechanism
Margin logic
Stage
Direct meals
Consumer
Item + delivery/service
Food, labor, packaging, delivery
Core now
Weekly programs
Consumer
5/10/14 meals; prepaid or scheduled
Better demand visibility, retention
Product built; operations to prove
Corporate wellness
Employer
Contract, credits, scheduled drops
Dense delivery and repeat volume
Launch channel
Partner location
Partner/operator
Referral, royalty, or revenue share
Asset-light central platform income
Infrastructure built
Affiliate
Tossed Leaf pays
Performance commission
Variable CAC, not revenue
Infrastructure built
Technology license
Qualified operator
Setup + recurring fee
High gross margin after support
Future option, not base thesis
Format A · Cloud kitchen
Lowest front-of-house capex; delivery/pickup focused; ideal for initial city cells and centralized production.
Bottom-up planning model—not third-party market valuation. Served-city population basis: Lebanon launch corridor, Dubai, Abu Dhabi, Riyadh, Jeddah, Doha, London, and one initial US metro. Refresh with official city data and primary research before fundraising.
Illustrative expansion priority score / 100
Riyadh
86
Dubai
85
Abu Dhabi
82
Jeddah
81
Kuwait
79
Doha
77
London
75
Miami
73
Lebanon
70
Scoring logic
Addressable spending
20%
Digital delivery behavior
20%
Healthy/personalized fit
15%
Operational and regulatory feasibility
15%
Expected unit economics
15%
Strategic proximity and management reach
15%
Scores are decision tools, not market-size facts. They must be refreshed with rent, labor, delivery fees, licensing, tax, competitive pricing, and customer research before a lease or franchise commitment.
Lebanon · proof and brand lab
Role: validate recipes, operations, retention, and central team at lower nominal setup cost.
PCI scope review, AML/sanctions for crypto, reconciliation, fraud controls
Finance/risk
Marketing
Wellness-not-medical disclaimer
Claims approval, influencer disclosure, age rules, local consumer law
Legal + brand
Lebanon
Food establishment licensing, municipal/public health rules, employment, tax, e-commerce/privacy, consumer protection, and payment legality require local counsel and authority confirmation.
UAE
Food authority/municipality approvals, VAT, corporate tax, labor, consumer protection, UAE PDPL, and emirate-specific requirements. Treat wellness data conservatively.
KSA
SFDA and municipal requirements, ZATCA tax/e-invoicing, labor localization, Saudi PDPL, halal and labeling standards, payments and promotions.
Qatar
Food registration/safety, municipality licensing, tax and labor, personal-data law, labeling, imports, payments, and delivery operations.
London / UK
Food business registration, hygiene ratings, FSA allergen rules, UK GDPR, employment, VAT, advertising, packaging and delivery obligations.
USA
Federal, state, county, and city layers; FDA menu labeling at qualifying scale; sales tax, employment, privacy, franchise, nutrition claims, insurance, and food codes.
Non-negotiable policy
No allergen-free guaranteeNo medical diagnosisNo hidden health data sharingNo AI-invented ingredientNo unverified nutrition claimNo payment-by-redirect assumptionNo partner without auditNo launch without legal sign-off
21 / 25
Risks and mitigations
Operational, financial, regulatory, technology, and brand downside cases.
Investor discussion draft
Risk
Likelihood
Impact
Leading indicator
Mitigation
Weak mature-site economics
Medium
Critical
Contribution/order; food/labor variance
Gate openings; shrink radius/menu; renegotiate site and delivery
Pause a market if food safety fails, cash runway falls below policy, mature sites miss contribution thresholds, or customer trust degrades.
Recovery criteria
Root cause verified, controls changed, staff retrained, tests passed, liability funded, and board/risk owner approves restart.
Resilience
Multiple suppliers, limited radius, staged capital, local substitutions, role separation, backups, dual communications, and documented fallback processes.
22 / 25
Capital plan
Illustrative raise, use of funds, runway, release gates, and investor reporting.
Investor discussion draft
Illustrative $4.5M use of funds
Kitchen capex + equipment
$1.5M
Technology/data/security
$0.8M
Launch marketing + partnerships
$0.8M
Working capital + inventory
$0.8M
Central team + training
$0.6M
Compliance/insurance
$0.2M
Contingency
$0.1M
Round objective
Fund approximately 24 months to prove reproducible Lebanon/UAE operations, prepare the KSA entry system, strengthen security and governance, and produce investor-grade operating evidence.
$4.5MIllustrative raise
24 mo.Target runway
4–8Proof locations before acceleration
3Board release gates
Capital release gates
Gate 1
Product + proof
Verified recipes/nutrition, safety system, direct cohort baseline, first-site contribution trend.
Gate 2
UAE replication
Licensing, two sites or cells, corporate/partner demand, CAC payback, on-time operations.
Concrete customer, kitchen, corporate, partner, and crisis examples.
Investor discussion draft
01 · Dubai office customer
Dina needs a 550-calorie high-protein lunch
Her account profile excludes nuts and favors high protein. TL-AI composes a chicken rice bowl with vegetables and a compatible sauce from live ingredients. Validation checks category structure, portions, calories, allergen flags, availability, and price. Dina replaces one vegetable, applies points partially, schedules delivery, and tracks the driver. The completed order updates repeat history and earns new points.
Value: relevance + conversion + retained identity.02 · Beirut family order
One cart, different needs
The family combines a salad, pizza, baguette, and protein dessert. Each item has its own required base/structure; nutrition is summarized per item and total. The signed-in customer’s delivery details prefill, an exact pin is required, and the kitchen receives one deduplicated order with clear item detail. Push messages show preparation and delivery status.
Value: broader occasion and larger basket.03 · Corporate weekly program
Forty employees across two office days
The employer buys meal credits without seeing employees’ wellness data. Employees select or approve meals individually. Tossed Leaf aggregates production by day, ingredient, and delivery cluster while preserving account privacy. Substitutions occur against live inventory; consolidated delivery improves density.
The gym receives a secure kiosk plus an approved-domain Web Component. Orders use the shared menu, live availability, nutrition, and payment methods. Partner attribution is automatic; only completed/eligible sales mature into commission. The gym sees its history and payout state while Tossed Leaf retains centralized kitchen and safety control.
Value: asset-light distribution + auditable CAC.05 · Friday rush
Capacity prevents overpromising
Operations reaches the configured slot limit. The next customer sees a later local-time slot rather than an impossible promise. A sold-out ingredient disappears across direct ordering and kiosks. Kitchen staff move tickets through safe states; a driver starts sharing only after assignment and readiness.
Value: service recovery before failure.06 · AI/provider outage
Personalization degrades safely
The model request fails. The customer’s TL-AI credit is restored, cached valid results remain available, and the deterministic nutrition engine supplies a controlled fallback where possible. Normal ordering, Chef’s Picks, checkout, and kitchen operations continue without the model.
Value: AI is additive, not a single point of failure.07 · Partial stablecoin payment
Payment is not assumed complete
The private payment service detects an underpayment and reports an exception through a signed callback. The order remains in the correct payment-aware state; the kitchen and partner commission do not treat it as paid. Reconciliation is visible to management.
Value: financial integrity.08 · Allergy concern
Digital filter plus human process
The profile removes flagged ingredients and the order carries the customer’s note to the kitchen. The interface repeats the cross-contact warning and does not claim allergen-free food. Staff follow the location SOP, document the decision, and contact the customer if the request cannot be served safely.
Value: safer expectations and escalation.
25 / 25
Methodology and sources
Assumptions, research references, limitations, and diligence checklist.
Investor discussion draft
Method
Product inventory: reviewed the current Tossed Leaf builder, TL-AI wellness, operations, payments, PWA, affiliates, kiosk, embed, partner history, map, landing, and brand modules.
Market logic: used public demographic, public-company, health, food, privacy, and regulatory sources to frame—not guarantee—opportunity.
Bottom-up operations: modeled orders/day × AOV × operating days by location archetype.
Network model: separated total system sales from platform revenue and applied an illustrative partner take.
Scenarios: built conservative, base, and upside paths with visible assumptions and expansion gates.
Risk treatment: identified controls that must exist before country launches and institutional capital.
Model limitations
No audited historical financial statements were provided
No verified current customer, revenue, cohort, or order dataset was provided
No signed lease, franchise, supplier, corporate, or investor commitments are assumed
Taxes, VAT, duties, financing, depreciation, and working-capital detail are simplified
City rent, wage, delivery, ingredient, and licensing quotes require live local diligence
Public sources can change; counsel and authorities remain authoritative
Management diligence checklist before external circulation
Insert actual legal entityInsert founder/team biosInsert historical financialsInsert active users/ordersInsert repeat cohortsInsert actual food/labor costInsert current sitesInsert supplier evidenceInsert IP ownershipInsert fundraise termsLegal review all claimsUpdate research date