Most businesses that ask us for an app do not need one. That is not a sales position — an app is the more expensive project, so talking you out of it costs us money. It is just usually true.
Here is how to tell which side of the line you are on.
The question that settles it
Will the same person use this more than once a week?
That is nearly the whole test. Apps earn their cost through repeat use. Somebody has to want your business on their home screen, and they only want that if they are coming back constantly — a loyalty scheme they use weekly, a system staff work in daily, a service with genuine ongoing engagement.
If a customer deals with you twice a year, they will not install anything. They will search, land on your site, and call. Building an app for that customer means building something they will never download.
You probably need a website
- Customers find you by searching.
- They buy from you occasionally rather than constantly.
- What you need is to be found, be credible, and be easy to contact.
- You are a service business — trades, professional services, hospitality, health.
Apps do not appear in search results. A website is how people find you in the first place, which is why an app is rarely a replacement for one and almost always an addition to it.
You might genuinely need an app
- People use it several times a week, every week.
- It needs something only a phone does properly — the camera in a workflow, location in the background, working offline in places with no signal.
- Your staff work in it all day and it needs to be one tap away.
- Push notifications are the point, not a nice-to-have.
If that describes you, that is a real app project and it should be scoped as one.
The option most people have not heard of
There is a middle path, and it covers a surprising number of the businesses that come to us asking for an app.
A website can be built so it installs to a phone's home screen, opens without a browser bar, works offline, and sends push notifications — while still being a website that Google can find and index. No app store, no review process, no separate build for iPhone and Android, and no second codebase to maintain forever.
We built exactly this for a tattoo artist in Fort Worth: an installable app with push notifications for new booking requests, on top of a site that still ranks for what she does. That case study is here.
It is not the right answer for everything. If you need deep hardware access or your users genuinely expect to find you in the App Store, build the app. But for "I want customers to have us on their phone", it does the job at a fraction of the cost.
What each one really costs
The build is the smaller number. What people underestimate is the running cost.
A website needs hosting and maintenance. That is a known, modest monthly figure.
A native app needs developer accounts for both stores, and it needs updating when Apple and Google change their requirements — which they do, on their schedule, whether or not you have budget that quarter. An app that is not maintained stops working. A website that is not maintained just gets gradually out of date, which is a far gentler failure.
Start from the problem
The businesses that get this right do not start from "should we build an app". They start from a specific problem — too much time on the phone taking bookings, customers who never come back, staff filling in paper forms and typing them up later.
Describe the problem and the right build is usually obvious. Start from the technology and you can spend a lot of money solving something you did not have.
If you are weighing this up, tell us the problem rather than the solution and we will tell you honestly which one you need — including when the answer is neither.