Simple website, booking system or owner app: which does your business need?

Ask almost any small business owner what their website is for and you will usually get a warm, slightly vague answer. Look at how they actually use it, though, and the answer is usually blunt: they want people to get in touch, they want people to book them, they want to sell something, or they want to stop fighting a piece of software that does not quite do the job.

Those four answers lead to four genuinely different builds. Treating them as the same project is the most common reason a business pays twice, or ends up with a feature-rich site that is still awkward to run.

The test: pick up the phone

Put your phone down, open your website, and try to do the one thing a customer would do: get in touch, book, or buy. Where does it break?

• You find an email address or a form and nothing more. You are an enquiry-only website. You need a good, fast, trustworthy site that makes contacting you obvious. That is the Launch shape of project.
• You want customers to choose a time, pay a deposit and see it in a diary. You need customer booking plus owner controls. That is the booking systems work.
• You want people to browse products, pay and for you to know what left the shelf. You need an online shop.
• You are chasing data between three tools that do not speak to each other. You need a custom app or automation.

If two of those feel true at once, you do not have to choose between them today. Most owner apps sit on top of a website deliberately, and the honest answer is usually that the website is the smaller half of the job.

The four needs, side by side

These are descriptions of fit, not a ranking. Plenty of good projects sit across two of them, and we will tell you honestly when the simpler option is the right one.

Why the phone decides it more often than the brief

Almost all of your customers will find you on a phone, often while standing up, often on patchy mobile signal. That has three consequences worth deciding on before any design work starts.

Access should not depend on a login

If someone has to create an account to see your prices, your availability or your before-and-after gallery, most of them will not bother. Keep the public site open to everyone. If you need a private area, that is the owner side, and it is a deliberate extra, not a condition of the public page.

Own your content and your domain

Your photographs, your copy and your domain name should be yours, editable by you, and not trapped inside a platform that can change the rules or the price. If you cannot export your content or move your domain elsewhere, you do not own it, you are renting it. We build so that leaving is always possible, even though we would rather you stayed.

Editing should not need a manual

If changing a price means emailing a developer, you will stop making changes, and the site will slowly go out of date. The content you touch weekly should be editable in plain language, ideally on the same screen you are already looking at.

What this looked like in practice

Three recent projects cover most of the range. They are worth reading because the shape of the need shows up long before the price does.

A quick checklist before you brief anyone

Run through these before you spend time writing a spec. Most businesses can answer them in ten minutes, and the answers usually reveal the shape of the project.

If your answers point in two directions, that is normal and worth saying out loud on a call. Half the value of talking it through is noticing which of the two you should do first and which can wait.