Byteet
Book a call
Back to articles

Software Development / Buyer's Guide

Does Your Business Need an App? A Decision Guide for SMEs

Nov 20, 20269 min read

A native app, a progressive web app, or just a mobile-friendly website — the SME that picks based on the real job wins. This guide covers what each option is, when it actually earns its cost, and what you're really paying for once you count the app store, the review process, and the maintenance nobody budgets for.

Does Your Business Need an App? A Decision Guide for SMEs

Ask three small-business owners why they want an app, and you will usually hear three reasons that have nothing to do with the app itself: a customer asked for one, a competitor just launched one, or someone on the team assumes a modern business needs an app the way it needs a website. None of those is actually a reason to build one. The question that matters is narrower: is there a job your customers or staff need to do on a phone, on the move, possibly offline, that a website cannot do well enough? If the honest answer is no, the cheapest and fastest option is usually the right one, and it is not an app.

This guide walks through the three real options for reaching customers or staff on a phone — a mobile-friendly website, a progressive web app (PWA), and a native app — what each one actually is, when each one fits, what each one costs to build and keep running, and the practical realities that decide whether the investment pays off.

The three options, plainly

A mobile-friendly website is a normal website, built to work well on a phone screen. No installation, no app store, found through a search engine or a shared link like any other page. This is the right starting point for most SMEs, and often the only thing needed.

A progressive web app (PWA) is a website built to behave more like an app: it can be added to a phone's home screen, work offline for pages already visited, and send notifications on some platforms. It still runs through a browser engine rather than as a true installed app, and it updates the moment you publish a change — nobody downloads anything. It is a middle ground, not a lesser version of a native app, and for many business uses it covers everything a native app would.

A native app is built specifically for iOS or Android (often both, as two separate builds), downloaded through the Apple App Store or Google Play, and able to use a phone's hardware directly: camera, GPS, Bluetooth, background location, biometric unlock, push notifications that work reliably even when the app is closed. It is also the most expensive option to build, the slowest to update, and the one with an ongoing store-review process built into every change.

When each option actually fits

A website covers you when customers mainly look something up, fill in a form, or read content — a service business's booking page, a restaurant's menu, a B2B company's product catalogue. If nothing on your list below applies, stop here.

A PWA earns its cost when you want an app-like experience — a home-screen icon, faster repeat visits, basic offline access to content already loaded — without the cost and delay of two separate native builds. It is a strong fit for loyalty programmes, simple ordering flows, internal staff tools, and anything where "feels like an app, updates instantly" matters more than deep phone-hardware access.

A native app is worth its cost only when the job genuinely needs something a browser cannot reliably give you: continuous background GPS tracking (a delivery or field-service app), offline-first operation in places with no signal, direct access to a barcode scanner or specialised hardware, or push notifications that have to land reliably on a closed phone. If your actual requirement is "customers should be able to reach us easily from their phone," that is a website or PWA requirement wearing an app's clothing.

Discoverability cuts the other way from what most owners expect. A PWA or website is found the way everything else is found — search, social, a shared link — the moment it exists. A native app is invisible until someone searches the right term in a crowded app store and chooses to download several megabytes before they have used it once. Unless you have an existing audience ready to install, a store listing by itself brings very few of the customers a website already reaches through search.

What it costs

These are typical ranges for a Dutch SME project in 2026, not a specific vendor's price list — scope moves these bands a great deal in both directions, the same way it does for any custom build.

OptionWhat it typically coversTypical build cost
Mobile-friendly websiteResponsive design on an existing or new site, no app-specific featuresOften already covered by a normal website project
Progressive web appInstallable icon, offline caching of key pages, basic push supportEUR 8,000 - 25,000
Native app, one platformiOS or Android, moderate feature set, backend connectionEUR 20,000 - 60,000
Native app, both platformsiOS and Android, shared backend, moderate-to-complex feature setEUR 40,000 - 120,000+

For a general sense of what a custom software build looks like once you are past this decision — the project phases, what to prepare, and the contract terms worth settling before you sign — see our guide to custom software development cost. If what you actually need is an online store rather than an app, that is its own, usually cheaper, path: see our webshop development cost guide.

App stores add a layer most businesses forget to budget for

Choosing native means choosing to work inside Apple's and Google's rules, not just your developer's. Both stores review every submission before it goes live and can reject or delay a release over a guideline issue that has nothing to do with whether your app works correctly; both charge a recurring developer-account fee just to publish at all; and both can take anywhere from under a day to over a week to approve an update, which turns "we need to ship a fix today" into a wait. None of this is a reason to avoid native apps when you genuinely need one — it is a reason to budget the review cycle and the account fee into your timeline and running costs from the start, rather than discovering them the week you planned to launch.

A PWA has none of this: you publish a change and it is live for everyone the next time they load the page, with no reviewer in between.

Maintenance does not stop at launch

Whichever option you choose, someone has to keep it running: operating-system updates that change what phones expect from an app, a backend that needs the same patching and monitoring as any other software, and small fixes as your business changes shape around the tool. A native app adds one more maintenance category the others do not have — Apple and Google periodically change platform requirements and will eventually stop accepting updates built against an old version, which means an app that nobody touches for a couple of years can simply stop being installable for new users even though nothing about your business changed. Our guide to custom software cost covers what an ongoing maintenance arrangement should include and, if the app will handle customer or staff personal data, what belongs in the contract before you sign.

A simple decision checklist

  • Can you name the specific phone hardware (GPS, camera, offline storage, push-to-closed-phone reliability) the job needs, or are you really just describing "reachable from a phone"?
  • Would your actual customers find you through an app store search, or only after you have told them to download it?
  • Can you commit to a maintenance budget for years, not just a launch budget?
  • Would a home-screen icon and offline access to already-visited pages — what a PWA gives you — cover the job just as well?

If you land on "a website already does this" or "a PWA would do this," that is the right answer, not a compromise.

Common mistakes

  • Building native because "an app feels more serious." A well-built website or PWA looks and feels just as professional, loads faster, and reaches more customers through search than an app sitting undiscovered in a store.
  • Skipping the store-review timeline. Planning a native launch the way you would plan a website launch, without budgeting days for app-store review on the first submission and every update after it.
  • No plan for OS updates. Treating a native app as a one-time build rather than software that needs the same ongoing attention as anything else you run.
  • Choosing native for reach, not for features. The store does not hand you customers; search and your own marketing still do most of that work, exactly as they do for a website.

FAQ

What does it cost to build an app for a small business? A progressive web app typically runs EUR 8,000 - 25,000. A native app for one platform (iOS or Android) typically runs EUR 20,000 - 60,000, and both platforms together EUR 40,000 - 120,000 or more, depending on feature complexity and backend work. A mobile-friendly website is usually part of a normal website project rather than a separate cost.

Is a PWA as good as a native app? For most SME use cases, yes — a PWA covers an installable icon, offline access to pages already visited, and (on supported platforms) notifications, without a separate iOS and Android build or app-store review on every update. A native app only pulls ahead when you need deep phone hardware access (continuous background GPS, a barcode scanner, guaranteed push delivery to a closed app) that a browser cannot reliably provide.

Do I need an app if I already have a website? Usually not. Most of what businesses want from "an app" — being easy to find and use on a phone — is already covered by a well-built, mobile-friendly website. An app is worth the extra cost only when there is a specific job a website genuinely cannot do.

Can I turn my existing website into an app? You can turn it into a progressive web app in many cases, since a PWA is built on top of your existing website rather than replacing it. Turning a website into a true native app is really a separate build that reuses your backend, not a conversion — budget and plan for it as its own project.

Talk to us before you decide

If you are not sure whether your business genuinely needs a native app, a PWA would do the job, or a better website solves it outright, our Web & Software Development team will scope the real requirement with you before recommending the most expensive option. If the app will handle customer or staff personal data, our Cybersecurity & Identity team can review what belongs in the contract and the access setup before you sign anything.

  • Software Development
  • Mobile Apps
  • Web Development
  • SME

Related Articles