App or website? What a small business actually needs.

Every so often a client asks us, "Should we have an app?" It is a fair question. Apps feel modern and look impressive on a pitch deck. But for most small businesses in Norwich and Norfolk, an app is the wrong first move. It costs more, takes longer and asks customers to do something they often won't: download it.

That said, sometimes an app is exactly right. Here is how we help clients decide.

Three different things people call an "app"

Before you weigh up cost, be clear about what you actually mean. There are three options, and they get mixed up all the time.

1. A website

A public site that anyone can find through Google, open on any phone or laptop and use straight away. Built well, it works on every screen size. For most businesses this is where enquiries, bookings and sales happen.

2. A web app

Software that runs in the browser, usually behind a login. Think dashboards, client portals, booking systems or account areas. No download, no app store, and you update it once for everyone.

3. A native app

An app installed from the Apple App Store or Google Play. It can work offline, use the phone's camera and storage more deeply and send push notifications. It also needs app store approval and, often, separate work for iPhone and Android.

Most businesses asking for an app actually need a better website or a web app.

When a website is enough

If customers mainly come to you to find out what you do, see prices, get in touch, book or buy, a website does the job. People will not install an app to look up a cafe, a surveyor or a personal trainer once or twice a year.

A good example is our work for NR Surveyors, a RICS regulated firm in Norwich. Home buyers get an instant price, sign the engagement letter and pay online, so a survey can be booked from start to finish without a phone call. All of that runs on the website. Nobody needs to download anything, which matters when someone is booking a one-off survey.

When a web app makes sense

A web app suits work where people log in regularly and share information, but don't need anything a browser can't do. Typical signs:

• Several people need to see the same records, like a business and its accountant.
• Users work mostly at a desk, on a laptop.
• You want to change things often without waiting for app store review.

Qantori is a good case. It is a shared workspace where small businesses and their accountants keep documents, bank transactions and HMRC filings in one place. We built the whole platform as a web application, in English and Bulgarian. Accountants and their clients use it from the browser, so there is nothing to install and every update reaches everyone at once.

When a native app is worth it

A native app earns its cost when the work happens away from a desk and the phone itself is the tool. Look for these signs:

1. Poor or no signal where people use it. Offline working is the biggest reason to go native.
2. Heavy use of the camera or photos that need to be organised on the spot.
3. The same people use it daily, so a download is no barrier.

This is exactly why we built an iOS app for PropScribe. It helps residential surveyors write RICS Home Survey reports from their site notes. Signal on site is patchy, so a tool that needs a connection was no good. The app captures RICS Level 2 and Level 3 surveys offline, with photos and condition ratings filed by section. Then the web dashboard is where the AI draft is checked and signed off, back at a desk.

Notice the split. The bit used in the field is native. The bit used at a desk is a web app. You don't have to choose one for everything.

The costs people forget with apps

The build is only part of it. Native apps bring extra running work:

• App store review for every release, which can slow down fixes.
• Keeping up with phone software updates, which can break things that worked last month.
• Payments get more complicated. Selling subscriptions inside an iPhone app usually means going through Apple's in-app purchases. For PropScribe we set up Stripe and App Store subscriptions on one set of plan limits, with purchases verified on the server, so a customer gets the same plan wherever they paid.
• Getting downloads. An app nobody installs does nothing for you. A website can be found through search from day one.

Questions to ask before you commit

• How often will each person use it? Once a year, or every day?
• Will they have a reliable connection?
• Do they need the phone's camera, storage or notifications in a way a browser can't manage?
• Do you need to be found by new customers through Google?
• Who will look after it once it launches, and how often will it change?

If most answers point to occasional use, decent signal and a need to be found, start with a website. You can always add a web app or native app later, building on the same foundations.

Build for how your customers actually work, not for what looks impressive.

Not sure which you need? Tell us how your customers use your service and we will give you a straight answer, even if it is "you don't need an app".