A branded app sounds like the obvious next step. The pitch writes itself: "your customers, your brand, your data." But every operator has heard that pitch from ChowNow at $400 setup, BentoBox at $250/month, and Toast at "let me get you on a call with sales." The real question isn't whether you should have a branded app. It's whether the unit economics work for your business at your scale.
This is the math.
The promise vs. the payback
The pitch from any branded app vendor says three things:
- Repeat customers reorder more often — push notifications, loyalty, faster checkout
- You capture customer data — phone, email, order history, preferences
- You stop paying commission to DoorDash and Uber Eats on those repeat orders
All three are true. But they're true at different rates depending on your business. A pizzería with a strong delivery base and 40% repeat customers gets a different return than a fine dining restaurant with mostly first-time visitors.
The math has three inputs:
- Your monthly active customer count (MACs) — people who ordered at least once in the last 30 days
- Your average ticket — total revenue ÷ total orders, on direct + 3rd-party channels
- Your existing repeat rate — % of customers who order again within 60 days
If you don't know these numbers, log into your POS and pull the report. Don't keep reading until you have them. The whole exercise is meaningless without them.
The base case: a 3-location pizzería
Let's run the math on a real-feeling business. Three pizzerías. 800 monthly active customers across all three. $32 average ticket. 35% existing repeat rate (DoorDash data).
Monthly direct revenue today (no app): Most of these customers reorder via DoorDash because that's where they originally ordered. Let's say 50% of orders are direct (your phone + your existing website) and 50% are 3rd-party.
- Direct orders/month: 800 customers × 1.5 orders × 50% direct = 600 direct orders
- Direct revenue: 600 × $32 = $19,200/month
- 3rd-party orders: also 600. Revenue net of 30% commission: 600 × $32 × 0.70 = $13,440/month
- Total monthly revenue: $32,640
With a branded app, after 6 months of adoption:
App-based businesses see two specific lifts. First, customers who download the app reorder 2.5–3× more often than non-app customers (industry data, validated across BentoBox, ChowNow, and Toast case studies). Second, push notifications drive a one-time spike of 5–10% of dormant customers back into the funnel each month they're sent.
Let's assume a conservative 30% app adoption among existing MACs (240 of 800 customers download). Those 240 customers now order 2.5× more often:
- App users: 240 customers × 3.75 orders × $32 = $28,800/month (all direct, 0% commission)
- Non-app direct: 560 customers × 1.5 × 50% × $32 = $13,440/month
- Non-app 3rd-party: 560 customers × 1.5 × 50% × $32 × 0.70 = $9,408/month
- Total monthly revenue: $51,648
Net delta: $51,648 - $32,640 = +$19,008/month ($228k/year)
App cost (Eatsy Branded App tier): 3 locations × $149.99 = $449.97/month
Payback period: Less than a single week of incremental revenue.
Pricing is linear
Eatsy charges $149.99/month per location for the Branded App tier. There is no bundle discount and no enterprise tier — 10 locations is exactly 10× the price of 1. That keeps your forecasting clean and your migration risk low.
Where this math falls apart
The base case looks great. It also has assumptions that fall apart in three predictable ways.
1. Adoption rate is everything
If only 5% of your MACs download the app instead of 30%, the lift drops to ~$3,500/month. Still positive, but a much slower ramp. Adoption depends on how aggressively you promote the app — QR codes on receipts, table tents, in-store signage, "first order in the app gets 10% off" campaigns, push from your existing customer database via SMS or email.
The single best driver of adoption is a real reason to download. "Get our app" doesn't work. "Order ahead and skip the line" works. "Get loyalty points faster" works. "Exclusive app-only specials on Sundays" works.
2. Repeat-rate lift is not free
That 2.5× reorder rate from app users isn't because they're suddenly hungrier. It's because the app removes friction (saved cards, one-tap reorder, push reminders) and adds incentive (loyalty points, app-only specials). If you don't actually run those programs — if your app is just a digital menu with a checkout — the lift collapses to maybe 1.3×.
In practice: budget for 1 hour/week of marketing time to send pushes, design specials, and review loyalty performance. Without that hour, your app becomes a parked asset.
3. 3rd-party customers don't migrate automatically
This is where most operators get burned. They assume DoorDash customers will magically download their app once it exists. They won't. DoorDash customers are loyal to DoorDash, not to you.
The migration tactic that works: a printed insert in every 3rd-party delivery bag. "We noticed you ordered through DoorDash. Next time, save 15% by ordering directly through our app — same drivers, faster delivery, no DoorDash markup." Direct insert programs typically convert 8–12% of DoorDash customers to direct app users within 90 days. That's the slow grind.
The break-even framework
The number you should be solving for is your monthly incremental revenue from the app, vs. the app's monthly cost.
Plug your own numbers in:
- Monthly Active Customers (MACs): ____
- Average ticket ($): ____
- Existing direct orders/month: ____
- Existing 3rd-party orders/month: ____
Then estimate (be conservative):
- Likely app adoption rate in 6 months: ____% of MACs
- Repeat-rate multiplier for app users (assume 1.5× if you won't run loyalty/push, 2.5× if you will): ____
Monthly incremental revenue ≈ (MACs × adoption% × multiplier × avg ticket) - (those same orders going through 3rd-party today × avg ticket × 0.70)
The break-even on Eatsy's Branded App tier ($149.99/location) is roughly 5 incremental orders per month per location. If you can't believe you'll generate 5 extra orders per month per location from having an app, don't get the app. If you believe you'll generate 50, the app is one of the highest-ROI investments in your operation.
The hidden ROI line items
The math above only counts revenue lift. Three other things move the ROI but rarely show up in spreadsheets:
Customer data ownership. If you decide to leave Eatsy in 3 years, you take your full customer database with you (CSV export, no questions). The same customer ordering through DoorDash for those 3 years is owned by DoorDash forever.
Push notification optionality. Email open rates run 18–22% for restaurants. Push notification open rates run 30–50%. SMS runs 90% but is expensive and easy to abuse. The push channel is essentially free incremental marketing capacity that you can't get any other way.
Brand defense. When a customer searches "[your restaurant name] app" on the App Store, your app shows up. If you don't have one, a competitor's app shows up — or worse, DoorDash's. App Store presence is brand defense, not just brand offense.
When a branded app is wrong for you
Not every operator should have a branded app. Three signals it's premature:
-
You don't have 200+ monthly active customers yet. With less than 200 MACs, the adoption math doesn't generate enough orders to matter. Spend that money on customer acquisition first (Google Ads, local SEO, in-store experience). Come back to the app conversation at 200+ MACs.
-
Your average ticket is under $14. Branded app economics work because each repeat order has meaningful margin. At $14 average ticket, the loyalty + push lift exists but the absolute dollars are smaller. The Microsite plan ($89.99) plus aggressive Google ranking is usually a better starting point.
-
You don't have time to actually run the app. As mentioned, adoption requires active marketing. If you can't commit 1 hour/week, you're paying $149.99/location for an asset that just sits there.
What this looks like at Eatsy specifically
Eatsy's Branded App tier is $149.99/month per location. That includes:
- Native iOS + Android app published under your restaurant's name
- Push notifications (segmented, scheduled, bilingual)
- Loyalty + coupons fully integrated
- Microsite + EatsyAI + Catering bundled (Order Management — the kitchen-tablet product — is a separate add-on for operators who route tickets to a back-of-house display)
- Live in 5–7 days (not the 6 weeks ChowNow takes)
For a 3-location pizzería on the base case math above, the app pays for itself ~70× over in the first year.
Payments under the hood
The card processing on the Eatsy app runs through Shift4 or NMI depending on your existing merchant relationship. You keep your processor; we handle the integration. No new payment contract required to launch.
What to do this week
If you're over the 200 MAC / $14 ticket threshold, here's the 30-day plan:
- Pull your data — MACs, average ticket, repeat rate, direct vs. 3rd-party order mix. Don't skip this.
- Plug into the framework above. Build a conservative model and an optimistic model. Pick the conservative number to base your decision on.
- Identify your push/loyalty hour. Who on your team has 1 hour/week to manage app marketing? If nobody, this isn't yet the right move.
- Book a demo. Walk through your specific numbers. Operators with solid baseline data get better implementations because the launch plan is calibrated to your business.
Frequently Asked Questions
How fast does a branded app actually launch?
5–7 days for most pizzerías and quick service operators on Eatsy. Day 1: brand kit collection. Day 2–3: app build + menu import via Shift4. Day 4–5: you review and approve. Day 5–7: Apple/Google approval (typically 1–3 days for Google, 3–5 days for Apple). Some operators take longer because they want custom photography or unique design — that's fine, just adds time.
Do I need an Apple Developer account?
No. Eatsy submits your app under our enterprise developer account. You don't pay Apple's $99/year fee or maintain anything. If you ever want to migrate to your own developer account, we transfer ownership.
What if my app gets rejected by Apple?
In 4 years of submissions, Eatsy has a sub-3% rejection rate, and we handle the back-and-forth with Apple at no extra cost. Most rejections are minor metadata issues that take 24 hours to resolve. The rare structural rejection (e.g., "the app doesn't have enough unique value over the web experience") is something we'd flag in your demo before you started.
Can my customers order in Spanish in the app?
Yes. The app is fully bilingual EN+ES at the customer level. They pick their language on first open and the app remembers it. Menu, modifiers, allergens, push notifications, receipts — all match the customer's language. See the Bilingual Menu Best Practices article for how to scale this beyond 50 menu items.
What metrics should I track post-launch?
Five core metrics, weekly:
- App downloads (target: +5% week over week for first 90 days)
- App MAC (monthly active customers ordering through the app)
- App repeat rate (% of app customers who order again within 30 days)
- App revenue % (app revenue ÷ total revenue — target: 15%+ within 90 days)
- DoorDash revenue trend (should be flat or declining as app revenue grows)
If app MAC and app revenue % are both growing while DoorDash revenue is shrinking, you're winning. If DoorDash revenue keeps growing alongside app revenue, you're acquiring net-new customers — also fine, but a different story.