Your Website Should Save You Time, Not Just Look Good

Ask a business owner what their website is for and you will usually hear something about credibility: looking professional, being findable, giving customers somewhere to check before they get in touch. All of that is true.

There is another benefit that rarely makes it into the brief. A well-planned website quietly absorbs the questions you answer over and over — the ones you have typed into an email so many times that your hands know it without thinking.

That is worth paying attention to, because those questions are not free. Each one costs a few minutes of attention, usually interrupting work that needed it.

The hidden cost of repeating yourself

Every business has a list. Which services are included, how long things take, where you work, how pricing is arranged, what a customer needs to prepare, when someone becomes eligible, what happens after they get in touch.

Some of these come up in almost every first conversation. Some arrive at eight in the evening by email. Some come from people who were never going to become customers, and who would have worked that out from one paragraph on your website.

Not every business experiences the same problem, and plenty will recognise only one or two items on that list. The point is to notice which questions belong to yours — and how much of your week they consume.

Answer questions before a conversation begins

A website can hold a great deal of routine information without becoming a manual nobody reads, if that information is placed where people actually look for it.

• On a service page, explain what the work covers, what changes the scope, and roughly what it involves.
• In a short FAQ, answer the questions that come up in nearly every first enquiry.
• On a contact page, explain what happens after someone gets in touch.
• In project examples, show the kind of requirement you handle, in the language customers use.

The test for each of these is simple. If a question is asked before someone decides whether to contact you, it belongs somewhere they will see it before they decide.

Set expectations from the beginning

Most friction in a new customer relationship is not about price. It is about assumptions that were never discussed.

Explaining what happens next is genuinely useful:

• What is included in the service, and what is not.
• How the work is run, and who does what.
• Approximate timescales, with a word about what makes them move.
• What the customer needs to prepare or decide.
• What happens after they get in touch, and how quickly.

Publishing a range or a "from" figure works well for some businesses; for others, quoting always requires a conversation. That choice is yours — the useful part is telling people which it is, so they are not left guessing.

The same applies to guarantees and commitments. Publish the ones you already make, and leave the rest out.

Help customers take the right next step

Confusion about how to contact a business leads to two poor outcomes: enquiries that never arrive, and enquiries so vague that they take three messages to untangle.

Clear signs help:

• A contact method that is easy to find, wherever someone is on the site.
• A form that asks for what you genuinely need — no more.
• A booking route with real availability, and a note on what happens after booking.
• A sentence telling people what to expect next, and by when.

None of this requires new technology. It is a matter of saying what is true and making the route obvious.

Help visitors arrive better informed

There is a version of this that helps you, and a version that helps the customer. They tend to be the same version.

When someone understands your services and what you need from them, the first conversation starts further along. Instead of explaining your process and eligibility, you can explore what they actually need. Instead of a cautious message that begins "I was wondering if you could tell me...", you get a specific question you can answer.

Visitors rarely mind reading. They mind reading something that turns out not to have answered their question.

Keep the website useful after launch

A website is not a one-off project. Details change: services grow, timescales shift, prices are adjusted, contact addresses move, common questions change with the seasons.

Every one of those changes is an opportunity. If a question starts appearing repeatedly, that is a signal that it should be answered on the site — with the answer you now know you want to give.

It is worth returning to the site every few months and asking a simple question: what are we explaining most often this quarter, and does the website say it?

A five-question exercise

Write down the five questions customers most often ask before they choose or contact you. Be honest — include the ones that are slightly awkward to answer, because those are usually the ones costing the most time.

For each one, decide three things:

1. Is this a deciding question? If people ask it before choosing you, it belongs on the website. If it only comes up once a project has started, it may belong in a welcome email instead.
2. Who needs it? A question that only applies to one type of customer is usually better placed on the relevant service page than in a general FAQ.
3. Is it already answered well? A page that answers it vaguely is worse than no answer at all — people will still ask, now with an extra layer of confusion.

Then put a date in your calendar to look at the list again. Questions change as a business changes.

Be realistic about what a website can do

A website will not remove the need for conversations. Complex requirements, unusual situations and anything carrying real risk still need a person, and customers often want one.

Nor should a website try to answer everything. Some questions are better handled in a short call than in three paragraphs of text, and some answers change depending on who is asking.

Its job is narrower and more useful: make routine information easy to find, reduce the repetition you can reduce, and help the conversations you do have start in a better place.

The takeaway

A website that only presents a business is doing half of its job. The other half is answering the questions you would rather not answer five times this week — clearly enough that people arrive informed, and accurately enough that they trust what they read.

Pick one question you answer most often and check whether your website answers it. If it does not, that is a good place to start.

If you would like help working out which questions are worth answering and where they belong, tell us how your enquiries usually begin. You can also read more in our journal.

Frequently asked questions

Should every common question go into a FAQ?

No. A general FAQ works for questions that apply to everyone. Anything specific to one service belongs on that service's page, where the reader is already thinking about it.

How long should an answer be?

Long enough to be useful, short enough to read standing up. Three or four sentences usually covers the question, with a link to the relevant page for anyone who wants more detail.

What if publishing more detail puts customers off?

It rarely does. Customers are usually reassured by detail that shows you understand their situation. What does put people off is vagueness — and the uncertainty it creates.