Website design cost depends on what the website needs to do: the layouts it requires, the content available, the functionality involved and the work needed before launch. A useful estimate starts with a defined scope. Counting pages alone leaves too much unanswered.
If you are preparing a new business website, the first decision is which customer journey matters most. A visitor might need to understand your services, compare products, explore your work or send a project enquiry. That journey should guide the design brief and the work you commission.
Why can websites with the same number of pages require different budgets?
Consider two illustrative projects. One uses a shared layout for several service pages, with approved copy and images supplied. Another needs a different structure for every service, new content, multiple languages and a connection to a customer management system. Their page counts may match, but their design, development and testing requirements do not.
Ask how many distinct page layouts are needed, which components can be reused and what visitors must be able to accomplish. A product configurator, searchable catalogue or booking flow deserves its own scope rather than being treated as just another page.
Which decisions affect website design cost?
- Visual direction: adapting an established identity involves different work from developing a new website design language. Clarify the expected layouts, mobile behaviour and interactions.
- Content readiness: approved text and usable imagery help define the pages. Copywriting, image production, editing and content migration should be identified separately.
- Functionality: describe each form, integration and customer action. Include confirmation messages, error handling and what happens to the information after submission.
- Languages: translated text needs space in the design, working navigation and checks across different screens. Agree who supplies and reviews each language.
- Existing website constraints: preserving useful content, mapping changed addresses and working around an existing system adds tasks that a new build may not have.
- Review and launch: identify decision-makers, revision stages, testing responsibilities and the conditions for going live.
What should a website proposal make clear?
A useful proposal defines deliverables and boundaries. Look for a page or template list, content responsibilities, the platform, required functionality, review stages and launch support. It should also explain what you will be able to edit after handover.
Check ownership and ongoing dependencies: domain access, hosting, software licences, images and any paid services used by the website. Ask which costs recur, who manages renewals and what support is included after launch. These details help you compare proposals covering the same work.
Website design, ongoing maintenance and search visibility work may overlap, but each needs an explicit scope. A website build should state its search foundations; continuing content creation or search optimisation should not be assumed to be included indefinitely.
How can you keep the initial scope focused?
Separate what visitors need on day one from improvements that can follow. For an enquiry-led business, that may mean prioritising clear service pages, relevant work, a useful contact form and a reliable mobile experience.
A later phase could introduce a complex calculator or an extensive resource library once there is a clear reason for it. Keep the essential enquiry journey complete: postponing an optional feature should not leave visitors without enough information to contact you.
For an existing site, start with a website redesign checklist to identify what to retain before commissioning replacement work.
What should you send before discussing your project?
- Your current website address, if you have one.
- What the business offers and which customers the website should reach.
- The main action you want visitors to take.
- The pages, languages and functions you already know you need.
- Examples you like, with a short explanation of the design or experience you find useful.
- Available copy and imagery, plus any fixed launch date and its reason.
You do not need a finished technical specification. A short description of the business and the problem you want to solve is enough to begin a useful conversation. Uncertain items can be identified as questions rather than guessed requirements.
Common questions about planning a website
Can we start without final website copy?
Yes, but content ownership and review milestones should be agreed early. Approximate content can support initial planning; final layouts need realistic headings, text lengths and images so the design can be tested properly.
Is a redesign always a smaller project than a new website?
No. The existing platform, content quality and features determine what can be reused. Reviewing the current site first makes it easier to distinguish a focused improvement from a rebuild.
Should maintenance be included in the discussion?
Yes. Agree who will handle updates, renewals and technical issues after launch. Our website maintenance guide explains the questions to ask.
Tell us what your website needs to achieve
Fovoya designs and builds business websites around their content, visual direction and customer journeys. Share your current website or describe your idea, and we can discuss a suitable project scope.
Discuss your website with Fovoya · Explore website design and development
