- Inventory before replacing
- Separate design from migration
- Define acceptance and handoff
| Source measure | Published figure | Interpretation |
|---|---|---|
| Most reviewed projects | Less than $10,000 | Not a guaranteed project band |
| Mean reviewed project | $38,105.39 | Different from the typical project |
| Typical agency hourly band | $100 to $149 | Hours and deliverables still required |
What do published web design prices actually tell you?
Clutch's web design pricing guide, updated September 21, 2026, reports that most reviewed projects cost less than $10,000 and gives a mean project cost of $38,105.39. It also lists a typical agency hourly band of $100 to $149. These describe its web design review data, not a redesign-only survey or a Dappr quote.
The difference between most projects and the mean is important: a mean can be pulled upward by expensive projects. Neither number identifies what a particular replacement website should cost. The source includes different project sizes and services, so use it as broad market context while comparing actual deliverables.
An hourly rate alone also leaves the quantity of work unknown. Ask for the discovery assumptions, estimated effort, and approval process behind a quote. A lower rate attached to an uncertain scope can be less predictable than a clearly bounded project with a higher rate.
Separate the reason for redesign from the proposed treatment
Write the business problem in observable terms. Customers may struggle to identify the right service, staff may be unable to update important information, or a critical inquiry journey may fail on small screens. Each problem calls for different work. Replacing the whole site is one possible response, not proof that every existing element is defective.
Collect examples before requesting a price: a confusing page, an outdated product entry, a recorded form error without personal details, or a publishing task that requires developer assistance. The provider can then assess whether targeted changes, a design refresh, a platform migration, or a full rebuild fits the situation.
Define the decision criteria as well as the symptoms. If the goal is easier staff editing, acceptance should include a staff member completing the relevant update. A beautiful demonstration does not establish that the business can operate the replacement without additional ongoing help.
Inventory the site you already own
List live URLs, page types, downloads, images, forms, search features, and external services. Identify which accounts the business controls and which depend on a previous provider. Separate accurate material worth preserving from content needing review. Missing source files or unclear media rights can create work that a page-count estimate overlooks.
Look at meaningful journeys rather than treating every page as equal. A technical specification download, a product selector, and a general contact page have different requirements. Record where each journey begins, what information it needs, and what a successful completion looks like. Include return visitors seeking support, not only new sales prospects.
A content inventory should assign a disposition: retain, revise, combine with a justified destination, or remove after review. Do not let a new navigation mockup silently decide the fate of useful old information. The business owner should approve consequential content changes before migration work begins.
Why templates and page counts are different cost drivers
A site with sixty products may reuse one product layout but still require sixty accurate records and image checks. A smaller site can require several unique interfaces, such as a configurator, searchable resource library, and multi-step inquiry. Ask for both the number of page records and the number of distinct layouts or interactive features.
Clarify whether content writing, photography selection, image preparation, and data cleanup are included. Supplied content is not necessarily publication-ready content. The quote should identify the expected input format, who checks factual accuracy, and what happens when the materials arrive incomplete.
Agree how design revisions work. A round should have a defined review window and a consolidated response from authorized stakeholders. Repeated contradictory feedback consumes time without necessarily improving the result. Naming one content approver and one design decision-maker can make the estimate more credible.
Budget for URL preservation and migration
Google's site-move guidance explains that changed URLs need deliberate mapping and that many old pages should not be redirected to one irrelevant destination. Preserve useful URLs where practical; where they change, define an appropriate destination and test the redirect. This is a migration responsibility, not something established by visual similarity.
Include internal links, metadata, canonical signals, sitemaps, and access settings in the transition checklist. A staging environment intended to stay private has different needs from the public release. Someone must verify that launch does not accidentally retain a blocking setting or expose an unfinished alternate copy.
No provider can promise that a redesign will preserve every ranking or produce an immediate increase. Search systems must process changes, and content changes can alter relevance. Agree on baseline records, monitoring responsibility, and a response process for unexpected problems rather than relying on a broad assurance that SEO is included.
Price the operating connections, not only the visible screens
A form may need to deliver an inquiry, show a clear confirmation, handle invalid input, and provide a fallback when delivery fails. A booking link may be managed by a separate vendor. Document what the website actually controls and what must be verified with the external service owner.
Test the real destination of approved test submissions without including customer data. A button click is not proof that a useful request reached the right team. W3C's forms guidance also supports clear labels, instructions, validation, and understandable feedback; accessibility review should examine the whole interaction.
Changes to account ownership, email delivery, analytics, payment services, or other connections require explicit scope. Do not assume a redesign fee includes replacing every surrounding system. Conversely, do not exclude a critical connection simply because it sits behind the page visitors see.
A fictional redesign estimate for a parts distributor
Imagine a fictional parts distributor with forty product pages, twelve technical PDFs, six service pages, and an inquiry form. The owner wants clearer product compatibility information and easier staff editing. The existing product facts are reliable, but the PDFs use inconsistent names and several inquiry links are outdated.
A useful proposal separates information architecture, two reusable page layouts, product-data preparation, PDF labeling, form delivery, URL mapping, and staff training. It also identifies who approves compatibility claims. This makes the substantial content and operating work visible alongside the design effort.
The distributor might defer a custom product configurator while retaining a clear compatibility inquiry. That reduces the initial scope through a specific product decision. It is more useful than applying an arbitrary discount while keeping the same feature promises. The example is original planning analysis, not a real Dappr client or price estimate.
Define launch acceptance and recovery before launch day
Acceptance should cover the agreed devices, navigation, key pages, forms, error states, and editing tasks. Include keyboard use and motion preferences where relevant. Define what evidence is captured and who signs off. Automated checks can identify some defects, but they do not establish that customers understand the content or can complete every task.
Assign responsibility for backups, release timing, domain or hosting changes if separately authorized, and recovery if a critical issue appears. A recovery plan must identify what is restored and who can perform the action. The old site may not remain a safe fallback indefinitely if content or connected systems have changed.
Specify the post-launch observation period and distinguish defects covered by the project from newly requested features. A clear handoff includes account access, operating instructions, and a known support route. These items belong in the comparison even when they are less visually impressive than the home page.
Compare the first year and prepare an accurate brief
Alongside project fees, list hosting, subscriptions, licensed assets, ongoing support, and expected content work. Note which charges recur and which are optional. A low initial quote can exclude operating costs, while a larger proposal may include services the business does not actually need.
Bring Dappr the existing URL, reasons for change, inventory, known integrations, decision-makers, and desired launch constraints. Identify a preferred spending boundary without treating it as proof that all requirements fit. Major redesign work needs its own scope; a marketing plan price should not be represented as a complete rebuild quote.
The strongest budget conversation ends with a documented scope and unresolved assumptions, not a falsely exact number. If essential facts are missing, a bounded discovery step can establish them. Its deliverables should remain useful to the owner regardless of which provider performs the subsequent build.
Questions before you begin
Is a redesign cheaper than a new website?
Sometimes, when useful content, accounts, and layouts can be retained. Existing complexity can also add migration and compatibility work. Compare the actual reuse and preservation requirements rather than assuming the presence of an old site automatically reduces effort. A short inventory usually makes this distinction clearer.
Can I keep the same domain during a redesign?
Often yes, but domain continuity does not guarantee URL continuity or unchanged search performance. Review page paths, hosting, redirects, and account ownership separately. Any domain or hosting changes should be explicitly authorized and planned; they are not implied merely by approving new design work.
Should copywriting be included in the price?
It should be clearly included, excluded, or assigned to an identified owner. Specify which pages need original writing, editing, or factual review. Reusing inaccurate copy to reduce the headline price can leave the business problem unresolved, while rewriting accurate technical information unnecessarily adds review work.
What makes a cheap redesign quote risky?
The issue is unclear scope rather than price alone. Look for missing content transfer, URL mapping, form delivery, accessibility review, account handoff, or operating charges. Ask each provider to mark these responsibilities explicitly so a lower-cost option can be evaluated on what it actually delivers.
How can I reduce redesign cost responsibly?
Reduce or defer named features, preserve accurate reusable assets, prepare organized content, and consolidate stakeholder feedback. Keep critical customer journeys and migration checks in scope. A staged release can be sensible when each stage works independently and the deferred work is documented rather than quietly omitted.