Back to home

Article

Customer-First Website: What Makes a Business Website Effective?

What makes a business website effective? Start with who it's for, and work backwards from what they need.


What you'll take away

By the end, you'll have a clear understanding of your customer's journey and what they need at any given stage.

You'll also understand how to build a website that supports this journey, accurately represents your business, and helps turn visitors into customers.

I went to my developer and said, “I run a Google Ads management agency and I need a website.”

He made one.

The result looked impressive. It had all the things you'd expect from a modern agency website: cards, visuals, taglines, sections and polished design.

But when I started looking beneath the surface, I found a problem. The website contained processes that weren't actually ours. It made claims without explaining the reasoning behind them. Its trust signals were no different from those you'd find on countless other agency websites.

Much of the content was essentially filling the expected spaces on a website rather than representing what was actually true about our business.

It looked like a website. It didn't yet represent the business.

Later, when talking to my developer, I realised this wasn't unusual.

Business owners often come to developers with a similar request:

“I run a business. Can you build me a website?”

That's the entire brief. The developer is then expected to turn that vague request into a finished website.

The owner may have an intuitive understanding of:

“This is who we are. This is what we do. This is why customers choose us.”

But unless that understanding is communicated, the developer doesn't have access to it.

And the developer can't manufacture that knowledge simply by being good at web development.

Therefore the developer relies on assumptions to fill the missing information, often based on:

  • templates
  • industry conventions
  • previous websites
  • generic copy
  • AI-generated copy
  • generic design patterns

And that's how you get the website that looks appropriate for the category but doesn't really represent the business.

When the purpose and requirements of a website remain ambiguous, the ambiguity doesn't disappear. Someone has to resolve it, usually through assumptions.

A developer may know that they need more information, but knowing what to ask, how to ask it, and in what order is itself ambiguous.

“Tell me about your business” isn't enough.

The useful questions are determined by the decisions the website eventually has to support.

A website can be built by a developer, an agency, or increasingly by AI. You don't need to know how to code to get one built well.

But you do need to understand what you're asking to be built.

This article is about developing that understanding.

That's what changed when I built version 2 of the Ad-Ascent website. I didn't start with the website. I started with a much simpler question:

Who is this website for?

Then I worked backwards, applying the same reasoning to every component of the website.

That way of thinking is what we'll explore in this article.

A website is an asset, not just a collection of pages

A website is an asset that gives a business its own environment on the internet; one where people can explore the business more deeply.

They can learn about what it offers, understand how it works, look at its work, evaluate it against other options, decide whether there is a fit, and take the next step without needing to speak to the business at all.

Notice that we're describing the website from the visitor's perspective. That's intentional.

Often developers think about a website in terms of what the business wants to put on it: an About page, a Services page, some photographs, a few testimonials, and a contact form. But those things are only meaningful because of what they enable the people visiting the website to do.

And those people won't all arrive for the same reason.

Some may already be considering your business. They want to understand what you offer, decide whether there's a fit, compare you with their other options, and determine whether they can trust you enough to move forward.

Others may know little or nothing about your business. They may have encountered you while exploring a problem, considering possible solutions, looking for information, or simply exploring the internet.

In either case, they arrive at a different point in their relationship with the business.

The website needs to meet them where they are and give them what they need to move forward.

The Customer’s Journey

Imagine you're driving your car and it suddenly starts making an unfamiliar noise.

Your first thought probably isn't:

“Which mechanic should I choose?”

It's more likely:

“What's wrong with my car?”

You want to understand the problem.

You might listen to the noise more carefully, search online, ask someone you know, or take the car to a mechanic. And these don't always happen separately.

You might take the car to a mechanic precisely because you don't understand what's wrong. The mechanic examines it and tells you what the problem is, what caused it, and what needs to be done.

In that situation, the mechanic isn't only providing the service. They're also helping you understand the problem you're paying them to solve.

You may not know enough to fix it yourself. But if the mechanic can explain the problem clearly, show you what they've found, and explain why a particular repair is appropriate, you have a better basis for evaluating their recommendation.

Now you're dealing with another question:

“Is this the person I want to trust with my car?”

You might ask questions. You might look at their experience or previous work. You might look at reviews or ask someone for a recommendation. You might pay attention to how they diagnose the problem and explain what they're proposing to do.

As you learn more, you begin to form an impression of them.

Eventually, you may reach a point where you think:

“I think these people know what they're doing. I'm comfortable leaving my car with them.”

You've developed enough trust to move forward.

Notice what just happened.

You didn't go directly from having a problem to choosing a provider.

You needed to understand your situation, determine whether the proposed service was appropriate, evaluate the person providing it, and develop enough confidence to trust them with something that mattered to you.

Only then were you ready to choose. And if the experience was good, you might later recommend the mechanic to someone else.

The exact process may vary from one situation to another, but there is a useful progression underneath:

  1. Discover
  2. Understand
  3. Evaluate
  4. Trust
  5. Contact
  6. Purchase
  7. Refer

These stages help us think about the different things people may need as their relationship with a business develops.

A website can support that progression. It can help people discover a business, understand what it offers, evaluate whether it's right for them, develop trust, and take the next step. Although it's important to note that people may arrive at different stages, and some stages may take place elsewhere.

Another important nuance is that these stages often overlap in real life. We're separating the concepts to understand what a website needs to help people do.

The important question is what people need at any given stage, and how the website can help them move forward.

That's what we're going to explore next.

Helping visitors understand your business

Imagine you've arrived at the website of a business you've never encountered before.

Before you can decide whether you want to work with them, you need to form some basic understanding of what you're looking at.

Who are they?

What do they do?

Who do they do it for?

What exactly do they offer?

And perhaps:

Is this even relevant to me?

If the website doesn't make these things reasonably clear, it becomes difficult to move any further.

And so one of the first jobs a website needs to do is help someone form a clear picture of the business.

This is where the homepage becomes important. The homepage is often the first substantial place where someone encounters the business, but its job isn't necessarily to explain everything the business does.

Its job is to help the visitor understand what they're looking at and give them enough context to decide where to go next.

For example, imagine a Google Ads agency whose homepage simply says:

We help businesses grow.

The statement may sound appealing, but it doesn't give the visitor much to work with. They may still be wondering:

“What do you actually do?”
“What kind of businesses do you work with?”
“What does ‘grow’ mean here?”
“Is this something I need?”

Now imagine the homepage provides a more specific explanation:

We help small and medium-sized businesses attract and convert customers through Google ads and websites.

The visitor now has a clearer picture of what the business does, whom it serves, and how its services might help.

They can begin to decide whether the business is relevant to them and whether they want to learn more.

But the homepage doesn't necessarily need to explain everything in detail.

For example, a visitor might need a brief introduction to a service before deciding whether to explore it further. That introduction could appear on the homepage, with a link to a dedicated page explaining the service in greater depth.

Other information might belong in a different section of the homepage or on another page entirely.

The need for the information comes before the decision about where that information should live.

Some information belongs on the homepage because it helps establish the basic picture of the business.

Some requires a deeper explanation.

Some may deserve its own page.

There is no universal answer. The structure should emerge from what the visitor needs to understand, rather than from a standard list of pages that websites are supposed to have.

We're deciding what someone needs to understand about the business in order to move forward in their relationship with it.

Once visitors start to form an understanding of the business and its offering, another question becomes important:

“Is this actually right for me?”

And that takes us to the next stage: evaluation.

What do visitors need to evaluate your business?

Let's say you're considering hiring a service provider.

What would help you determine whether the service provider is right for you?

You might want to know whether they've handled situations like yours or done work similar to what you're looking for. You might want to know who will actually be doing the work and what experience or qualifications they bring. You might also want to understand how the provider approaches a problem and what their working process involves. Or perhaps something completely different.

What matters will vary from one situation to another.

The important thing to note is that, at the evaluation stage, the question becomes:

“What would help the people we're trying to serve determine whether this business is right for them?”

The answer determines what the website needs to provide.

If visitors need to see previous work, the website might need a portfolio or case studies. If the business's approach is an important consideration, it might need to explain that approach. If the process affects the customer's decision, the website might need to make it clear.

These don't necessarily need to become separate pages. A brief explanation might be sufficient in one context, while another business might need a dedicated page with considerably more detail.

The requirement comes first. The website element comes afterwards.

We're not simply collecting information the business has available or adding components because other websites have them.

We're determining what visitors need to know in order to evaluate the business, and then deciding how the website can best provide that information.

But even when visitors have enough information to judge that a business might be right for them, one question can remain:

“I think this could be right for me but should I work with them?”

That's where we turn to trust.

Building confidence in the working relationship

By this point, someone may understand your business, recognise that your offering is relevant to their situation, and believe that you have the capability to help them.

They're beginning to imagine working with you.

But some uncertainty may remain.

“This looks like what I need. But what would working with these people actually involve?”

They may be wondering:

  • How much will it cost?
  • How much time and effort will I need to invest?
  • How long will the service provider need to deliver?
  • What will happen once we start working together?
  • What can I expect from them?
  • How will communication work?
  • What happens if something changes?

These questions are different from those involved in evaluating the business.

During evaluation, the visitor is trying to determine whether the business and its offering are right for them.

Now, they're considering what choosing that business would mean for them.

They may believe the business can deliver what they need, yet remain uncertain about the commitment involved, the experience of working together, or whether the arrangement will fit their circumstances.

And this is where the website can do something different.

It can help the visitor build confidence in the business and in the relationship they are considering.

Some of that confidence may come from things we've already encountered while thinking about evaluation: previous work, experience, qualifications, or evidence of capability.

But confidence can also come from helping someone understand what happens after they choose you.

For example, if the process is explained clearly, the visitor can begin to imagine what working with the business will actually be like.

They might understand:

  • what happens first
  • what happens next
  • how long different stages might take
  • what the business will need from them
  • what they can expect from the business
  • how communication will work
  • what happens if something changes

The exact things that need to be explained will depend on the business and the relationship it is asking someone to enter.

The point isn't to add a generic “Trust” section to a website.

It's to ask:

“What uncertainty might still prevent someone from feeling comfortable moving forward, and what could the website do to reduce it?”

Sometimes the answer will be evidence.
Sometimes it will be transparency.
Sometimes it will be the people behind the business.
Sometimes it will be a clear explanation of the process and expectations.
Sometimes it will be something else entirely.

Trust, then, isn't something you create by adding a few testimonials or putting a “trusted” badge on the page.

It develops from the overall experience the business gives someone: what it says, what it can demonstrate, how clearly it communicates, and how well it sets expectations about the relationship.

And once someone has understood the business, evaluated the offering, and developed enough confidence in both the business and what working with it would involve, we reach a much simpler question:

“How do I take the next step?”

That is what the website needs to facilitate next.

The next step

Once a visitor is ready to move forward, what should happen next?

For a service business, that might mean inviting someone to:

  • Call the business.
  • Send an enquiry.
  • Request a quote.
  • Book a consultation.
  • Schedule an appointment.
  • Start a project.

The appropriate next step depends on the business, what it offers, and what the visitor needs to do to move forward.

A business might want someone to book a consultation. Another might need an enquiry before it can provide a quote. A business that sells directly online might want the visitor to purchase immediately.

The next step needs to make sense for both the visitor and the business.

This is where the call to action, or CTA, comes in.

A CTA is essentially the website saying:

“If you're ready to take this next step, here's how.”

A CTA invites the action, while the website needs some form of functionality to enable it.

A Book a consultation button might lead to a booking system.
A Request a quote button might open an enquiry form.
A Call us button might initiate a phone call.

The appropriate solution depends on the action the visitor needs to take and how the business needs to handle it.

The principles of a Customer-First Website

The principles we've been applying throughout this article can now be stated explicitly:

  • Start with the customer, not the website. Understand who the website is for, what they need, and where they are in their relationship with the business.
  • Understand the customer's journey. Consider what people need as they discover, understand, evaluate, and decide whether to work with a business. Remember that this journey isn't necessarily linear.
  • Let customer needs determine website requirements. Identify what visitors need to understand, what would help them evaluate the business, what could give them confidence, and what they need to do next.
  • Derive website components from those requirements. Decide what information to provide, how to organise it, how to present it, and what functionality is needed. Don't add pages or features simply because other websites have them.
  • Represent the business accurately. The website should reflect what the business actually offers, how it works, and what customers can reasonably expect from it.

These principles give us a way to reason about what makes a business website effective. They move us beyond asking what a website should look like or which pages it should contain, towards understanding what it needs to accomplish.

The next step is to translate these principles into concrete website requirements:

  1. Content
  2. Organisation
  3. Design and presentation
  4. Functionality

That's what we'll explore in the next article.

Wondering what your website needs to do?

We'd start with who your website is for — not with a list of pages it's supposed to have.

Start the Conversation
Related reading Understanding your business's online presence Before deciding what to build, understand what your business needs the internet to do. Read the article