PlateLine — plate-cost tracker for independent restaurants

1. One-liner

Forward your supplier invoices; we keep every dish’s margin live and flag which ones to re-price.

2. Trend signal — why now?

Three things collided in the last 12 months.

First, the margin squeeze is no longer abstract — it’s structural. US menu prices rose 3.6% YoY as of April 2026, the slowest pace in 15 months, but food costs are now more than 35% above pre-pandemic levels and only 42% of US restaurants were profitable in 2024. Protein and produce keep swinging. A flat markup formula set in January is wrong by March. The industry’s own coaches are blunt about the blind spot: “Easily 90% of all restaurants do not have accurate, up-to-date costs for all the items they sell” and “restaurants doing $1M+ in sales but losing $50k/year because their costs scaled up with volume while prices stayed flat.”

Second, the incumbent tools that should solve this are too heavy and too expensive for the 70% of US restaurants that are single-unit independents. MarketMan runs $239–$429/month per location, and its reviews are full of the exact failure that matters: “Invoice scanning did not work 50% of the time and support would take days to respond,” “the setup is very tedious,” and “trying to cancel MarketMan was like jumping through flaming hoops… a required 60-day notice.” Apicbase is enterprise-grade and priced to match. These are inventory ERPs that happen to do costing — overkill for an owner who just wants to know which five dishes are bleeding.

Third — and this is the unlock — vision models in 2025–2026 finally parse a crumpled, hand-totalled supplier delivery note reliably and cheaply. The single feature MarketMan’s customers say breaks half the time is now a solved, sub-cent-per-page primitive. That’s the wedge: do the one painful thing (turn a photo of an invoice into structured line-item prices) flawlessly, and skip the 200-feature ERP no independent will ever configure.

Provenance:

• Signal 1 (demand): “How Restaurants Lose Money Working with Food” — 90% of restaurants lack accurate up-to-date item costs; $1M-sales restaurants losing $50k/yr — https://www.restaurantowner.com/public/How-Restaurants-Lose-Money-Working-with-Food.cfm — observed June 2026
• Signal 2 (economic/competitor): MarketMan pricing $239–429/mo + review complaints (“invoice scanning did not work 50% of the time”, “60-day notice”, “tedious setup”) — https://www.g2.com/products/marketman/reviews & https://www.g2.com/products/marketman/pricing — June 2026
• Signal 3 (feasibility/macro): Restaurant food costs 35%+ above pre-pandemic, only 42% of US restaurants profitable in 2024, menu inflation 3.6% YoY April 2026 — https://oysterlink.com/spotlight/inflation-impacting-restaurant-menu-prices-statistics/ — June 2026 Category: Tech-unlock

3. The opportunity

The job-to-be-done is small and sharp: “tell me which dishes stopped making money since my supplier prices moved, and what to re-price them to.” Nobody serves that job cleanly for an independent.

The incumbents are inventory-management ERPs (MarketMan, Apicbase, Craftable). They bundle costing inside theoretical-vs-actual inventory variance, PAR levels, and purchase-order workflows that demand a full SKU catalog and weeks of setup. That’s a great fit for a 15-location group with a finance person. It’s a wall for a single-owner taqueria. The POS giants (Toast, Square, and in India Petpooja) ship a “food costing report,” but it’s a static module the owner has to feed manually and re-feed every time a price changes — which is exactly the chore they never do.

The 10× cut is to invert the workflow. Instead of “build a perfect inventory system, then derive costs,” PlateLine starts from the invoices that already arrive every week. The owner snaps or forwards each supplier delivery note. We extract every line item and unit price, map ingredients to recipes once, and from then on every dish’s plate cost and margin updates itself. When a case of chicken thighs jumps 18%, the owner gets a one-line nudge: “Butter chicken margin dropped to 58%, below your 65% target. Suggested price: ₹X / $Y.” No inventory counts, no PAR levels, no PO module. The AI does the data-entry that kills every spreadsheet attempt.

4. Target market

• Primary customer: Owner-operators of single-location independent restaurants, cafés, and cloud kitchens — 1–3 locations, no dedicated finance staff, the owner does the books. Sweet spot is full-service and fast-casual where recipes have 6–15 ingredients and prices move. Starts US/UK/AU/Canada (English, USD-anchored willingness-to-pay); India/SEA as a localized second wave.
• Why they buy: They already suspect a few dishes are losing money but can’t prove which, and re-costing by hand after every price change is the chore that never happens. In their words: popular ≠ profitable, and “if you do not know what each item on your menu costs, you may be leaving 5% on the table.” On thin restaurant margins, 5% is the whole profit.
• Rough TAM reasoning: ~749,000 US restaurants; ~70% single-unit independents (~525k); ~152k single-location full-service alone. Add UK/AU/Canada and the English-first serviceable base is comfortably 700k+ businesses. India adds ~500k+ organized standalone restaurants for the localized tier. Capturing even 0.5% of the English-first base at $39/mo is ~$1.6M ARR.
• Why now for them: The squeeze is acute now — 58% of US restaurants unprofitable, protein volatility, and menu-price fatigue (customers resist blunt across-the-board hikes, so owners need surgical per-dish re-pricing). The pain that was “nice to fix someday” became “fix this quarter.”

5. Product sketch (MVP)

• Invoice inbox: owner forwards a photo, PDF, or email of any supplier delivery note (WhatsApp, email, or in-app camera). AI extracts each line item, quantity, unit, and price.
• Recipe builder, once: owner enters each dish’s ingredients and portions a single time (or imports from a spreadsheet/POS menu). Guided, 10 dishes in an afternoon.
• Live plate cost & margin per dish: every dish shows current food cost %, contribution margin, and trend since last price change — auto-updated whenever a new invoice lands.
• Re-price alerts: push/WhatsApp nudge when any dish crosses the owner’s target margin, with a suggested new price that hits the target.
• Menu engineering view: the classic 2×2 (popularity × margin) using POS sales data if connected, or manual top-sellers if not — labels Stars / Plowhorses / Dogs.
• Price-watch on ingredients: flags supplier price spikes (“eggs up 22% this month”) so the owner can substitute or renegotiate.
• Weekly margin digest: one email/WhatsApp summary — “3 dishes slipped below target, here’s the fix.”

6. AI angle — what’s load-bearing

Remove the AI and the product collapses back into the spreadsheet every owner already abandoned. The load-bearing job is turning unstructured, messy, handwritten-or-printed supplier invoices into clean structured line-item prices, automatically, every week. That is precisely the step incumbents’ older OCR botches half the time and the reason owners stop maintaining their costing. Modern vision-language models do it reliably and for a fraction of a cent per page. Secondary AI work: fuzzy-matching invoice line items (“Chkn Thigh BNLS 5kg”) to the owner’s named ingredients, and generating the plain-language re-price suggestion. The data-entry elimination is the product.

7. Localization angle (if any)

Strong optional second wave, not the wedge. India: WhatsApp-first invoice forwarding (suppliers already send bills over WhatsApp), ₹ pricing with a ₹799/mo tier where $39 won’t land, and GST-aware costing (standalone restaurants are 5% GST with no input-tax-credit, so the full input cost hits margin — making accurate plate cost even more critical than in credit-recoverable markets). Petpooja owns India POS but treats costing as a static report; a WhatsApp-native, auto-updating layer that sits beside the POS is a real gap. Launch English-first (cleaner WTP, faster sales cycle), localize once the core loop is proven.

8. Business model — path to $1M–$5M ARR

• Pricing: $39/mo solo (one location, unlimited invoices), $89/mo for 2–3 locations + POS sync. India tier ₹799/mo. Undercut MarketMan’s $239 floor by ~6×.
• ACV: ~$520/yr blended (mix of solo and multi-location).
• Rough math to $1M ARR: ~1,900 paying restaurants at ~$44/mo average. Against a 700k+ English-first base, that’s 0.27% penetration. Eminently reachable.
• Rough math to $5M ARR: ~9,500 restaurants, or a lower count plus a $19/mo “menu-engineering pro” upsell and a supplier-price-benchmark add-on. Requires a repeatable channel (see §9) and <4% monthly churn.
• Expansion path: add locations; add POS integrations (per-integration value); add a benchmark product (“you pay 12% more for tomatoes than nearby restaurants”) that compounds with data scale; eventually a supplier-comparison/RFQ layer.

9. Go-to-market wedge — first 100 customers

• Restaurant accountants & bookkeepers as a channel. A bookkeeper serving 20–40 restaurants feels the costing pain across their whole book. Recruit 10 of them with a revenue-share; each onboards a handful of clients. This is the fastest path to the first 100 — concentrated, warm, pre-qualified.
• The MarketMan/Apicbase refugees. Scrape G2/Capterra/Reddit for the public complaints already quoted above (price, broken scanning, brutal cancellation). DM/email those exact owners a 60-second Loom showing an invoice photo turn into live dish margins. The pain is named and dated.
• Restaurant owner communities. r/restaurateur, r/KitchenConfidential (owner threads), regional restaurant-association Slack/Facebook groups, and local chef WhatsApp groups in India. Post the menu-engineering teardown, not an ad — “I costed 10 dishes from this menu, here’s the 3 losing money.”
• Reseller motion via POS-adjacent consultants who set up Toast/Square/Petpooja for independents and get asked “but is my menu profitable?” — they have nothing to hand over today.

10. Build complexity — justification

Low. The whole stack is off-the-shelf: a vision-language API for invoice extraction, standard web/mobile front end, a simple recipe-and-cost data model, and a notification layer (email + WhatsApp Business API). No inventory engine, no PO workflow, no hardware. The only genuine engineering care goes into the invoice-extraction accuracy loop and ingredient fuzzy-matching — both tractable with off-the-shelf models plus a correction UI. A solo technical founder ships a credible v1 in 6–8 weeks; a pair gets to POS integrations in ~3 months.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Pure SaaS, no regulated data.
Ethical — no harm / dark patterns	✅	Helps owners survive; honest pricing, easy cancel (the anti-MarketMan).
Market exists (evidence above)	✅	749k US restaurants, paid incumbents at $239–429/mo, sourced complaints.
1–5 person team can build this	✅	Off-the-shelf stack, 6–8 week v1.
Launchable with <$50K / ₹40L	✅	Inference + infra + WhatsApp API; well under budget.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Real money lost weekly; 58% of restaurants unprofitable. Slightly below max because owners have tolerated it for years — it’s chronic, not always acute on a given day.
Demand evidence	15	12/15	Multiple sourced signals: paid incumbents, named complaints, industry “90% lack accurate costs.” Docked for thin direct verbatim from independents (vs. consultants).
Build feasibility	15	13/15	Off-the-shelf vision + standard stack, 6–8 week v1. The hard part (OCR) is now a commodity primitive.
Distribution clarity	15	11/15	Bookkeeper channel + named refugee list are concrete; conversion math still unproven.
Revenue mechanics	15	11/15	Pricing benchmarked 6× under incumbent; $1M needs only 0.27% penetration. Churn risk on SMB restaurants is the open question.
Time to first revenue	10	8/10	Self-serve trial-to-paid; first dollars within weeks of launch.
Defensibility	10	5/10	Execution + workflow lock-in + accumulating price-benchmark data over time. Copyable early; the data moat only compounds later.
Total	100	74/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · content-heavy

Key assumptions to validate (3–5)

1. Assumption: Independents will reliably forward invoices every week (the loop depends on input frequency). How to test: 20-restaurant pilot; measure % forwarding ≥1 invoice/week over 4 weeks. Kill if <50%.
2. Assumption: $39/mo lands for a solo owner who today pays $0 (uses a spreadsheet). How to test: pricing-page smoke test + 30 owner interviews; look for ≥20% “would pay today.”
3. Assumption: Vision extraction hits usable accuracy on real, messy supplier notes across cuisines. How to test: collect 200 real invoices, measure line-item extraction accuracy; target ≥95% with light correction UI.
4. Assumption: Bookkeepers will resell. How to test: pitch 10; need ≥3 to onboard a client within 30 days.

Risk flags

1. Retention risk: Restaurants churn (high closure rate) and SMB SaaS churn is brutal; the weekly-forward habit must stick or value evaporates. Mitigate with WhatsApp-native input and the weekly digest as a re-engagement hook.
2. Platform dependency: Vision-model pricing/availability and WhatsApp Business API policy. Mitigate by keeping the extraction layer model-agnostic.
3. Incumbent encroachment: Toast/Square/Petpooja could ship a “good enough” auto-costing feature for free inside the POS. The defense is being the focused, cross-POS, better-at-the-one-thing tool — and getting to the data-benchmark moat before they bother.

14. Structured verdict

Score:                  74/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder who can ship vision-extraction + a clean mobile UX, paired with restaurant-world content/distribution
Time to revenue:        4–8 weeks from launch
Capital to launch:      $5–10K (₹4–8L) — mostly inference + WhatsApp API + landing
Top 3 assumptions to validate first:
  1. Weekly invoice-forward habit holds (20-restaurant pilot, ≥50% forwarding weekly)
  2. $39/mo willingness-to-pay vs. free spreadsheet (smoke test + 30 interviews, ≥20% "pay today")
  3. Vision extraction ≥95% line-item accuracy on real messy invoices (200-invoice test)
Kill criteria:
  - Abandon if <50% of pilot restaurants forward an invoice weekly after 4 weeks
  - Abandon if extraction accuracy stays <90% after tuning (the whole value prop is "no data entry")
  - Abandon if a major POS ships free auto-costing covering 80% of the value before your v1 traction

15. Next step — 1-week validation sprint

• Day 1–2: Build a one-page landing — “Forward your supplier invoices, know which dishes lose money” — with a $39/mo button (fake-door). Collect 200 real supplier invoices from owner forums/contacts and run them through an off-the-shelf vision model; measure line-item extraction accuracy.
• Day 3–4: Interview 30 independent owners (r/restaurateur, local restaurant groups, India WhatsApp chef groups). Ask: do you know your per-dish margin today, how often do prices change, what would you pay. Pitch 5 restaurant bookkeepers on reselling.
• Day 5: Decide. Go if: extraction ≥95% accurate, ≥20% of interviewed owners say “I’d pay $39 today,” and ≥3 bookkeepers want in. No-go if extraction is unreliable on messy invoices or owners shrug at the price.

The falsifiable result: a measured extraction-accuracy number on real invoices and a measured “would pay today” rate — not “owners seemed interested.”