0

Back to Catalogue

Table of Contents

How much does website design cost in 2026?

What published prices cover and what to check before accepting a website-design quote.

3 min read
post image

Website design cost depends on what you’re asking the team to deliver. Clutch and WebFX publish 2026 price references, but they cover different samples and packages of work, so neither gives you a universal average to apply to your project. For a useful estimate, you’ll need to agree on what’s included, who supplies the inputs, and how changes will be priced.

Have two proposals open and no clear idea why the totals are so different? Start with what each one includes. The references and worksheet below give you a way to compare them.

The short answer: a market benchmark is not your estimate

Two proposals can list the same number of pages and still cover different work. One might include individual layouts while the other reuses templates. A small-looking distinction on paper, but one you need to clear up before comparing totals.

If you already have approved copy, a sitemap, and a developer ready to build, you can ask a designer to price the layouts and handoff. If you also need help deciding what the site should say or moving content from the old site, put those tasks in the proposal too. Otherwise, you may get to the work and find that neither team has budgeted for it.

Read the proposal with those responsibilities in mind. Can you identify each of the following?

  • the deliverables being priced;
  • the work the client must supply;
  • dependencies that can delay or change the work;
  • exclusions that would require another estimate;
  • the rules for reviews, new requirements, and handoff.

If something is missing, ask about it while you’re still agreeing on the scope.

Current website design cost benchmarks and what they measure

Published ranges give you somewhere to start when a quote arrives. Before using them to judge it, though, check what went into the figures. Clutch and WebFX describe different samples, as the table shows.

ReferencePublished valueWhat it coversMethod or sampleCurrency and geographyCheckedWhat not to infer
Clutch web design pricing guide$2,000–$100,000 for web-design-company projects; around $100–$149/hour for shortlisted companiesProjects and providers represented in Clutch's web design marketplaceClutch says its pricing draws on its agency database and first-party client reviews; page updated September 21, 2026USD; geography for the overall project range was not stated in the saved evidenceSeptember 28, 2026This is not a universal agency range, a Merge rate, or an estimate for your project
WebFX web design pricing guide$1,000–$30,000+Reported business spending on web designProvider-published survey of 250 U.S.-based marketing professionalsUSD; United StatesSeptember 28, 2026This is not independent market consensus or a quote for a defined scope

The Clutch figures describe activity in a services marketplace and include both project and hourly references. The WebFX figure comes from respondents reporting web design spending. Because the population, unit of measurement, and project boundaries differ, averaging the two would create a number that neither source reported.

That’s why a published range can leave you with quite a bit of room. To judge your own quote, you need to look at the work the team will actually deliver.

How the type of website changes the work

“It's a small website” is a useful start, but what will people do there? A brochure site and a small online store can have similar page counts while asking quite different things of the designer.

Use these examples to describe your project before requesting a price. They are scope prompts, not fixed packages or price bands.

Website typeWork to discuss in the estimateDetail worth checking
Brochure or service-business siteService pages, contact details, an inquiry route, and reusable layoutsIs the copy ready, and can the services share a template?
Content-led business siteArticle and resource templates, categories, search, and the editing workflowWho will organize and migrate existing content?
Ecommerce storeProduct browsing, product details, cart, checkout, and account states where neededWhich parts use the platform's existing checkout, and which need custom design?
SaaS marketing siteProduct explanations, pricing, feature pages, and a demo or trial entry pointAre you also asking for product graphics, motion, or interactive demonstrations?
Corporate or multilingual siteNavigation across audiences, language versions, and reusable content structuresWho approves each version, and what must the CMS let local teams change?

The label helps you describe the project. The answers in the last column help a supplier understand the work behind it.

What changes a website-design estimate

Go through the proposal with the supplier and ask who will do each part of the work. Whenever the answer is “your team,” make sure someone on your side has time to do it. An assigned responsibility still needs an available person.

Starting condition, content, and information architecture

Start with what you’ll have on day one. For a new site, that may look quite different from a project that needs to preserve parts of an existing one. Check whether the messaging is approved and a page inventory exists. Then name who will decide the navigation, write the copy, gather assets, and approve the final content.

Count the unique templates or page types as well as the total pages. A group of case studies could share one layout, while a pricing page and a product tour could each need a separate design. Your proposal should make it clear which layouts the team will design individually and which pages will reuse the system.

If you’re working with an existing site, agree on who will inventory the content, map old URLs, prepare migration files, and approve redirects. Calling the project a redesign doesn’t assign those tasks to anyone.

Agentless layouts: a resource hub and an article page illustrate why a page inventory should identify different template types.
Agentless layouts: a resource hub and an article page illustrate why a page inventory should identify different template types.

Brand, interaction, and responsive requirements

With the content accounted for, look at your visual starting point. Can the designer use your existing brand guidelines, or do you need a new direction? Spell out whether you’re asking for a moodboard, custom illustration, iconography, graphics, or wider art direction, and confirm who supplies the source assets and licenses.

List the interactions the designer needs to work through. Identify animations, menus, forms, filters, carousels, calculators, or product demonstrations that require designed states. If the final deliverable is a static design file, specify how the intended behavior will be documented for developers.

Picture the page on a narrow screen, with the menu open and a heading that runs longer than expected. Those states need design attention too. Ask which viewports or device classes are covered, along with validation errors, empty results, and logged-in views. If accessibility or browser support matters to the project, write the acceptance criteria into the scope. You need to know what everyone has agreed to check.

VersusTrade interface examples. Account screens and their states need their own scope; a marketing-site page count does not describe that work.
VersusTrade interface examples. Account screens and their states need their own scope; a marketing-site page count does not describe that work.

CMS, integrations, build responsibility, and launch risk

Does the quoted work end when you receive the design files, or does it continue through the build? Agree on who selects and configures the CMS. If another team is building the site, check what they need from the designer before you accept the handoff.

List the systems the website must work with: forms, CRM, analytics, localization, search, user accounts, payment flows, product data, or another internal source. For each one, ask whether the designer is defining the interface, whether a developer is implementing it, and who provides access, documentation, test data, and approval.

Agree who prepares the staging site, where the team can check the build before it goes live. The proposal should assign content preparation and redirect checks, along with testing forms and responsive layouts. Define acceptance testing: who checks the site against the agreed requirements, who fixes defects, and who signs off on launch. A supplier may exclude some of this work, but someone still needs to own it.

Review rounds, change handling, and ownership

Think ahead to the first design review. You’ll need someone who can approve the work and someone to bring the feedback together. Ask the supplier how they treat a correction against the brief, a refinement, and a new requirement. Those may lead to different conversations about the fee.

Ask how review rounds work, what happens if your feedback arrives late, and how scope changes are estimated. “Revisions included” sounds reassuring, but you still need to know which work and which stage it covers.

Before handoff, check what you will receive. Confirm who owns the final files, which editable source files transfer, whether fonts or media need separate licenses, what documentation is included, and whether post-handoff questions or support have a defined boundary.

Compare quotes on the same assumptions

To compare website design pricing, put the proposals side by side and fill in this table. If their documents leave you guessing, ask each supplier to fill in the gaps.

Comparison itemProposal AProposal BQuestion to resolve
Business and site objectiveWhat decision or user action must the site support?
Starting assetsWhich content, brand, analytics, and technical materials are ready?
Pages and unique templatesHow many distinct layouts and states will be designed?
Content and information architectureWho owns copy, sitemap, migration, and approvals?
Brand, graphics, and motionWhich assets and interactions are included, and at what fidelity?
Responsive and accessibility requirementsWhich viewports, states, and acceptance criteria are in scope?
CMS, forms, and integrationsIs the work design-only, configuration, or implementation?
QA and launchWho tests, fixes, redirects, deploys, and signs off?
Review and change handlingHow are review rounds, new requirements, and delays treated?
Handoff, ownership, and ongoing workWhich files, licenses, documentation, and support transfer?
Exclusions and dependenciesWhat could require a separate estimate?

Before comparing totals, normalize the currency, tax treatment, and price basis. Separate one-time work from recurring charges. If one proposal is fixed-price and another is time-based, record the assumptions behind the fixed amount and the controls around the time-based work.

A lower total may exclude more work, or it may be a better commercial offer for the same scope. Use the completed table to see whether the difference comes from scope or price.

Where to simplify when the budget is tight

Start with the pages and tasks the first release needs to support. If a page has no clear job yet, you can ask for it as a later phase rather than have the team design around unfinished requirements.

Reusable layouts are worth discussing, too. A set of service pages may work well with one shared structure, while a product explanation needs more individual attention. Let the content show you where customization is useful. Making every page different gives the designer more work without necessarily giving the reader more help.

You can also separate optional motion or custom illustration from the initial estimate. Ask for the scope with and without those items, then decide what the extra work contributes. Keep the checks needed for the agreed release visible in both versions, including mobile behavior and working forms.

Finally, look at what your team can realistically supply. Approved copy and organized assets can remove tasks from the supplier's scope. If preparing them takes time you don't have, putting “client to supply” in the proposal won't solve the problem.

Build a brief that produces a more useful estimate

You can use the same questions before requesting a quote. Put your answers into a website design brief so each potential partner starts with the same information. You don’t need to settle every design choice; explain what’s ready and where you need help.

Include:

  • Business and audience: what the company offers, who the site serves, and any audience distinctions that affect navigation or content.
  • Website job: the decisions or actions the site should support, plus the signals your team will use to judge whether it works.
  • Current state: the existing URL, platform, known constraints, and the parts that must be retained or reconsidered.
  • Page inventory: expected pages, unique template types, repeated content, and special states.
  • Content readiness: what is approved, what needs editing or creation, who supplies media, and who can approve it.
  • Brand and visual inputs: existing guidelines, references, required assets, and any brand work still open.
  • CMS and implementation owner: who will build the approved designs and who makes platform decisions.
  • Integrations and data: forms, CRM, analytics, search, localization, accounts, payments, or internal systems.
  • Responsive, accessibility, QA, and launch expectations: the required states, acceptance criteria, testing responsibilities, and release owner.
  • Decision process: stakeholders, one accountable approver, review cadence, and any procurement or legal steps.
  • Timing context: fixed external dates, dependencies, and when the client team can provide feedback or materials.
  • Commercial boundary: a preferred engagement model or budget boundary, if you want suppliers to design the scope around one.
  • Handoff and ongoing work: required source files, documentation, ownership, training, and post-launch support.

If you don’t know an answer yet, say so. Ask how the supplier would work it out and whether that work is included. A clear brief gives you something concrete to discuss, although the final price can still change if you agree to change the scope.

Need to compare an agency proposal next?

Once the scope is clear, take a closer look at the team behind the proposal. Who will you work with, and how will you make decisions together during the project? Review these nine questions before comparing B2B web design agencies.

How to read Merge's published pricing examples

As of September 28, 2026, the Website view on Merge's pricing page displayed a $2,100 Design sprint, an On-demand team starting at $3,200 per month, and an Exclusive option based on a tailored proposal.

Each example describes a way to engage Merge; the price of your website still depends on the agreed scope. To understand the cost of website design for a specific project, confirm the page and template scope, content responsibility, design-versus-development boundary, duration or capacity, integrations, exclusions, and change process.

Check the revision terms for the engagement you are considering. Merge's public plan comparison and Website Design FAQ use different revision language. Do not assume that one rule applies to every model; the applicable plan and proposal should state the review and change terms for the work being priced.

FAQ

How much should a small business budget for website design?

Start with the pages and functions you need, then request estimates against that scope. The published benchmarks above provide context, but they do not isolate a comparable small-business project. Ask suppliers to separate design from implementation and identify anything your team must supply. That gives you a budget you can relate to an actual deliverable.

What is the cheapest way to get a professional-looking website?

If an existing template fits your content and you can handle setup, it is worth comparing that route with a custom-design quote. Include your own time and any help you will need to finish the site. Ask what customization is possible before choosing a template; changing its structure extensively may defeat the reason you chose it.

Why might an agency quote more than a freelancer?

Look for differences in scope, staffing, and commercial terms. One proposal may include research and implementation while another covers design files only. Either type of supplier can offer a broader or narrower engagement, so ask who will do the work and what you will receive. The supplier's label is not enough to explain the price.

Does website design pricing include development?

Only if the proposal includes it. A design engagement may end with approved layouts and developer-ready files. A combined engagement may also cover the CMS and implementation. Confirm the boundary, including who checks the built site against the design and resolves issues before launch.

Which costs should I check beyond the initial design fee?

Ask about domain and platform subscriptions, paid assets or plugins, and any ongoing work you want the supplier to handle. Distinguish technical upkeep from new content or design requests. Check which charges are included, which are billed separately, and who owns the relevant accounts; there is no need to assume a fixed percentage of the design fee.

How long does a website design project take?

Ask for a schedule tied to your scope and review process. The supplier needs to know whether the content is ready, how many distinct layouts need approval, and whether development is included. Have them identify dependencies and explain how late inputs or additional review affect the schedule. A delivery date is more useful when you can see what it depends on.

How can I keep the estimate from growing during the project?

Agree on deliverables and acceptance criteria, appoint an approver, and clarify how changes are priced. Ask for the cost and schedule impact before approving additional work. You can still change your mind; you will simply have a clearer view of what that decision adds to the project.

When a scoped website-design conversation is the next step

If you have the page and template inventory, content status, integrations, build responsibility, and decision process, Merge can scope the design work against those inputs. Depending on the agreed project, that work may include visual direction, page designs, mobile adaptations, a UI kit, and interaction notes, with development included or handled by another team.

Discuss a website-design project with Merge.

call to action image

Design packages for your startup

Ideal for early-stage product UIs and websites.

See pricing
author

Co-Founder and CEO of Merge

My mission is to help startups build software, experiment with new features, and bring their product vision to life.

My mission is to help startups build software, experiment with new features, and bring their product vision to life.

You may be interested in

Let’s take this to your inbox

Join our newsletter for expert tips on growth, product design, conversion tactics, and the latest in tech.