Hiring a web designer can feel strangely personal. You are handing someone the business you have built, the ideas in your head and, occasionally, a folder called “final logo new new 3.”
You may know that the current website is no longer working, but not know what the replacement should look like or what information the designer will need.
A good website process should make those decisions feel more manageable. You do not need to arrive with every answer. You do need a clear conversation, realistic expectations and a shared understanding of what is being built.
The best website projects feel collaborative without requiring the client to become the designer.
Step 1: The first conversation
The process normally begins with an enquiry, discovery call or introductory questionnaire.
This is not only about the number of pages. The designer needs to understand the business, the audience, the current challenges and what the new website should help achieve.
You may discuss:
- What the business offers
- Who the ideal client is
- What is and is not working on the current site
- The pages or features you think you need
- Your preferred launch date
- Your available budget
It is completely fine not to know every technical detail. A good designer should help translate the business need into an appropriate website scope.
Step 2: The proposal and scope
After the conversation, you should receive a proposal or quote explaining what is included.
Read this carefully. The most useful proposals are specific about the pages, functionality, revision rounds, responsibilities, timeline and payment terms.
Look for clarity around:
- Website pages and features
- Copywriting or content support
- Image sourcing or photography
- Mobile optimisation
- Basic SEO setup
- Domain and hosting responsibilities
- Revision rounds
- Post-launch support
A proposal protects both sides. It keeps a small project from quietly turning into a much larger one halfway through.
Step 3: Content gathering
This is often the stage that determines whether the project moves smoothly or pauses for several weeks.
The designer may ask for copy, photographs, testimonials, service information, contact details and brand files.
You do not need everything to be perfectly written before the first conversation. But before design begins, there should be enough real content to understand the shape of each page.
Designing without content is a little like tailoring a suit without knowing who will wear it.
How to make this stage easier
- Choose one person to approve content and feedback
- Keep files in one shared folder
- Use clear filenames
- Confirm which version of the logo is current
- Gather testimonials and project examples early
- Be honest when you need help with the writing
Step 4: Strategy and structure
Before the visual design, the website needs a sensible structure.
This may involve planning the navigation, deciding which information belongs on each page and identifying the journey a visitor should take.
A one-page website needs structure just as much as a larger site does. The sections should move naturally from introduction to trust, services and contact.
For a multi-page site, the aim is to make information easy to find without creating unnecessary pages simply to make the website appear larger.
Step 5: The visual design
This is the part most people imagine when they think of website design.
The designer brings together the brand colours, typefaces, photographs, content and page structure to create the visual experience.
Depending on the process, you may see a home-page concept first or receive several key page designs together.
When reviewing a design, try to look beyond whether you personally like every individual detail. Ask:
- Does this feel appropriate for the business?
- Will the ideal client understand the message?
- Is the important information easy to find?
- Does the next step feel clear?
- Does the design reflect the level of service being offered?
Step 6: Feedback and revisions
Feedback is expected. It is part of the process, not a sign that the first design has failed.
The most helpful feedback explains the reason behind the concern.
“I do not like the green” gives the designer very little direction. “The green feels too playful for the financial audience we are trying to reassure” creates a useful conversation.
It also helps to gather feedback into one clear list rather than sending separate messages over several days.
What happens when several people are involved?
Choose one person to collect and consolidate the comments. Contradictory feedback from several decision-makers can slow the project and make it difficult to protect the original strategy.
Step 7: Development
Once the visual direction is approved, the site is built.
This includes creating the pages, adapting the design for different screen sizes, setting up forms and adding the required functionality.
There may be a quiet period during this stage because much of the work happens behind the scenes.
The designer will also test links, spacing, forms and the mobile experience before the website is ready for your review.
Step 8: Your final review
You will normally receive a link to review the working website before launch.
Read the content carefully and test the practical details:
- Are names, numbers and email addresses correct?
- Do all buttons go to the right place?
- Do the forms work?
- Does the website make sense on a phone?
- Are the services and prices current?
- Have you checked spelling and factual details?
This is the best time to catch small errors. It is not usually the ideal time to introduce a completely new page or change the original strategy.
Step 9: Launch day
Launch day is exciting, but it is often less dramatic than people expect.
The website may need to be moved to the live domain, connected to analytics, indexed for search engines and checked again after publication.
There can be a short period while domain or security changes settle. A responsible designer will complete a final round of checks once the site is live.
Step 10: After the launch
A website is not something that should be ignored for the next five years.
Content changes, software needs updates and the business continues to evolve.
Ask what support is included after launch and what future updates will cost. You should also receive the access details or training needed to manage the parts of the site you are expected to update.
What you are responsible for as the client
A collaborative process works best when both sides know their role.
The designer is responsible for guiding the process, solving design problems and building the agreed website. The client is responsible for providing accurate information, timely feedback and decisions.
You do not need to micromanage the design. But disappearing for a month while the designer waits for the service copy will affect the schedule.
What a good process should feel like
You should feel informed, not overwhelmed.
You should understand what happens next, what is expected from you and how decisions are being made.
There may still be moments of uncertainty. Creative work often involves exploring something before it feels completely resolved, but the overall process should remain clear and respectful.
You do not need to arrive with a perfect brief or know the difference between hosting and a domain.
You need to know your business, be open about what you need and choose a designer who can turn that information into a website that feels both useful and true to you.
Planning a new website?
Tell me what you have now, what is changing and what you would like the new site to achieve. I will help you understand the process and the most sensible scope before the project begins.
Start a conversation