A redesign is usually an investment, not just a cost. You do it to improve conversions, search visibility, or reduce maintenance. This article breaks down where costs come from, gives realistic ranges and a method to estimate payback time.
I include concrete ranges, a worked example and a checklist. There are assumptions — this won’t match every project exactly — but it should give you a practical baseline.
What does a redesign cost? Cost items
A redesign is made of multiple workstreams. You don’t pay one single fee, you pay per activity. Main items:
- Discovery & strategy: audits, analytics, stakeholder sessions. (€1,000–€6,000)
- UX/UI design: wireframes, high-fidelity screens, a design system. (€3,000–€20,000)
- Front-end development: responsive HTML/CSS/JS and performance work. (€3,000–€25,000)
- Backend & CMS migration: change or upgrade CMS, data migration, integrations. (€2,000–€30,000)
- Content & SEO migration: rewrite, redirects, metadata, technical SEO. (€1,000–€8,000)
- Testing & QA: cross-browser, accessibility, device testing. (€500–€5,000)
- Hosting & scaling: setup, CDN, SSL, security hardening. (one-off €100–€2,000, then monthly)
- Maintenance & support: updates, SLA, monitoring. (monthly €100–€1,000)
All figures are indicative and vary per project. A simple brochure site often ranges €6,000–€15,000. Mid-market sites with integrations are commonly €15,000–€40,000. Complex webapps or large e‑commerce projects can easily exceed €40,000.
Quick comparison table: scope vs cost vs timeline
Small site (info)
- Indicative price
- €6,000–€15,000
- Timeline (workdays)
- 15–40
- Typical time to live
- 2–8 weeks
SME site with CMS
- Indicative price
- €15,000–€40,000
- Timeline (workdays)
- 30–80
- Typical time to live
- 6–16 weeks
Complex site / webapp
- Indicative price
- €40,000–€100,000+
- Timeline (workdays)
- 60–200+
- Typical time to live
- 3–9 months
| Scope | Indicative price | Timeline (workdays) | Typical time to live |
|---|---|---|---|
| Small site (info) | €6,000–€15,000 | 15–40 | 2–8 weeks |
| SME site with CMS | €15,000–€40,000 | 30–80 | 6–16 weeks |
| Complex site / webapp | €40,000–€100,000+ | 60–200+ | 3–9 months |
Timelines are from discovery to launch. Iterations, content delivery and external integrations extend them.
How do you get the investment back? (and when)
Payback comes from several channels:
- Higher conversion rates: small percentage increases can mean large revenue gains.
- Lower maintenance costs: cleaner code and better hosting reduce support hours.
- Less churn: better UX reduces cancellations for subscriptions.
- More organic traffic: technical SEO and improved speed help long-term visibility.
Important: SEO gains take time. Improvements in search rankings often take months to stabilize. Google’s guidance on timing is useful: see How long until I see results in Search?. Also follow the technical recommendations in the SEO Starter Guide.
Performance improvements tied to Core Web Vitals can have more immediate effects on engagement and conversion. Prioritise metrics like Largest Contentful Paint (LCP) when you plan workstreams: Core Web Vitals and Largest Contentful Paint (LCP) explain why.
Simple ROI example (conservative)
Assume:
- Current traffic: 10,000 visitors/month
- Conversion rate: 1.0% (100 conversions)
- Average value per conversion: €100
- Monthly revenue: €10,000
If redesign raises conversion to 1.3% (130 conversions → €13,000), extra monthly revenue is €3,000. With a €30,000 redesign cost, payback is 10 months. This is illustrative; your mileage will vary.
Signs that delaying is more expensive
Delaying a redesign sometimes makes sense. Other times it costs you more. Watch for:
- High mobile bounce and low mobile session duration — Google uses mobile-first indexing, so mobile experience matters.
- Falling conversions while traffic is steady.
- Rising support tickets from outdated code or plugins.
- Drops in organic traffic after search updates.
- Slow pages: bad LCP or failing Core Web Vitals metrics.
- CMS limitations that block growth (complex integrations, poor content workflows).
If you see one or more of these, postponing can lead to lost revenue or higher future costs.
Decision checklist
- Do a technical audit (performance, SEO, security).
- Record baseline KPIs: traffic, conversion, LCP, bounce, uptime.
- Prioritise goals: conversion, SEO, maintenance, brand.
- Plan a staged release and redirects to protect SEO.
- Budget for content and SEO migration work.
- Choose a provider who combines design and technical skills.
- Agree a clear SLA for post-launch support.
Practical tips
- Start with an MVP phase if budget is limited. Focusing on conversion and speed usually gives the fastest payback.
- Build responsive from day one; use recommended patterns from Responsive web design basics.
- Don’t skip accessibility — remediation later is often more expensive.
If you want a tailored estimate, check our scope details on website redesign and request a detailed quote. DevCru is a senior-led web and app development agency from the Netherlands. We build bespoke websites, webshops and apps and provide maintenance and support. No vague promises — practical advice and clear numbers.
Sources
- SEO Starter Guide — https://developers.google.com/search/docs/fundamentals/seo-starter-guide
- How long until I see results in Search? — https://developers.google.com/search/docs/monitor-debug/search-console-start
- Core Web Vitals — https://web.dev/articles/vitals
- Responsive web design basics — https://web.dev/articles/responsive-web-design-basics
Sources
Every figure and guideline in this article can be checked in the sources below.
- SEO Starter Guide — Google Search Central
- How long until I see results in Search? — Google Search Central
- Core Web Vitals — web.dev (Google)
- Responsive web design basics — web.dev (Google)
Got a project in mind?
Tell us briefly what you want to build. You get an honest read on scope, price and timeline within one business day.
Request a quoteRelated services
Continue on the page that matches this topic.
Keep reading
Other articles that pair well with this one.

