All articles
6 min read

Website or web app: What does my business really need?

A website explains what you offer and generates inquiries. A web app models workflows. Find out which solution your business needs and how to define its scope.

Website or web app: What does my business really need?

Your business needs a new website. Customers should be able to understand what you offer, find your services and get in touch. At the same time, you’re considering adding a customer portal. Customers could use it to download documents, track orders or request changes.

That means you already have two different tasks on the table. Explaining what you offer is a different job from managing orders and customer data. This makes a significant difference to the planning. It affects development effort, ongoing costs and operational requirements.

So I’d start by clarifying what you want people to be able to do after visiting your site.

What a website can do for your business

A business website provides information and guides visitors towards a specific action. Someone looks for your service, checks out what you offer and sends an enquiry. A job applicant learns about your business and applies for a position.

For this, you need clear content, a suitable design and a site that works on smartphones. Visitors should be able to tell who your offer is for, what tasks you take on and how to reach you.

A website can also present extensive content. For example, my work for Futouris involved a website with lots of information and toolkits whose content the team can manage themselves. So the amount of content alone doesn’t turn a website into a web app.

When planning, the questions are: Which pages do you need? Who writes and updates the content? How can visitors find the information they need? And what details do you need to handle an enquiry?

When you need a web app

A web app is an application used in a browser. People use it to get things done. They create records, manage processes, approve items or view information linked to their account.

Take a customer portal for a service provider. A customer logs in and sees their current orders. They upload documents, fill in missing details and check the progress. Your team works on the same order and decides what information the customer is allowed to see.

The software needs to reliably bring several things together: user accounts, stored data, access permissions and the workflow. It needs to be clear who can change an order, when it counts as complete and what happens if information is missing.

At idea-ly, employees can submit ideas that companies can then track in an organised way. That’s a job for an application: information is collected and processed as it moves through the workflow.

A web app makes sense when workflows like these are a key part of your project.

Individual features don’t determine the scope of the whole project

A form, login or booking feature doesn’t tell you much about the scope on its own. What matters is what needs to happen behind it.

A contact form can send a message to your business. But if the enquiry then needs to be linked to a customer, handled by several employees and approved according to specific rules, it becomes a much more extensive process.

Existing systems can also handle tasks like these. On the careers website I developed for hybrid-experts, application data submitted through a form is sent directly to Personio. This means the website is connected to an existing recruitment process.

So if you already use suitable software, it’s worth checking what it can do. Perhaps all you need is to connect it to your website. A custom application needs a specific reason, such as a workflow that your existing systems don’t support well enough.

Look at where manual work happens today

Before you start listing features, describe a real process in your business. For example, follow it from the moment a customer enquiry comes in to when it’s fully handled.

  • Where does the enquiry come in?
  • Who handles it, and what information do they need?
  • Where is the data stored?
  • Which details are transferred to other systems?
  • What questions come up regularly?
  • How does the customer find out that their enquiry has been dealt with?

This shows what the new solution needs to do. If enquiries are already handled reliably and all you really need is a clearer online presence, you can focus the scope on the website.

But if details are being copied from emails into spreadsheets, documents are searched for in several folders and people are constantly calling to ask about status updates, there may be a case for an application. You can then look at which of these tasks could be handled together.

A rough calculation can help here. How often does the process occur? How long does it take to handle? Which parts could the software eliminate? These details give you a basis for estimating development effort.

Ongoing work is part of the decision

A website still needs looking after after it launches. Content changes, forms need to work and technical components need to be kept up to date.

With a web app, you’re also responsible for the processes it handles. If your team uses it every day, you need a system for dealing with errors, backups and changes. New features can affect existing workflows. That’s why you need to check that those workflows still work before releasing an update.

Responsibilities should also be clear. Who helps users when they run into problems? Who decides on changes? Who looks after the technical operations?

These tasks should be part of the planning from the start. They affect which solution you can maintain over the long term and what budget you should set aside for it.

Define the initial scope around a specific task

For a website, the initial scope could include service pages, case studies, a contact form and a way to update the content. That’s enough to find out whether visitors understand what you offer and send relevant enquiries.

For a web app, the initial scope could cover one complete process: a customer submits an enquiry, your team handles it and the customer sees the result. You can add reporting or other workflows once this process works in everyday use.

A website and an application can also work together. The public-facing site explains what you offer, while logged-in customers handle their tasks in the customer portal. In that case, it’s important to define the scope of each area separately. Otherwise, a planned website can quickly turn into a software project whose scope only becomes clear during development.

If you’d like to discuss your project with me, briefly describe what visitors or employees should be able to do in the future and how the process works today. That gives us a basis for working out which pages, features and integrations your business actually needs.