Do you need a website, or a web app?

“We need an app” is often a useful starting point, but it is not yet a useful specification. People use the word app to mean a public website, a private customer area, an internal tool, a mobile application or a single feature inside an existing system.

The right choice depends less on what the product is called and more on the job it needs to do.

Start with the user’s job

Write down the main thing each audience needs to accomplish. Be specific:

A prospective customer needs to understand the service and make an enquiry.
A customer needs to see progress and download documents.
A member of staff needs to turn incoming information into a quote.
A manager needs a reliable view of work, costs or capacity.

If the job is mainly about explaining, reassuring and creating a route to contact, a well-structured website may be enough. If people need to sign in, return regularly, save information, follow a process or work with data, you are probably looking at an application or a website with application features.

Look for repeated work

The strongest case for a custom product is usually a repeated process, not a desire to have something bespoke.

Ask:

How often does the process happen?
How many people touch it?
Where is information copied or checked by hand?
What happens when someone is unavailable?
What does an error cost in time, money or customer confidence?

If the answers are vague, the process may need clarification before it needs software. Mapping the current steps often reveals that one small improvement, such as a better form or a single source of truth, will do more than a large platform rebuild.

Choose the smallest useful shape

A sensible progression might look like this:

Website: public information, content, enquiries and clear calls to action.
Website plus integrations: forms, payments, booking, CRM or email workflows connected to existing services.
Web app: accounts, permissions, saved records, dashboards and repeat tasks.
Mobile app: a strong reason to use a phone-specific capability, such as notifications, camera access or offline use.
Custom platform: several connected workflows, user types and business rules that off-the-shelf tools cannot handle cleanly.

There is no prize for choosing the most complicated option. More software creates more things to design, secure, maintain and explain to users.

A useful test before commissioning anything

Describe the first version without naming a technology. Include the user, the task, the information needed and the successful outcome.

For example: “A customer can submit a request, see its current status and receive the next action by email.” That is a better brief than “We need a React app with a dashboard.” It leaves room to find the simplest dependable way to deliver the result.

The best digital foundation is the one that supports the important work today and leaves a sensible route for tomorrow. Start with the decisions and repeated tasks. Let the technology follow.