Your website is not a brochure any more

Ten years ago a small-business website had one job: exist. Somebody searched your name, found an address and a phone number, and called. The site was a leaflet that happened to be online, and that was enough, because the alternative was the phone book.

That is no longer what people do. They want to finish the task on the page they landed on — book the table, order the part, pay the invoice, check whether the job is done. If your site cannot do that, they go somewhere that can. Very often that somewhere is a platform taking a cut of the sale, and you have paid for a website whose main function is to send customers to a competitor of your own margin.

The difference between a site and an application

A brochure site presents information. A web application lets someone do something, and remembers that they did it. That distinction used to carry a large price tag; it does not any more. Booking, ordering, customer accounts, quote requests, job tracking, document upload and payment all run comfortably in a browser now, on a phone, with nothing to install and nothing to approve in an app store.

What actually changed is not the technology so much as the expectation. A customer who books their doctor, their haircut and their groceries on a phone does not make an exception for you because you are smaller. They are not comparing you to the shop down the road. They are comparing you, without thinking about it, to the last easy thing they did on their phone.

Start with the one thing they came to do

You do not need to build all of it, and you should not try. Work out the single action most visitors want to complete, and make that action possible without a phone call.

For a restaurant it is almost always ordering. For a contractor it is a quote request with photographs attached, because the photographs are what let you answer without a site visit. For a clinic it is scheduling. For a wholesaler it is checking whether something is in stock, which is also the question that eats the most staff time on the phone.

Everything else on the site is supporting material for that one action. Your story, your team, your accreditations — these matter, but they matter as reassurance on the way to the thing the visitor actually came for. A site organised around the owner's sense of importance rather than the customer's task is the most common and most expensive design mistake we see.

What this looks like on an actual invoice

A contractor we work with was fielding roughly forty quote calls a month. Each one ran ten to fifteen minutes, most of it asking the same four questions and trying to picture a job he could not see. Perhaps a third turned into work.

The change was not a redesign. It was one page: describe the job, attach photographs, choose a rough budget band. Nothing clever.

What it altered was the shape of his week rather than the number of leads. The calls he took were with people who had already described the problem and shown him the room, so they started at the second question instead of the first. The unserious enquiries mostly stopped arriving, because filling in a form with photographs is more effort than dialling a number — which is a filter, not a flaw.

None of that shows up in a traffic report. It shows up in how many hours a week he spent on the phone.

The test that tells you whether it is working

Watch someone use it. Not a friend who wants to be encouraging — an actual customer, on their own phone, without help. Give them the task and say nothing.

You will learn more in four minutes than from a month of analytics. You will see where they hesitate, what they tap that is not a button, which word they read as meaning something you did not intend. Every business we have done this with has come away with two or three changes that were obvious in hindsight and invisible beforehand.

Analytics tell you what happened. They do not tell you why, and the why is where the fix is.

What it costs to get wrong

The expensive mistake is rarely choosing the wrong feature. It is building something nobody can maintain: a custom booking system only one developer understands, on a plugin that stops being updated, collecting data that is backed up nowhere.

Whatever you build, get answers to three questions before it goes live. Who can change it next month — you, your staff, or only the person who built it? Where is the data backed up, and has anyone ever restored one? And what happens when the person who built it is unavailable for a fortnight?

A proposal that cannot answer those is not cheaper than one that can. It has simply moved the cost somewhere it will not appear until later, usually at the least convenient moment.

Where to start if the site you have is a leaflet

Do not rebuild everything. Add the one action, on the page people already land on, and leave the rest alone until you know whether it gets used.

That is a small piece of work with a measurable result: either people use it or they do not, and you will know inside a month. It is a far better first step than a redesign, which takes a season, costs several times as much, and changes so many things at once that you cannot tell which of them worked.