What are the stages of creating a custom website?

Creating a custom website follows a progression: understand the need, organise information, design the experience, make it usable and check the delivery. The order matters because a decision left open early can require several parts to be revisited later.

There is no identical schedule for every business. A company website, a shop and a booking journey have different dependencies. Each project nevertheless benefits from knowing what is expected at every stage, who participates and which decision allows work to continue.

1. Define the brief around priority uses

The first task is to describe what the site must enable. Identify visitors, their questions and the main intended action: understand expertise, examine a project, request an appointment or prepare a reservation.

Collect constraints as well: available content, existing tools, languages, business deadlines and the time your team can contribute. These facts influence scope before layout preferences are discussed.

The outcome should be a shared brief covering objectives, proposed pages, essential functions and responsibilities. Approval means the company and agency are working towards the same need. It does not mean every visual or technical detail has already been settled.

What your team prepares

Bring examples of customer enquiries, a description of the offer and representative content. Explain what must remain accurate, including available services and contact arrangements. An agency can organise information; it cannot replace your knowledge of the business.

2. Organise pages and information hierarchy

The site structure describes the main pages and their relationships. It helps check whether visitors can find a service, understand its value and continue. The menu is only the visible part of that organisation.

Next, define the content needed in principal templates: home, service, project, article or contact. Establish what each page explains and what it does not need to repeat. Clear structure supports writing and avoids pages that attempt to contain the entire company story.

As a fictional illustration, a villa builder might separate its method, completed projects and enquiry page. Projects show concrete choices; the method explains how an engagement works. The content complements itself without telling precisely the same story twice.

Approval concerns page logic and necessary information. This is the moment to identify a missing service or a section with an unclear role, before its presentation is developed in detail.

3. Prepare copy and visual assets

Content production can begin once its purpose is defined. It may run alongside design if the information that determines structure is available. A temporary page title can support exploration; an undecided offer makes approval much less reliable.

Create a table for each page: copy to write, facts to verify, photography to supply, responsible person and expected date. Distinguish files that exist from files that are genuinely usable. An excessively cropped image or an unapproved version is not necessarily final material.

If animation is planned, specify its story and the assets needed. Showing transformation or assembly requires a comprehensible sequence of moments, rather than an impressive image alone. Media work should be coordinated with the sequence’s place in the page.

Plan adaptation and review for additional languages. Layouts then need checking with the corresponding copy. A longer translation can change the balance of a screen; discovering that before publication allows it to be addressed within the design process.

4. Establish art direction

Art direction connects company identity to the website’s visual choices: typography, colours, composition, photography and reading rhythm. It provides shared rules so pages belong to a recognisable whole.

An initial proposal may use a reference board and representative screens. Assess coherence with positioning rather than only your preference for one isolated element. Ask why a choice helps communicate the offer or makes information easier to read.

Approval sets a direction clear enough to develop the templates. It should distinguish a coherent adjustment from a complete change of visual world. If essential points remain open, name them rather than providing a broad approval that different participants may interpret differently.

5. Design screens and interactions

Layouts specify main page templates, hierarchy, components and content. Interactions explain what happens when someone opens a menu, starts an enquiry, browses a gallery or scrolls through a sequence.

Examine screens as a journey. An appealing page alone does not show whether visitors know where to go afterwards. Move from a service to a project and then contact. Consider labels, continuity of information and ways to continue or return.

Mobile versions should account for their own reading and action constraints. Some content changes order or presentation, and animation may need adaptation. Ask to see significant choices instead of assuming that shrinking the format resolves everything.

How to provide useful feedback

Group comments by page and need. “We cannot find how to request a visit after the gallery” is more useful than “something is missing”. Separate factual errors, usability difficulties and visual preferences. A central contact can send a summary approved by the relevant people.

6. Develop pages and functions

Development turns approved work into a usable website. It implements templates, content, administration and agreed functions. Connections to other tools are checked in this context, including the information and states involved.

The team should consider ordinary situations and potential errors: longer text, missing imagery, an incorrectly completed field or a temporarily unavailable external service. A demonstration is insufficient if it works only with ideal content.

Ask how progress will be shared. Checkpoints based on completed journeys are often more understandable than an abstract development percentage. They let you inspect what works and what remains without confusing a design with a usable version.

Keep new ideas distinguishable from the approved scope. Development often makes additional possibilities easier to imagine. Record their purpose and discuss the implications before adding them, so a useful suggestion does not silently change the work everyone expects.

7. Populate and review final content

Final population places approved copy and suitable media into the planned pages. It also checks links, labels and consistency between versions. A well-written file can still create a difficulty when placed in context.

Read each page within its journey. Are contact details correct? Is a withdrawn offer mentioned elsewhere? Does a card’s title correspond to the page it opens? These checks draw directly on your knowledge of the business.

Avoid distributing corrections across several conversations. Use a list with the page, affected passage and required change. This reduces ambiguity when many small items are converging towards publication.

Make the status of each page visible. A design may be approved while a photograph or a factual confirmation remains outstanding. Distinguishing these states helps prevent an apparently complete page from carrying unfinished information into launch.

8. Perform acceptance checks before launch

Acceptance checking is an organised review of the site before it is approved. It establishes whether expected journeys work and tracks problems requiring correction. It should involve more than viewing pages on one computer.

Classify issues by their effect. An enquiry that never arrives needs different treatment from a graphic preference. Identify new ideas that exceed the approved scope so they are not mistaken for corrections.

For each reported issue, record the attempted action and observed result. This gives the team something it can reproduce and discuss. A vague report about the whole website being wrong is less useful than a precise description of the failing step.

9. Publish and check the accessible version

Publication takes place when acceptance conditions are met. It should be organised with the people responsible for access and follow-up. A date alone does not replace the launch decision.

After publication, check essential journeys on the version visitors can actually use. Confirm enquiry delivery, access to principal pages and content coherence. If the project replaces an existing website, check the transition points agreed in scope too.

Name a contact for early reports. Each report should describe what was attempted and what happened, allowing a precise response. Keep the team aware of which observations require immediate correction and which belong in a later improvement discussion.

10. Hand over and organise improvements

Delivery includes the agreed operating materials: access, documentation and training. Let the person responsible practise routine tasks. A guide will be more useful if it corresponds to those operations.

Then build an improvement list linked to objectives, rather than a catalogue of effects to add. New customer questions and changes to your offer will help select priorities. Each proposed addition should say which need it addresses and who will keep the resulting content current.

To prepare a website with MV Design, start with intended uses and available resources. That provides a basis for defining useful, clearly documented stages and the decisions to make together, from the initial brief through handover.