Website or mobile app: which does your business actually need?

"Should we build an app?" is one of the most expensive questions a business can answer badly. Build too early and you've spent five figures on something your customers download once and forget. Skip it when you needed it and your competitor owns the home screen your customers tap daily. Here's the framework we use with clients — including the times we talk them out of the app.

Start with the frequency question

The single best predictor is how often a customer interacts with you. A restaurant that regulars order from twice a week, a gym with daily check-ins, a service company whose clients track jobs — those are app-shaped businesses. A wedding photographer, a roofer, an accountant hired once a year — those are website-shaped businesses, and an app would sit unopened between visits.

Be honest about frequency, not aspiration. "Customers could use it weekly" is a hope; "customers already contact us weekly" is data.

What only an app can do

Four things genuinely require an app: push notifications (the only channel that reaches a phone screen without paying per message), home-screen presence (a permanent icon versus remembering a URL), deep device access (NFC payments, background location, camera integrations), and reliable offline work (field technicians in basements and rural areas). If none of these four matter to your business, an app is a more expensive way to do what your website already does.

What a good website does better than a bad app

It's found by search engines and AI assistants — apps are invisible to both. It works instantly with no install step, and the install step is where most potential users quit. It updates the moment you publish, with no store review queue. And it costs a fraction to maintain. A fast, well-built mobile website beats a mediocre app on every metric that matters to a small business.

The middle path most people miss

The choice isn't binary. Three intermediate options solve most cases: a progressive web app (installable from the browser, home-screen icon, basic offline — without store approval); an internal-only app for your team while customers use the website (very common in field services: technicians get the app, clients get bookings and tracking on the web); or an app built on an existing platform, sharing your website's backend, so you pay only for the mobile interface rather than rebuilding accounts, payments and data from zero. That last one is how we work — and it's why an app can start at €5,000 rather than €40,000.

The decision, in one paragraph

If your customers interact occasionally, start with an excellent website — mobile-first, fast, bookable. If they interact frequently and you need notifications or offline capability, build the app on top of that same system, not beside it. Never build an app to look modern; build it when a specific job can't be done any other way. And whatever you choose, insist that both interfaces share one backend — two disconnected systems mean double data entry, and double data entry is the problem you were trying to solve.

We build both, on one platform, and we'll tell you plainly when you don't need the app. That's what the thirty-minute discovery call is for — you leave with an answer, and a fixed-scope proposal within 48 hours if it makes sense.