Skip to content

Our Approach to Building a Website A good website does not start with a homepage design. It starts with understanding what the website needs to achieve, who it needs to work for and what might currently be getting in the way of the business growing online. That sounds obvious, but it is one of the areas where website projects can go wrong surprisingly quickly. A business can have a clear idea of the pages it wants, a logo, a colour palette and a list of features, yet still end up with a website that looks perfectly respectable without actually making the business easier to find, understand or choose. Our approach is different. We combine our experience in web design, UX, UI, content, SEO, conversion and digital strategy with AI-assisted research, analysis and design to look at the website as a complete system rather than a collection of individual pages. The purpose is not simply to produce a better-looking website. It is to remove the things that are getting in the way of growth.

Approach To Building A Website

Last updated 24 September 2026

We Start With the Business, Not the Design

Before deciding what a website should look like, we need to understand what it is supposed to do.

That means looking beyond the obvious information about the business and understanding how the business actually operates, where enquiries come from, what customers need to know before making a decision, what services or products are most important and where the opportunities for growth might be.

We also want to understand what is not working.

Perhaps the current website receives visitors but very few enquiries. Perhaps the business has excellent services but the website does not communicate their value particularly well. Perhaps customers repeatedly ask the same questions because the information they need is difficult to find. Perhaps the website has grown over several years and now feels disjointed, with pages and content added individually rather than as part of a coherent structure.

These are not simply design problems.

They are constraints.

The website should help remove them.

That is why we do not believe a website project should begin with somebody asking us which colour button they would like.

There is a much more important conversation to have first.

Finding the Constraints Before We Build

Every business has things that make growth easier and things that make it harder.

The website can be one of those things.

It might be making the business harder to understand than it needs to be. It might be attracting the wrong audience. It might be failing to communicate the difference between the business and its competitors. It might be difficult to use on mobile. It might have important information buried several clicks deep. Or it might simply look like a website from a different stage of the company’s development.

Our first job is to identify these constraints.

We look at the existing website, the structure, the content, the user journeys, the search opportunity, the competition and the wider market. Where useful, we use AI-assisted analysis to process information quickly, identify patterns and explore possibilities that would otherwise take considerably longer to investigate manually.

But AI is not making the decisions for us.

It is part of the toolkit.

Our experience is what determines which findings matter, which ideas are useful and which should be ignored.

That distinction is important because a website should never be designed simply because an analysis tool suggested something.

The technology helps us investigate more deeply.

Experience tells us what to do with what we find.

Strategy Comes Before Screens

A website can be beautifully designed and still fail because the underlying strategy is weak.

Visitors do not arrive on a website thinking about its visual design system. They arrive with a question, a problem, a need or an intention.

They want to know something.

They want to compare something.

They want to buy something.

They want to contact someone.

They want reassurance that they have found the right business.

The website needs to accommodate those different states of mind.

That means deciding what information should appear, in what order, and what the visitor should be able to do next.

We consider the important journeys through the website before committing to the visual design. That might mean someone arriving from Google on a service page, someone coming directly to the homepage after hearing about the business, someone viewing a product on a mobile phone or someone comparing the business with several competitors.

Each visitor can have a different reason for arriving.

The website needs to make sense to all of them.

Using AI to Extend the Thinking

AI has changed what is possible during a website project, but we do not see it as a replacement for expertise.

We use it to extend what we can investigate, test and explore.

It can help us analyse large amounts of information, examine competitor positioning, identify recurring questions, explore search behaviour, structure information, test alternative approaches and generate possibilities that can then be assessed from a design, UX and business perspective.

This gives us something particularly useful during a website project: the ability to explore more before we build.

Traditionally, some of these decisions would only become obvious after a design had already been produced or a website had already been developed.

By then, changing direction can be expensive.

Our approach is to use analysis and AI-assisted exploration much earlier, when changes are still relatively inexpensive.

That means we can ask better questions before development begins.

Could this service be explained more clearly?

Is there a better way to organise these pages?

Are customers likely to understand this terminology?

Is there an important question missing from the page?

Could the mobile experience be simplified?

Is there a stronger route from a search result to an enquiry?

Could the content be structured differently?

What happens if someone arrives here without knowing anything about the business?

These are the questions that influence the final website.

UX Is About Making Things Easier

UX, or user experience, can sound like another piece of digital terminology.

In reality, it is largely about making things easier.

A visitor should not have to think unnecessarily hard about where they are, what something means or what they should do next.

If someone arrives on a service page, they should be able to understand the service without hunting around the website.

If they are comparing options, the differences should be clear.

If they are ready to make contact, the process should be straightforward.

If they are using a mobile phone, they should not have to pinch, zoom, swipe around awkwardly or deal with tiny buttons.

Good UX often goes unnoticed because it simply feels natural.

Poor UX is different.

You notice it immediately.

You cannot find what you need. You click the wrong thing. The navigation does not make sense. A form asks for too much information. Important information is buried below irrelevant content.

Our job is to reduce that friction.

UI Design Gives the Strategy a Visual Language

Once the structure and user experience are understood, the visual design has a much stronger foundation.

UI, or user interface design, is not simply about making pages look attractive.

Typography, spacing, colour, imagery, buttons, cards, navigation, layout and interaction all influence how easily someone can understand what they are looking at.

A strong visual system creates hierarchy.

It tells the visitor what matters first, what matters next and what can wait.

That is particularly important on business websites because there is often a huge amount of information competing for attention.

The answer is not to make everything more prominent.

It is to decide what deserves attention and design the page accordingly.

This is where our design process combines human judgement with AI-assisted visual exploration. We can explore layouts and visual directions quickly, test different approaches and develop ideas at a speed that would have been difficult using a traditional design process alone.

But the finished design still has to answer a simple question:

Does this help the visitor understand and act?

If it does not, it does not belong there simply because it looks impressive.

Content Is Part of the Design

One of the biggest mistakes in website projects is treating content as something that gets added after the design is finished.

Content and design are inseparable.

A page cannot be properly designed until you know what the page needs to communicate.

That does not mean filling every section with large blocks of text.

It means understanding the information the visitor needs and deciding how best to present it.

Sometimes that will be a paragraph.

Sometimes it will be a comparison.

Sometimes it will be an image, diagram, product demonstration, statistic, testimonial or interactive element.

Sometimes the best decision is to remove information altogether because it is distracting from the main message.

We look at the content from several perspectives at the same time: what the business needs to communicate, what the visitor needs to understand, what search engines need to interpret and what information is likely to help someone move towards a decision.

That creates a much stronger relationship between content, UX and design.

Designed for Mobile From the Beginning

Mobile should not be treated as a smaller version of the desktop website.

People use websites differently on a phone.

They may be standing in a shop, sitting on a train, walking between meetings or looking something up quickly because they need an answer immediately.

The available space is smaller, attention is often more limited and interactions are different.

That affects everything from navigation and typography to image sizes, buttons, forms and the order in which information appears.

We therefore consider the mobile experience as part of the design from the beginning rather than leaving it until the end and simply making the desktop design responsive.

A page that looks excellent on a large screen can become unnecessarily long or difficult to use on a phone if it has not been properly considered.

The objective is not simply for the website to “work on mobile”.

It should feel as though it was designed for the device being used.

SEO Is Built Into the Thinking

SEO should not be something added to a website after the design has been completed.

The structure of a website, the pages it contains, the way information is organised and the language used throughout the site can all influence how well search engines understand the business.

That does not mean designing a website around keywords.

It means understanding what potential customers are searching for and making sure the website provides useful, relevant destinations for those searches.

During the process, we consider the relationship between the business, its services, its audience and the opportunities available through search.

This can influence the site structure, page hierarchy, content, headings, internal linking and the information provided on important pages.

It also means thinking about search intent.

Someone searching for a service may need a very different page from someone researching a problem or comparing different options.

The website needs to accommodate those different needs rather than treating every visitor as though they arrived through the same door.

We Look at the Competition, But We Do Not Copy It

Competitor research is useful because it tells us what customers are already seeing when they search for businesses like yours.

It can reveal common patterns, gaps in the market, weaknesses in competitors’ websites and opportunities to communicate something differently.

But there is little value in building a website that simply looks like everyone else in the industry.

If every competitor uses the same structure, the same language and the same generic claims, copying that approach simply makes another indistinguishable website.

We look at what is already being done, but we also ask where the opportunity exists to do something more clearly, more usefully or more convincingly.

The objective is not to be different for the sake of being different.

It is to give the business a stronger position.

Interactive Elements Should Have a Purpose

Interactive design can be very effective, but interaction should not be added simply because technology allows it.

A moving graphic, animation or interactive component needs to help the visitor understand something, explore something or make a decision.

For example, an interactive comparison can make complex choices easier to understand. A visual product selector can help someone narrow down options. An animated explanation can demonstrate how something works more effectively than a paragraph of text.

The important question is always what the interaction contributes.

If it makes the information easier to understand, it has a purpose.

If it merely makes the page move, it probably does not.

This is particularly important on mobile, where unnecessary interaction can quickly become frustrating.

Building a Website That Can Grow

A website should not be treated as a finished object that gets launched and then left alone for five years.

Businesses change.

Services change.

Markets change.

Customers ask different questions.

New opportunities appear.

Search changes.

The website needs enough flexibility to accommodate that.

That means thinking about the structure and underlying system rather than designing only for the immediate launch.

A good website should make it possible to add useful content, new services, landing pages, products, resources or campaigns without having to rebuild the entire thing every time the business develops.

This is another reason why the thinking that happens before development matters.

A website can look great on launch day and still be poorly structured for the future.

We want the opposite.

The launch should be the point from which the website becomes a useful platform for continued growth.

Testing the Thinking Before Launch

A website should not reach launch simply because all the pages have been built.

We look at the experience as a complete journey.

Can someone understand the proposition quickly?

Can they find the information they are likely to need?

Does the navigation make sense?

Are the important calls to action obvious without becoming intrusive?

Does the content answer the questions people are likely to have?

Does the design establish the right level of confidence?

Does the website work properly across different screen sizes?

Are there unnecessary steps that could be removed?

Does the page still make sense when somebody arrives directly from Google rather than through the homepage?

These questions matter because visitors do not experience a website in the neat sequence in which it was built.

They can arrive almost anywhere.

Every important page therefore needs to work as an entry point into the business.

Analysis Does Not Stop When the Website Launches

One of the advantages of building a website properly is that the launch is not the end of the process.

Once the website is live, there is an opportunity to see how people actually use it.

Search data can show which pages are being discovered and what people are searching for. Analytics can reveal how visitors move through the website. Enquiry patterns can reveal where people are still asking questions that the website could answer better.

This creates a useful feedback loop.

Instead of assuming that the original decisions were perfect, we can use evidence to understand what happens in the real world and identify opportunities for improvement.

That might lead to a new landing page, a clearer service explanation, a change to the navigation, improved content or a completely different route through part of the website.

The website becomes something that can continue to improve rather than something that is simply launched and forgotten.

Why We Work This Way

The technology available to us today has changed the way websites can be planned and designed.

We can research more deeply, analyse more information, explore more possibilities and move from an idea to a visual concept far more quickly than was possible with traditional website processes.

But technology on its own does not produce a good website.

The value comes from combining it with experience.

We bring together strategy, UX, UI, content, SEO, mobile design, conversion thinking and analysis, using AI as an additional capability throughout the process rather than treating it as the product itself.

That means we can spend more time thinking about the things that actually matter.

Who is this for?

What are they trying to achieve?

What is stopping them?

What does the business need to communicate?

What should happen next?

What could be simpler?

What is missing?

Where is the opportunity?

And ultimately:

What is preventing this website from doing more for the business?

The Aim Is Not Simply a Better Website

A new website should certainly look better.

It should also be easier to use, easier to manage and easier for search engines to understand.

But those are means rather than the final objective.

The real opportunity is to create a website that helps the business move forward.

That could mean making a complex service easier to understand, turning more relevant search traffic into enquiries, improving the experience on mobile, giving a growing business a clearer digital presence or creating a structure that allows the website to support new opportunities over time.

That is why our approach is built around removing constraints.

We do not want to simply reproduce the website you already have with a newer design.

We want to understand what is holding it back and then use strategy, design, content, technology and analysis to remove those barriers.

The result should not just be a website that looks better when it launches.

It should be a website that gives the business more room to grow.

And that is ultimately what we believe a website should be built to do.