WebFX’s redesign pricing table lists $3,000–$10,000 for freelancers and $5,000–$75,000 for agencies. For broader web-design projects, Clutch reports an average of about $38,100, although most reviewed projects cost under $10,000. These benchmarks cover different scopes and do not establish a redesign-only industry average.
On this page6 sections
A website quote only means something when the price is tied to a scope. This guide covers what the published numbers actually measure, so an average doesn't mislead you; where my own planning ranges sit and how I decide where a project lands; and what actually moves a quote.
What the published numbers actually measure
An average, a provider's estimate and a survey bracket are three different kinds of evidence. I checked each of these against the original publisher's page on September 6, 2026.
| Source | Published figure | What it measures |
|---|---|---|
| Clutch web-design pricing | $38,105.39 reported average; most reviewed projects under $10,000 | Broader web-design projects described in client reviews; redesigns are not separated out |
| GoodFirms development survey | 33% quote $1,000–$5,000; 30% quote $5,000–$15,000 | Self-reported estimates from 300+ providers in 31 countries, for web development in general |
| WebFX redesign pricing | Freelancers $3,000–$10,000; agencies $5,000–$75,000 | Redesign estimates published by a provider; no sample size disclosed |
The Clutch numbers show why an average alone can mislead you. A handful of very large projects pulls the average up even when most projects come in far below it. "Most under $10,000" is the more useful fact for most businesses.
How I read these sources
Clutch does not disclose the project sample or the collection window behind its average. GoodFirms reports what providers say they charge, not audited invoices. WebFX is a provider publishing its own view of the market. None of them gives a representative redesign-only average, and none validates any one developer's quote, including mine. I left out annual-spending surveys and older estimates with unclear dates.
Where my own ranges sit
These are my current planning ranges in US dollars. They describe my own work, not an industry average, and the written quote for your project is what actually sets the price.
| Type of work | Planning range | What I need to know before I quote |
|---|---|---|
| Small projects: improvements, new features, optimizations | $1,000–$3,000 | Which pages or capabilities to improve, what the site is built on, and how we'll check the result |
| Websites: new sites and redesigns | $4,000–$10,000 | Content, page types, who edits it, what it connects to, and what has to carry over from the old site |
| Systems: applications and workflows | $8,000–$20,000+ | Records, roles, workflows, integrations, and who runs it after launch |
Most new sites and redesigns I plan land in the middle range. That covers planning, writing, design, development and launch for an agreed set of pages. A small store or a simple customer login can sit inside it when we scope it on purpose.
A website that manages availability, deposits, staff assignments and customer accounts is a different thing. That's a business system with a public face on it. It belongs in the Systems range, and adding a login button doesn't turn it into a small extra.
If your current site has a sound foundation, I'll tell you. Better service pages, a clearer inquiry path or a measured performance pass often fits a Small project. You don't have to buy a rebuild to get a real improvement.
How I scope a website before I quote it
I start with one question: what do customers need to do on this site? An inquiry form and a customer portal might each take up one page, but they are very different amounts of work. The answer to that question puts the project in a range before we talk about anything else.
Then I make the jobs visible. Who gathers the content? Who designs the editing experience? Who connects the inquiry or booking to where it needs to go? Who keeps the old addresses working? Who handles the launch? When each job has an owner, the quote is something you can actually compare.
What actually moves the price
Content, and the decisions behind it
"We have the content" can mean approved copy and usable photos. It can also mean an old site describing services you no longer sell, or information that lives in proposals and the owner's head.
I separate collecting material, deciding the message, writing, editing, preparing images and approving. If the project needs new copy or a fresh set of project stories, I put that in the proposal. I don't leave it for someone to discover halfway through the build.
Page types, not page counts
Ten project pages on one well-designed template are a very different job from ten pages with unrelated layouts. I count the reusable page types: service, project, team member, guide, product, landing page. Then I name the few experiences that deserve individual design, like an interactive comparison or an animation that explains a process. Each one needs a purpose and a performance budget.
Who makes the next change
An owner who updates a service twice a year needs a different editor from a team publishing projects every week. Before I recommend a platform, I want to know who will be making changes and how often. My WordPress versus custom guide walks through how I decide.
What happens after the click
For every important action on the site, I write down what happens next. Does an inquiry become an email, a saved record, a CRM contact, an assignment, or all of those? Does booking happen inside the new site or in a service you already use?
This is where a small-looking website hides real work. I keep that work visible in the quote so you can phase it, compare options, or decide it isn't worth building yet.
Moving from the old site
If you already have a website, the quote should say what happens to its useful addresses and content. Google's site-move guidance calls for mapping old URLs to relevant new pages and testing the redirects, and it warns that visibility can fluctuate during a move. I plan that migration as part of the build. I can't promise your rankings won't move; nobody honestly can. Google's site migration guidance
Launch also includes the domain, hosting, HTTPS, forms, analytics and connected services. Moving a website does not have to mean moving company email, and I check those dependencies before anything changes. My redesign checklist is the sequence I run.
Build the brief before you ask for quotes
I built this planner so you can turn your situation into a short brief. Start with the example, then change it to match your business. It finds the right starting conversation and the open questions. It deliberately does not attach made-up dollar amounts to features.
Build a scope you can discuss
Scope a new website around its first useful job
Name the essential pages, content owner, customer action, and future editor. Add only the capabilities that the first release needs.
- Define the audience, offer, and next customer action
- Assign content writing, editing, and approvals
- Test the editing workflow, accessibility, performance, and launch handoff
Starts with a sample new-website brief. These are Ty’s published planning ranges, not an instant quote or market averages. Choices stay on this page until reload; the download keeps your current brief.
Keep the brief when you compare proposals, mine included. A builder should be able to tell you what's included, which assumptions still need checking, and what belongs in a separate scope.
What you pay for after launch
I keep the project fee and operating costs on separate lines. Domain, hosting, CMS or plugin licenses, mail delivery, booking or commerce subscriptions: each gets a named owner and a named payer.
When a project is hosted with DreamHost, DreamHost provides the hosting and I handle the code, images, caching and third-party behavior that decide what actually happens in a visitor's browser. I'm DreamHost's CMO; the hosting is DreamHost's product and billed separately, and the work described here is my own.
Ongoing website management is a separate monthly service for agreed upkeep, changes and improvements. Its fee depends on the site and the responsibilities, so I quote it after a review.
A good quote connects the price to a scope: what customers can do, what your team can manage, what carries over from the old site, and who owns it after launch. Published benchmarks run from $3,000 to $75,000 depending on who's counting, and most reviewed projects come in under $10,000. The price moves with content, editing needs, integrations and migration, not page count.