An agency emailed you last week. Or maybe a friend-of-a-friend who "does apps" sat across from you at a coffee shop and told you, with real conviction, that your restaurant is leaving money on the table because it doesn’t have one. The pitch is always the same three slides: loyalty program, push notifications, branded customer experience. The number at the end of the deck is usually somewhere between $15,000 and $40,000, and the monthly maintenance starts at $400.

Here’s the honest answer, which no agency is going to give you: probably not. For the vast majority of independent restaurants, a native app is a solution looking for a problem, at a price that doesn’t match the size of the problem it’s actually solving.

But "no" by itself is a useless answer, because the reasons you want an app are real. You want regulars to come back more often. You want to reach them without paying Meta for the privilege. You want your brand in the guest’s hand, not buried under the DoorDash logo. Those are all legitimate goals. The app just isn’t how you get there.

Here’s the map. On the left, the thing you think you want. On the right, the thing that actually delivers it — for a tiny fraction of the cost.

Five things operators typically want from a “restaurant app” · five cheaper, faster tools that each do exactly that one thing better

Total stack if you build all five: roughly $30–$80/month in tooling costs, plus maybe a week of setup. Total cost of the native app that was pitched at you: $15–$40K up front, $400–$1,200/month in maintenance, plus the ongoing cost of getting guests to actually install and open the thing. The app route costs 20–50x more to deliver the same underlying outcomes. That’s not a rounding error.

The install problem nobody talks about

Agencies pitching restaurant apps never want to discuss the install rate. Here’s the uncomfortable truth: the average independent restaurant that launches a native app sees under 2% of its guests install it, and of those who install, fewer than a third are still using it six months later. I’ve seen the dashboards. You get a flurry of downloads in the first two weeks from regulars who want to be supportive, then the curve flattens.

Reach of each channel as a share of your guest base

Mobile website (any visit)

100%

SMS opt-in (at host stand)

~20%

Native app — installed

<2%

Native app — still active at 6 mo

<0.6%

An independent-restaurant app reaches under 2% of guests at the install stage and under 0.6% at the six-month mark. Per industry benchmarks from Toast, Bluedot, and Restaurant Dive.

This isn’t because your restaurant isn’t beloved. It’s because your guests already have too many apps on their phone, and yours is the 187th notification competing for their attention. They love you. They also love the dry cleaner across the street and the gym around the corner, and none of those places have convinced them to install an app either. The friction-to-benefit ratio just isn’t there.

A website, by contrast, works on install rate 100%. Every single person who types your URL or taps your Google Business Profile is inside your "app" with zero friction. An SMS opt-in works on behavior — the guest texts a short code at the table and is signed up, no download required. A PWA (progressive web app) saved to the home screen looks exactly like a native app, launches with a tap, and installs in three seconds from a button on your website. Either path keeps the relationship in an owned channel — you don’t pay a platform every time a guest finds their way back.

The modern version of "I want my restaurant in the guest’s pocket" isn’t a native app. It’s a website good enough that the guest wants to save it to their home screen. That is an accomplishment your existing website stack can deliver — it just requires someone who cares about the details.

The two situations where an app is actually the right call

I’m not going to tell you no app, ever. Two specific situations make a native app defensible.

1. Multi-location brands with 5,000+ weekly app-relevant transactions

Starbucks has an app. Chipotle has an app. Sweetgreen has an app. That’s because when you have 20+ locations and guests ordering multiple times a week, the math on app-driven loyalty + pre-ordering actually pencils out — you amortize the build cost over a volume of orders that no independent restaurant sees. At Starbucks scale, a 1% conversion lift on mobile ordering pays for the entire app program in a quarter. At your scale, it doesn’t.

If you’re a two-location independent, the math still doesn’t work. If you’re five or more locations doing real mobile-ordering volume, it might. Below that, no.

2. A concept that genuinely requires app-level behavior

Ghost kitchens running multiple concepts out of one space. Pre-order-only meal prep services where every order is scheduled 48 hours in advance. Subscription dining clubs. These are actually app-shaped products — the app is the product, not a marketing layer on top of a restaurant.

If your concept is "sit-down independent restaurant where people walk in, eat, and leave," that isn’t app-shaped. The app is marketing overhead. If your concept is "subscription tasting club that ships a box every Tuesday," the app might be the entire distribution mechanism. Different animals.

  1. 1

    5,000+ app-relevant transactions per week?

    Pre-orders, mobile orders, and reservations combined. Below that volume, the build cost can’t amortize. No → stop here. Yes → next question.

  2. 2

    Is the app the product itself?

    Subscription dining club, meal-prep, ghost-kitchen aggregator. Yes → build — the app IS the business. No → next question.

  3. 3

    5+ locations with mature loyalty velocity?

    Two locations isn’t enough; the order-frequency math still doesn’t work. No → don’t build. Yes → final gate.

  4. 4

    Honest payback model under 18 months?

    Recovered profit margin in real dollars — not downloads, not “engagement.” If your agency can’t show this on a comparable client, the answer is no.

Four gates. Almost every independent restaurant stops at the first one. The two that survive all four are the only places the app math works.

The reasons you want an app are real. The app is just a much more expensive and much less-used way to get them than the tools that already live on your guest’s phone.

Want the honest “do we need an app” answer for your specific restaurant?

Bring the agency pitch to a 20-minute call and I’ll walk through it with you line by line — what’s real value, what’s markup, and what your current website + POS stack is already capable of delivering. Free for independent operators.

Email Don

The five-year cost of each path

Sticker shock is the wrong frame. The agency quotes you a build number; the real comparison is what each path costs over the life of the relationship. Below, the alternative stack from the map above versus a mid-range native-app build, totaled across five years. Both numbers assume the app actually ships and stays live.

Total cost over 5 years (build + ongoing)

Alternative stack (POS + SMS + GBP)

~$3.6K

Stack + PWA from ordering page

~$5K

Native app (mid-range build)

~$60K

$25K build plus ~$600/mo over 60 months runs the native-app path to roughly $60K. The same underlying outcomes — loyalty, messaging, own-pocket ordering, brand — cost roughly 16× less through the alternative stack.

Two columns of the same spreadsheet. The native app delivers nothing the alternative stack doesn’t already deliver — loyalty, messaging, an app-like icon on the home screen, brand presence — for sixteen times the money. The only thing the app delivers uniquely is the agency’s ongoing retainer.

What to do instead, in order

If this post has talked you off the app ledge, here’s the honest sequence. Do these first, in this order. If at the end of step four you still feel like you need a native app, call me and I’ll connect you with an agency who does them well. (Run Tech Stack first to see what your current tools already cover.)

  1. Turn on your POS’s loyalty program. Square Loyalty, Toast Loyalty — both included. Ten-minute setup. Every regular who pays with a card is automatically earning points starting tomorrow. No install required, nothing new on your guest’s phone.
  2. Start an SMS list. Services like Klaviyo, Attentive, or SimpleTexting run $20–$50/mo for a restaurant-sized list. Promote the opt-in at the host stand (“text [short code] for the weekend specials”). You’ll see the opt-in rate hit 20%+ of walk-ins within weeks. SMS has a 95% open rate. Push notifications from apps have an 8% engagement rate. It’s not close.
  3. Make your own-ordering page into a PWA. If you use Square or Toast, the ordering page already qualifies — guests can tap “Add to home screen” and get an app-like icon on their phone. Put a prompt on your site that tells them how. Zero additional cost.
  4. Audit your Google Business Profile. Full-strength photos, accurate hours, replies to reviews. This is the place guests actually interact with your brand on their phones, far more than any app ever would.

Four steps. A weekend of work. Probably $50–$100 a month in ongoing tooling. You get loyalty, push-equivalent messaging, an app-like icon on the guest’s phone, and a professional mobile presence. That stack outperforms a $25K native app on every measurable outcome, because your guest never had to make the choice to install it.

The one honest line to say to the agency

If an agency is actively pitching you right now, the line I’d use is this: “Show me a client of yours, my size, where the app has paid for itself in recovered profit margin within eighteen months — not in ‘brand engagement’ or ‘app downloads,’ but in actual dollars that wouldn’t have existed otherwise. If you can show me that, I’m interested. If you can’t, we’re done.”

Most agencies can’t answer that question, because the honest answer for an independent restaurant is almost always that the app is a marketing vehicle for the agency, not a profit vehicle for the restaurant. The margin on their side is better than the margin on yours, which is how the pitch got to your inbox in the first place.

Your goal isn’t to own a mobile app. Your goal is to have regulars come back more often and new guests find you. The tools that deliver those things already exist, mostly on your guest’s phone by default, and they cost pennies compared to what’s on the quote sheet in your inbox right now. Use those. Save the app budget for the patio build-out.