PayoutSnap — recovery clerk for independent restaurants

1. One-liner

PayoutSnap reads every delivery-app payout, flags the silent deductions, and auto-files the disputes before the 14-day window closes — for the one-location restaurant that has no bookkeeper.

2. Trend signal — why now?

Three things broke open in the last 12 months and they all point at the same money sitting on the table.

First, the bleed is now documented, not anecdotal. Industry reporting puts 2.5–3% of an operator’s total revenue tied up in disputes with their delivery providers, and operators recover their money “only about 60% of the time” — and that’s the ones who file at all. Most don’t: “the process is complicated and time-consuming, [so] most restaurants end up not filing.” One owner in Georgia is charged hundreds of dollars a month for undelivered orders where the driver pretended to pick up and walked off with the food — “two or three times a night.” An Omaha owner ate ~$188K in delivery fees in a single year before quitting the apps entirely.

Second, the regulator just put wind at the restaurant’s back. On April 16, 2026 the FTC published an ANPRM on unfair and deceptive fees in online food and grocery delivery — 60+ questions, comment window through May 18, 2026 — on the heels of a $60M Instacart and $25M Grubhub settlement and LA County suing Grubhub for “deceptively and unilaterally” charging restaurants for refunds without verifying fault. The platforms are about to get more careful about how they bill restaurants, which makes mis-bills more disputable, not less.

Third, it’s finally cheap to do the reading. Parsing weekly payout statements (PDF/CSV) across DoorDash/Uber Eats/Grubhub, matching line items against the POS order export, and drafting a portal-ready dispute is now a sub-cent LLM/vision task. Incumbents (Voosh, Restaurant365, DeliverGuard) have already proven the data is machine-tractable — they just aim it at chains.

Provenance:

• Signal 1 (demand): Operators report hundreds/month in fake-undelivered charges, 2.5–3% of revenue in disputes, ~60% recovery, “most restaurants end up not filing” — https://www.restaurantbusinessonline.com/technology/restaurants-say-theyre-bearing-brunt-delivery-chargebacks — 2026-06-12
• Signal 2 (economic/regulatory): FTC ANPRM on deceptive food-delivery fees, comment window to May 18 2026, on heels of $60M Instacart / $25M Grubhub settlements + LA County v. Grubhub — https://www.ftc.gov/news-events/news/press-releases/2026/04/ftc-seeks-public-comment-unfair-deceptive-fee-practices-online-food-grocery-delivery-services — 2026-06-12
• Signal 3 (feasibility): Reconciliation/dispute data is machine-tractable; incumbents centralize payouts vs POS and auto-file disputes (>80% win, recovering 2–8% of delivery revenue) but price for 20–30 location chains at $1.75/location — https://www.voosh.ai/finance-reconciliation — 2026-06-12 Category: Workflow automation

3. The opportunity

The money leaks through three pipes and nobody at a one-location restaurant watches any of them:

1. Error charges / refunds — the customer says “missing item,” the platform debits the restaurant, often without verifying fault. ~1/3 of these refunds are estimated fraudulent. The restaurant finds out only when the weekly payout lands short.
2. Commission and fee mis-calculation — commissions not reversed on refunded orders, duplicate deductions, promo spend billed wrong, payout-timing gaps. “Several operators told researchers they have no way to track this without exporting to a spreadsheet.”
3. Unfiled disputes — DoorDash gives ~14 days to dispute; the portal takes “multiple clicks just to view or dispute a claim.” A busy owner working the line never gets to it. The window closes. The money is gone.

The incumbents solve pipes 1–3 — but for the wrong customer. Voosh’s “sweet spot is mid-market brands with 20 to 30 locations,” sold to an ops/finance team, priced as a near-free loss-leader ($1.75/location/mo) to upsell a full ops suite. Restaurant365 wants you on its accounting platform. None of them onboard the single-location independent who has no accountant, doesn’t export to a spreadsheet, and doesn’t even know the statement is short. That operator is too small to be worth a chain-software sales motion — and that’s exactly the gap. A focused tool that a solo owner connects in an afternoon and that quietly claws back 2–3% of revenue is a no-brainer purchase for them and an un-fun, low-ACV segment for the incumbents to chase.

4. Target market

• Primary customer: Owner-operator of a single-location US restaurant doing meaningful delivery volume — pizza, wings, burgers, regional fast-casual, ghost-kitchen solos — typically $40K–$200K/mo total revenue, $10K–$60K/mo of it through DoorDash/Uber Eats/Grubhub. No in-house bookkeeper; the owner or a manager does the books at night.
• Why they buy: “I know they’re shorting me but I don’t have time to fight every charge, and I can’t even tell what I’m owed.” The pain is felt every single payout cycle (weekly), it’s measured in real dollars off thin restaurant margins, and the current workaround is either eating it or maintaining a manual spreadsheet most owners abandon.
• Rough TAM reasoning: ~750K+ restaurant locations in the US; a large share are independents, and the overwhelming majority of those run at least one delivery marketplace. Even a narrow beachhead — independents with >$10K/mo of delivery and no accounting software — is comfortably 100K+ accounts. At a few hundred dollars/year each, that’s a >$30M ARR ceiling well before touching small chains. More than enough for a sub-$5M target.
• Why now for them: delivery is now a structural revenue stream they can’t quit, the deduction noise has gotten loud enough to make the news, and the FTC spotlight makes them suddenly aware they may be getting fleeced.

5. Product sketch (MVP)

• Connect once: owner links their DoorDash, Uber Eats, and Grubhub merchant accounts (and forwards/uploads weekly payout statements where a clean API isn’t available).
• Connect the POS once: pull the order export from Toast/Square/Clover so PayoutSnap knows what was actually sold and at what price.
• The weekly catch: every payout cycle, PayoutSnap matches each platform line item to the POS order, flags error charges, un-reversed commissions, duplicate deductions, and short-pays — with a plain-English “here’s what they took and whether it looks legit.”
• One-tap dispute: for every disputable charge inside the window, it pre-fills the portal-ready dispute (or files it where the API allows) and tracks status to resolution.
• The Friday text: a weekly WhatsApp/SMS summary — “This week DoorDash took $312 in error charges; we flagged $214 as disputable and filed 9 disputes; $90 recovered from last week.” Zero-login glanceability for an owner on the line.
• Recovery ledger: a running tally of dollars clawed back, so the ROI is undeniable at renewal.
• Deadline guard: alerts when a high-value charge is about to age out of the dispute window.

6. AI angle — what’s load-bearing

Remove the AI and the product is a spreadsheet nobody fills in. The load-bearing work is: (a) statement parsing — extracting structured line items from inconsistent, frequently-changing PDF/CSV payout formats across three platforms via vision/LLM, where a brittle hard-coded parser breaks every time a platform tweaks its layout; (b) fault classification — judging from order detail, refund reason codes, and timing whether a given error charge is plausibly the restaurant’s fault or the platform’s/driver’s, which is the exact human judgment that makes filing slow; and (c) dispute drafting — composing the specific, evidence-cited argument each portal wants. The AI collapses a 2–3 hour weekly reconciliation-and-filing chore into a 2-minute review. That is the product.

7. Localization angle (if any)

N/A — this is a US-first play. The wedge is the US delivery-marketplace oligopoly (DoorDash/Uber Eats/Grubhub) and the US regulatory tailwind (FTC ANPRM, state AG suits). The same shape could later port to the UK (Deliveroo/Just Eat/Uber Eats) or India (Swiggy/Zomato), but the dispute mechanics and fee structures differ enough that each is a separate build, not a translation. Start where the deductions are loudest and the regulator is already swinging.

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

• Pricing: $99/mo base for a single location, OR 15–20% of dollars recovered (performance pricing) — owner picks. Most will start on performance pricing because it’s risk-free, then graduate to flat once they trust the recovery number. Blended effective ACV ~$1,500–$2,400/yr.
• Why it clears: if PayoutSnap claws back even 1.5% of $25K/mo delivery = $375/mo recovered, a $99 flat or ~$60 performance cut is a 4–6× ROI — the same ROI multiple incumbents cite, but kept by an operator the incumbents won’t serve.
• Rough math to $1M ARR: ~550 locations × ~$150/mo blended = ~$1M. That’s a single solid niche (e.g. independent pizza/wings shops in a handful of metros).
• Rough math to $5M ARR: ~2,800 locations, OR ~1,200 locations once you add small chains (3–10 units) at higher ACV and an accountant-referral channel. Both are inside the independent-restaurant TAM with no platform expansion required.
• Expansion path: add platforms (ezCater, Slice, Toast Delivery), add adjacent leaks (chargeback fraud scoring, promo-spend audit, commission-tier audit), then sell a “books-ready” export to whoever does the restaurant’s taxes. ACV grows by leak count, not seat count.

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

• Recovery-audit cold open: scrape independent restaurants with heavy delivery presence from DoorDash/Uber Eats marketplace listings + Google Maps in 2–3 target metros (pizza/wings first). Offer a free one-time payout audit: “send me last month’s three statements, I’ll tell you exactly how many dollars you were shorted.” A concrete found-money number converts far better than a feature pitch. Expect single-digit % reply, high close on the ones who send statements because the number sells itself.
• The undeniable-ROI flip: every free audit that surfaces real leaked dollars is a warm close on performance pricing — “I’ll get that money back and only take a cut of what I recover.” Zero perceived risk.
• Bookkeeper / restaurant-CPA referral: the people who do independents’ books hate reconciling delivery payouts and don’t want to. Partner with 10–20 small restaurant bookkeeping shops; they refer clients and get a margin. They’re a force multiplier into exactly the no-in-house-finance segment.
• Owner communities: r/restaurateurs, r/KitchenConfidential operator threads, local restaurant-association FB groups, and pizza-operator forums where the delivery-fee rage already lives. Show up with the audit offer, not a banner ad.
• FTC moment piggyback: the ANPRM news cycle is live recruiting. Content/posts answering “are you being overcharged by DoorDash?” with a free-audit CTA ride a wave of fresh awareness.

10. Build complexity — justification

Medium. Off-the-shelf: LLM/vision parsing, standard web stack, POS APIs (Toast/Square/Clover are documented), SMS/WhatsApp. The real work is the integration surface and parser resilience — three delivery platforms with inconsistent, changing statement formats and uneven/no public merchant APIs (some flows need authenticated portal access or statement upload), plus the fault-classification logic that has to be accurate enough to not file junk disputes. Estimate 3–4 months to a credible v1 covering DoorDash + one other platform and one POS, for a 1–2 person team. The platform-API/anti-automation risk is the thing that pushes this from Low to Medium.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Filing legitimate disputes on the merchant’s own behalf, with their credentials/consent. No scraping of third parties’ private data.
Ethical — no harm / dark patterns	✅	Recovers money the restaurant is genuinely owed; fault-classification is tuned to avoid filing bad-faith disputes.
Market exists (evidence above)	✅	Documented dollar bleed, funded incumbents, regulatory action.
1–5 person team can build this	✅	1–2 builders, 3–4 months to v1.
Launchable with <$50K / ₹40L	✅	Inference + infra cheap; main cost is builder time.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Felt every weekly payout, measured in real dollars off thin margins, current workaround abandoned. Just short of “hair-on-fire” because owners have learned to absorb it.
Demand evidence	15	13/20→13/15	Multiple independent signals: documented dollar figures, funded competitors, FTC action, owner complaints. Strong, but most direct quotes are about the pain, not about paying a 3rd party to fix it.
Build feasibility	15	11/15	Mostly off-the-shelf, but platform-API fragility and parser resilience across 3 changing formats is genuine work.
Distribution clarity	15	12/15	Free-audit cold open with a found-money number is a strong, named wedge; bookkeeper referral adds a channel. Conversion math still needs proving.
Revenue mechanics	15	11/15	Performance + flat pricing both credible, ROI is provable per-customer. Risk: per-location dollars recovered may be lower than headline 2–3% for smaller shops.
Time to first revenue	10	8/10	Free audit → performance close can produce paying customers within weeks of a working parser; no long sales cycle.
Defensibility	10	5/10	Execution + accumulating parser/format library + recovery-data moat; but incumbents could drop down-market and platforms could improve APIs. Soft moat only.
Total	100	76/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · domain-expertise-required

Key assumptions to validate (3–5)

1. Assumption: A typical single-location independent leaks enough ($200+/mo recoverable) to justify a $99/mo or 15–20% cut. How to test: Run 20 free audits on real last-month statements; measure median recoverable dollars per location.
2. Assumption: You can connect/ingest DoorDash + Uber Eats + Grubhub payout data reliably without the platforms blocking you. How to test: Build the ingestion for one platform via the available API/upload path; confirm it survives a statement-format change.
3. Assumption: Owners will hand over statements (and eventually credentials) to a new vendor. How to test: Free-audit offer — measure what % of contacted owners actually send statements.
4. Assumption: Fault-classification is accurate enough that filed disputes win at a rate worth the cut. How to test: Manually file the first ~100 AI-flagged disputes; track win rate vs. incumbents’ cited >80%.

Risk flags

1. Platform dependency / anti-automation: DoorDash/Uber Eats/Grubhub can throttle, change formats, or forbid third-party portal access. Mitigate by leaning on official merchant APIs and statement upload where automation is restricted.
2. Incumbent down-market move: Voosh/R365 could ship a self-serve single-location tier. Their disincentive is low ACV and a chain-oriented sales motion — but it’s not a hard moat. Speed and a restaurant-CPA referral network are the defense.
3. Recovery variance: smaller shops may have lower absolute recoverable dollars than the 2.5–3%-of-revenue headline implies, squeezing performance-pricing economics. Validate per-segment before scaling spend.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder comfortable with messy integrations + a restaurant-ops advisor
Time to revenue:        6–10 weeks (free audit → performance close, once one parser works)
Capital to launch:      $8–15K ($4–6K infra/inference + design; rest founder time)
Top 3 assumptions to validate first:
  1. Median recoverable $/location/month ≥ $200 — run 20 free statement audits
  2. Reliable, durable ingestion of at least one platform's payout data — build it, survive a format change
  3. Owners will send statements to a new vendor — measure audit-request conversion on cold outreach
Kill criteria:
  - Abandon if median recoverable dollars across 20 audits < $150/location/month (ROI too thin for the cut)
  - Abandon if all three platforms block third-party ingestion with no upload/API fallback within 60 days
  - Abandon if AI fault-classification can't beat ~60% dispute win rate on the first 100 real filings

15. Next step — 1-week validation sprint

• Day 1–2: Build a throwaway parser for ONE platform’s payout statement (DoorDash) + ingest a Toast/Square order export. Manually reconcile one real restaurant’s last 4 weeks. Confirm you can compute “dollars shorted.”
• Day 3–4: Cold-DM/email 50 independent delivery-heavy restaurants in two metros offering a free one-time payout audit. Measure how many send statements.
• Day 5: For every statement received, compute median recoverable dollars/location/month and how many charges fall inside the dispute window.

Falsifiable go/no-go: GO only if (a) ≥6 of 50 contacted owners send statements within the week AND (b) median recoverable dollars ≥ $200/location/month. Below either bar, the wedge or the economics aren’t there — fix the offer or kill it.