The Honest Answer: Most Small Businesses Don't
We build apps - so it might seem odd to open with this - but most small businesses do not need one, and being told otherwise has cost a lot of owners five-figure sums for something nobody downloaded.
An app is not a marketing channel. It is a tool for people who already know you and use you often. Nobody discovers your business through the App Store the way they discover you through Google. So before you spend a penny on an app, the real question is not "would an app be nice" - it is "do I have people who use my business often enough to want it on their home screen?" For a huge number of businesses, the honest answer is no, and a fast, well-built website does everything they need.
This guide is written to help you make that call properly, and to know what a real app project involves if the answer turns out to be yes.
App vs Mobile Website vs PWA
There are three distinct things people muddle together, and understanding the difference saves a lot of wasted money:
- A mobile website. Your normal website, built to work beautifully on a phone. No download, found through Google, works on every device, cheapest to build and maintain. For most businesses this is the right answer and the only thing they need.
- A progressive web app (PWA). A website that can be "added to home screen", works offline, and sends notifications - without going through the App Store. It gets you much of the feel of an app at a fraction of the cost and complexity. An underused middle ground.
- A native app. A true App Store / Google Play app, installed on the device, able to use the camera, GPS, secure payments, and hardware to their full extent, and to send rich push notifications. The most capable option and by far the most expensive to build and maintain.
Reach for a native app only when you genuinely need what only it provides. A lot of "we need an app" conversations end happily with a great mobile site or a PWA.
When an App Is Genuinely Worth It
A native app earns its cost when one or more of these is clearly true:
- People use it repeatedly. Daily or weekly engagement - tracking, logging, booking, checking - is what justifies a home-screen icon. One-off or occasional use does not.
- You need device features. Reliable push notifications, offline use, camera or barcode scanning, GPS, or secure in-app payments that a website cannot match.
- The app is the product. If you are building a software business rather than adding an app to an existing service, this is a different conversation entirely - and usually the right one.
- Loyalty and retention are the whole point. A cafe with a genuine daily-regular base and a points scheme can justify an app; a solicitor consulted once every few years cannot.
If none of these ring true, an app will most likely become an expensive icon nobody opens. There is no shame in concluding you do not need one - it is the outcome we recommend more often than not.
The Real Cost of Building and Keeping an App
The build price is the part people fixate on, but it is only the beginning. A native app is a living thing with ongoing costs that catch owners out:
- Two platforms. iOS and Android are effectively two builds. Cross-platform tools reduce but do not eliminate the difference.
- Store fees and rules. Apple and Google charge annual developer fees and take a cut of in-app purchases, and both enforce review policies you must keep meeting.
- Maintenance is not optional. Operating systems update every year and can break an app that is left alone. A neglected app quietly stops working. Budget for ongoing upkeep from day one.
- Getting it found. Building the app is not the end - people have to discover and download it, which is its own marketing effort.
A serious small-business app is a low-five-figures build and an ongoing annual commitment to keep it healthy. Anyone quoting a few hundred pounds for a "real app" is selling you a wrapped website, and you should know that is what you are buying.
Cheaper Things to Try First
Before committing to a native build, it is usually worth proving the demand with something lighter:
- A fast, excellent mobile website that does the core job. If people will not use the mobile site, they will not use the app.
- A PWA to test whether people actually want a home-screen presence and notifications, at a fraction of the cost and with no App Store gatekeeping.
- Existing tools - a booking platform, a loyalty app, a messaging channel - to validate the behaviour before you build bespoke.
If the lightweight version earns real, repeated use, you have proof worth investing in. If it does not, you have saved yourself a small fortune and learned something important.
How We Approach an App Build
When an app does make sense, we build it the way we build everything: small, hands-on, and honest. We have shipped our own apps to the App Store - Binny, a bin-day reminder for England, and Motorbook, a UK car-admin app - so we know what real submission, real maintenance, and real users involve, not just the demo.
That means starting with the honest scoping conversation above, building only what earns its place, testing on real devices, and using the same SEO and marketing skills to help people actually find the thing once it ships. You can see what we have built on the apps page.
If you have an idea - even a rough one - and want a straight answer on whether an app is the right move, get in touch. Sometimes the most valuable thing we tell a client is that they do not need to build one.
