Cost Of New Website Design | How Much Should I Spend?

A useful website budget starts with the work the business needs, not a price per page. Five pages can involve substantial research, writing and integration; fifty pages can share a small set of well-planned layouts. To decide what to spend, make those differences visible.

Two quotes for a “business website” may describe entirely different projects. One supplier might expect finished copy, approved branding and a ready-to-use template. Another might include discovery, content structure, visual design, development and launch support. Comparing only the totals tells you very little about the value of either offer.

This guide explains how to build a practical budget and compare proposals. It uses an illustrative calculation rather than presenting unverified market averages as a price list. The aim is to help you identify what belongs in the first release, what creates extra work and what the business will continue paying for after launch.

Start with the role of the website

Identify the decisions a visitor needs to make and the action you want to support. A local specialist may need to explain services and receive suitable enquiries. A retailer needs customers to find products, understand options and complete an order. An established company may need several audiences to find different information without competing for attention.

Describe the problem with the current experience if there is one. Perhaps staff receive enquiries for work you do not offer, prospective clients cannot find relevant projects or product information is difficult to update. Those observations help prioritise the brief. “Make it modern” alone does not tell a supplier what needs to improve.

For a focused brochure site, budget for the essential content and a dependable route to contact. Basic on-page SEO optimisation should have a defined scope, such as useful page titles, clear headings, internal links and appropriate indexing settings. Ask which tasks are included rather than assuming a general SEO label covers research and ongoing marketing.

A conversion-focused website may require more work on audience needs, evidence and the sequence of information. A firm offering bookkeeping support, for example, may need to explain which businesses it serves, what is included and how the relationship begins. A short enquiry form is only the final step in that explanation.

Planning for growth can reduce the need for an early redesign, but it does not mean building every future feature now. Identify likely changes that affect the architecture, such as adding case studies or another service category. Give those a sensible foundation and leave speculative features for a later decision.

Different website types create different kinds of work

An online store introduces a catalogue, product options, payments, shipping and order-related communication. A small catalogue with complex variants can demand more planning than a larger collection of straightforward products. Confirm who prepares product data and who tests the complete purchase journey, including errors and cancellations.

After launch, conversion rate optimisation can help investigate where customers encounter friction. Keep that work separate from the initial build estimate unless the proposal explicitly includes it. A store needs relevant traffic, reliable operations and suitable products as well as a clear interface; redesign alone cannot guarantee additional sales.

A larger marketing site may involve several content types, languages, integrations or approval roles. These requirements affect the CMS and the editing process, not just the visible page count. Describe the actual use cases so the supplier can identify dependencies before committing to a fixed scope.

A highly expressive design can also add implementation and testing work. Ask which interactions help explain the offer or improve navigation. A custom animation may be justified, but it should have a purpose the business understands. Complexity added solely to impress during a presentation can become a maintenance burden later.

Decide what needs to be bespoke

A bespoke approach plans the design around your content and audience. It can be useful when an existing layout makes important information difficult to communicate or when the business has unusual requirements. The brief should connect those decisions to specific business problems rather than treating uniqueness as an outcome in itself.

A template can be appropriate when its structure fits the task. It still needs real content, visual adaptation, configuration and testing. The relevant comparison is the work needed to reach a good result, not a simple assumption that every template is cheap or every bespoke site performs better.

Ask to test a representative page with your longest heading, ordinary imagery and realistic body copy. This reveals whether the proposed route accommodates the content. It also makes the discussion more concrete: a supplier can explain a layout change, rather than promise vaguely that the template will be “fully customised”.

Even a bespoke website should use reusable components where they improve consistency. A shared navigation, coherent service-page structure and repeatable case-study layout can reduce future work. Custom design does not require inventing every element from scratch or abandoning a platform's established capabilities.

The seven areas to include in the estimate

1. Discovery and structure

Allow for understanding the business, identifying audiences and planning the pages. An agreed sitemap is useful, but each page also needs a purpose. Distinguish unique layouts from pages that share a structure, and establish the important journeys between them. This prevents page count from becoming the only measure of scope.

2. Copy and visual assets

Decide who writes the copy, prepares product information and supplies photography. Existing material may need editing rather than a direct transfer. If the business is changing its positioning or services, resolve those decisions early enough for the design to reflect them. Repeated late changes create work across several stages.

3. Visual design and development

Specify the design work and the implementation separately. Development from approved files is different from creating the structure and visual direction first. Ask how mobile layouts, long content and optional fields are handled, and whether the price includes population of the actual pages or only reusable templates.

4. CMS and integrations

List the content types editors will manage and the systems the site must connect to. A simple enquiry email differs from a form that creates a CRM record, assigns an owner and sends a tailored response. Include access to documentation and test accounts in the plan so integration assumptions can be checked.

5. Search, performance and measurement

Page speed improvements should address identified causes, such as oversized assets or unnecessary scripts, with an agreed way to assess the result. Search work may involve content, metadata, internal linking and migration checks. Define the deliverables and avoid paying for an undefined promise to “optimise everything”.

If monitoring AI search is relevant, tools such as SE Visible provide a separate visibility-reporting service. Establish the question you want that reporting to answer and who will act on it. A subscription does not replace useful content or fix a broken website, and it need not be part of every launch budget.

6. Testing and launch

Include time to check the implemented site with real content. Important journeys should work across representative screen sizes and input methods. Forms need confirmed delivery, not just a success message. For a redesign, account for existing URLs, necessary redirects, analytics and connected services that must continue working.

7. Handover and ongoing responsibilities

Ask for a demonstration of routine editing and a record of account ownership. Establish who handles faults, renewals and future requests. A general offer of support needs an actual scope, availability and charging arrangement. The business should know what happens after any initial defect-resolution period ends.

Build a first-year budget, not only a launch budget

Separate one-off project work from recurring services. Domain registration, platform subscriptions, application licences and agreed maintenance can follow different billing schedules. Check renewal charges and account ownership as well as introductory offers. Some hosted platforms include infrastructure within a subscription, while other arrangements require separate services.

Here is a hypothetical planning example for a modest service website. It demonstrates the calculation only; these figures are not a market average or a Fit Design quotation. Replace every allowance with the scope and charges in your actual proposal before making a decision.

The £6,380 total combines £4,800 of project and content work with £1,580 of recurring allowances. It excludes paid advertising, additional applications and unplanned work. A different operating model might not need a monthly support arrangement, but someone would still need to own routine checks and arrange help when necessary.

Ask what would change the estimate. A new language, additional integration or missing content may have a different effect from adding another page using an existing layout. A useful proposal explains its assumptions and the process for approving extra work, so the budget does not depend on discovering exclusions halfway through the project.

Compare suppliers through the work they will deliver

A web design agency may coordinate several disciplines, while a freelancer may provide a direct relationship with a particular specialist. Neither structure establishes quality on its own. Ask who will perform the work, which parts they handle personally and where other contributors are involved.

Startups with very limited budgets can benefit from a narrow first release with prepared content and limited functionality. That does not mean they must accept unreliable forms or unreadable mobile pages. Reduce optional scope before removing the work needed to make the essential experience dependable.

Send shortlisted suppliers the same brief and compare inclusions line by line. Look at unique layouts, content responsibilities, migration, integrations, revisions, testing and handover. If one price is much lower, ask what accounts for the difference. It may reflect an efficient approach, a narrower service or an assumption that your team will supply more.

Review relevant live work and ask what the supplier contributed. A site can involve separate branding, content, design and development teams. Understanding the role behind the portfolio example is more useful than assuming every capability is included in every proposal.

Check how acceptance is defined before signing. A proposal might include two design revision rounds but say little about correcting implementation defects. Ask how an agreed layout, a functional requirement and a later change request are distinguished. This helps avoid using a creative revision allowance to negotiate whether a broken form should work.

Also clarify what happens if your content is delayed. The team may need to reschedule development or reserve another review window. Conversely, a supplier should explain how it handles its own delays and communicates changes to the plan. Understanding these dependencies makes the price and timeline more credible without pretending that every project follows an identical schedule.

Judge value without promising a return

A website can support commercial goals, but its financial contribution depends on more than design. Demand, offer, pricing, traffic quality and the sales process all affect the result. Avoid justifying a large project through an assumed conversion increase that has no supporting evidence.

Use a scenario to understand the relationship between investment and benefit. Suppose the business estimates that each additional completed sale contributes £500 after the relevant variable costs. Recovering the illustrative £6,380 outlay would then require thirteen additional sales at that contribution level. This is arithmetic, not a forecast that a redesigned website will generate those sales.

Some improvements have a different value: less manual administration, clearer editing or fewer avoidable enquiries. Record the current problem and decide what evidence would show progress. If staff spend time correcting catalogue information, measure that work before and after the change rather than relying only on visitor numbers.

Keep the first release focused

Separate essential launch requirements from useful future ideas. A service business may need convincing pages, relevant proof and dependable enquiry handling before an interactive quotation tool. An online store may need a clear catalogue and reliable fulfilment information before a complex personalisation feature.

Discuss future needs when they affect foundational decisions. A planned case-study library may influence the CMS now, even if only a few entries are ready. The aim is to avoid obvious rework while resisting speculative development. A phased plan should explain what is deferred and what would trigger the next investment.

Consolidate feedback from people authorised to make decisions. Conflicting late comments can consume a revision allowance without improving the site. Keep a record of approved content and design decisions, and ask for the cost and timing implications before changing them.

What to send with a request for a quote

A useful brief includes the current website, intended audience, essential pages, required functionality and the problems to solve. State what copy, imagery and branding already exist, which systems must connect and who will approve the work. Add any firm deadline and explain why it matters.

When discussing a project with Fit Design, bring those inputs and a realistic budget range. They make it possible to discuss an appropriate route and identify what can be phased. The right investment is the one that funds a clear, maintainable solution to the business's actual needs, with responsibilities understood from planning through to life after launch.