Do you need a mobile app? Most local businesses are better off without one.

Somebody — a competitor, a salesperson, maybe your nephew — told you that you need an app. And it sounds right. Apps feel like what real companies have. You're picturing your logo on a customer's home screen, and you're wondering what it costs.

Here's the uncomfortable part, coming from a studio that builds apps for a living: most local businesses should not build one. We'd happily bill for it. It's usually the wrong buy. Let's walk through why, and the specific cases where the answer flips.

The install problem nobody mentions in the sales pitch

An app only works if people install it, keep it, and open it. Every step of that chain is brutal for a business your customers use a few times a year.

Think about your own phone. When did you last install an app for a plumber, a roofer, a family law office, or a landscaping company? You didn't — and neither will your customers. Data from analytics firms like data.ai (formerly App Annie) has shown for years that people spend the overwhelming majority of their app time in a small handful of apps — messaging, social, video. Everything else fights for scraps, and uninstall rates for newly downloaded apps are high within the first weeks.

The math for a typical local business looks like this, illustratively: a Keller plumber gets a customer maybe two or three times over five years. To reach that customer through an app, you need them to (1) find it in the App Store, (2) download it, (3) create an account, (4) not delete it during the next "storage full" purge, and (5) remember it exists eighteen months later when the water heater dies. Or they could just Google "plumber near me" and tap your phone number in four seconds.

The website wins that race every single time.

What an app actually costs (it's not just the build)

The build quote is the visible number. A properly built custom mobile app for a small business typically runs from the low tens of thousands up — and that's before the part nobody budgets for:

• App Store overhead. Apple charges $99/year for a developer account, Google charges a one-time $25 — trivial. The real cost is review cycles, rejection risk, and required updates when iOS and Android change under you (which they do, every year).
• Two platforms, forever. Even with cross-platform frameworks, you're testing and maintaining for both ecosystems.
• Ongoing maintenance. A reasonable rule of thumb across the industry is 15–20% of the original build cost per year just to keep an app current, secure, and compatible. An app you stop maintaining doesn't sit still — it breaks.
• Marketing the app itself. A website gets found through search. An app gets found through... you promoting the app. That's a second marketing job stacked on your first one.

Compare that to a fast mobile-first website with tap-to-call, online booking, and a quote form. It's discoverable through Google, shareable by link, requires zero installs, works on every device on day one, and costs a fraction to build and a smaller fraction to maintain.

The 95% solution: a mobile site that actually does the job

When business owners say "I want an app," what they usually mean is a list of capabilities. Almost all of them are website features now:

• Tap-to-call and tap-to-text — plain HTML, works everywhere.
• Online booking and scheduling — embeddable tools or custom booking flows on your site.
• Payments and invoices — Stripe, Square, and similar handle this on the web just fine.
• "Add to home screen" — a progressive web app (PWA) can put your icon on the customer's phone without the App Store at all, and can even work offline.
• Photo uploads for quotes — a web form does this.
• Loyalty punch cards — phone-number-based loyalty tools work at the register with no install.

Even push notifications — the classic "only apps can do this" feature — are now available to web apps on both Android and iOS (Apple added web push support in iOS 16.4, back in 2023). The capability gap that justified apps a decade ago has mostly closed.

When an app genuinely earns its keep

There are real cases where the answer is yes. They share one trait: frequency. If your customers interact with you weekly or daily, the install cost gets repaid.

1. High-frequency loyalty businesses. A coffee shop customer who comes in four mornings a week will install your app for order-ahead and rewards — that's the Starbucks playbook, and it works at local scale too. Same for gyms with class booking, or a salon with a heavy repeat clientele.
2. Field crews and internal operations. An app your employees use — job tickets, photos, time tracking, route info — has a guaranteed install base of exactly the people who need it. Internal tools are one of the strongest app cases there is.
3. Push-notification-driven operations. If your business model depends on real-time alerts customers must act on — "your table is ready," "your order shipped," "class starts in 30 minutes" — and web push isn't reliable enough for your audience, a native app can be the right call.
4. Something a browser truly can't do. Heavy offline use in no-signal areas, deep hardware integration, background GPS. Rare for local businesses, but real when it applies.

If you don't recognize your business in that list, put the app money into a faster site, better local SEO, and a follow-up email system. Those compound. An unused app just depreciates.

How West Fork approaches this

When someone asks us for an app, the first thing we do is try to talk ourselves out of the bigger invoice. We map how often customers actually interact with the business; if it's less than monthly, we'll recommend a fast mobile site with booking and tap-to-call, usually with a PWA layer, and show the cost difference in writing. If the frequency case is real — a gym, a field crew — we'll build the app and say why it's worth it.