It's one of the most common questions we get asked: "Should I build an app or a website?" The honest answer is: it depends on what your customers actually need to do. Get it right and you've invested wisely. Get it wrong and you've spent thousands on something people barely use.
Here's a practical framework to help you decide.
Start here: most small businesses need a website first
A website is your 24/7 shopfront. It's how people find you on Google, check your services, see your prices, read reviews, and decide whether to call. It works on every device without anyone needing to install anything. If you don't have a website (or you have a bad one), that's the problem to solve first — full stop.
For the majority of small businesses — tradespeople, local services, professional practices, shops — a well-built website is all they'll ever need. It handles discovery, trust-building, and enquiries without any of the cost or complexity that comes with an app.
So when do you actually need an app?
An app makes sense when a website genuinely can't do the job. Ask yourself these four questions:
- Do your users do a repeated task every single day? If someone is using your tool constantly — not just browsing, but actively working in it — an app delivers a faster, smoother experience than a website.
- Does it need to work offline? Websites need a connection. Apps can cache data and work in basements, warehouses, or on-site with patchy signal.
- Do you need device features? Camera, GPS, push notifications, biometrics — these are things an app does naturally that a website either can't do or does awkwardly.
- Does a native experience genuinely serve your users better? Sometimes the speed, the gestures, the polish of a native app is the product. If the experience is the differentiator, build for it.
If you answered yes to one or more of those, an app is worth considering. If you answered no to all of them, a responsive website will almost certainly do the job.
Two real examples from our own work
StandbyCalc is an iOS app we built for electrical engineers doing battery and UPS system calculations on-site. They needed quick, accurate results while standing in a server room or plant room — often with no signal. They also needed to export a professional PDF for the client on the spot. A website couldn't do any of that reliably. The app works offline, uses the device's native performance, and exports directly from the phone. It was the only sensible choice.
J4 Security Systems is a security installer based in the East Midlands. Their customers search Google for security installers, browse the services on offer, look at case studies, and then fill in a contact form. That's it. A clean, fast, well-optimised website was exactly the right tool — and it gets them found. An app would have added cost and complexity with zero benefit to the customer.
Same studio, two completely different answers, based entirely on what users actually need to do.
The cost reality
Be clear-eyed about this. A decent iOS app typically costs £5,000 to £20,000+ to build, and that's before the ongoing costs: the £99/year Apple Developer membership, annual updates when Apple releases a new iOS version, and any new features or bug fixes. Apps are a long-term commitment, not a one-off.
A well-built website for a small business costs significantly less and has much lower ongoing maintenance. For a clear breakdown of what a website costs for a small business in the UK, we've written that up separately. If a responsive website can do the job, it's almost always the smarter investment.
The "both" scenario
Some businesses genuinely need both — but for different purposes. Lettivo, a property management platform we've worked on, is a good example. The website handles marketing and discovery: landlords search for property management software, land on the website, read about the features, and sign up for a trial. The app, on the other hand, is where the actual work happens — managing properties, tracking maintenance jobs, communicating with tenants — every single day.
In this model, the website and the app aren't competing. The website gets people in the door. The app keeps them coming back.
When not to build an app
The clearest sign you don't need an app: if you can describe everything your users would do in it, and a responsive website could handle all of it, don't build an app. Save the budget. Spend it on a better website, better content, or better marketing instead.
Another warning sign: building an app because it feels impressive, or because a competitor has one. An app nobody uses isn't a feature — it's a liability you have to maintain.
The short version
- Everyone needs a website. Fix that first.
- You need an app if: users are in it daily, it needs to work offline, you need device features, or a native experience is the product.
- You need both if the website does marketing and the app does the daily work.
- If a website can do the job, let it.