# How long does a website (re)design take? *Published: 2026-09-25* *Author: Griffo — Senior Brand & Digital Designer* Realistic website timelines phase by phase, why content readiness is the real delay driver, and what actually shortens a project. From a studio that ships them. # How long does a website (re)design take? For most businesses, a professionally designed and built website takes 8 to 16 weeks from kickoff to launch. A small site with content ready can land in 4 to 6 weeks; larger builds with e-commerce, integrations, or multiple languages run 4 to 6 months. The variable that moves a project between those ends is rarely design or code. It is content readiness: whether the words, images, and data the site needs exist yet. Those numbers come from our own projects, not a survey, so treat them as an experienced estimate rather than a law of physics. The reasoning behind them travels well, though, and it is the reasoning that lets you predict your own timeline. ## What actually takes the time in a website project? A website project is four kinds of work, and only two of them belong to the agency. Discovery and strategy come first: understanding the business, the audience, what the site must achieve, sitemap and page structure. Then design: wireframes, visual direction, page designs, revisions. Then development: building the front end, setting up the CMS, integrations, testing, accessibility, performance. These three are the agency's problem, and a competent studio can schedule them with reasonable confidence because it controls the inputs. The fourth kind of work is everything the site is actually made of: copy for every page, photography, case studies, testimonials, team bios, product descriptions and data, legal pages, translations. This work usually sits with the client, it is invisible in most proposals, and it is where timelines go to die. There is also a fifth ingredient that is not exactly work but behaves like it on the calendar: decisions. Every design presentation needs feedback, every draft needs approval. A project with 6 feedback checkpoints where each takes two days adds under two weeks of calendar. The same project where each checkpoint waits for a monthly leadership meeting adds a quarter. ![40](https://media.secondseason.studio/magnific_recreate-img1_s7ZF9AAl8e-95830a13a65e8433.webp) ## Why is content the real delay driver? Because content is the only major workstream that is simultaneously underestimated, unowned, and on the critical path. Underestimated: writing a website sounds easy until you try it. A 15-page site needs something like 6,000 to 10,000 words of copy that must be accurate, on-brand, and structured for the page designs. That is weeks of work for someone who also has a day job. Nobody budgets for it because it does not look like a deliverable; it looks like typing. Unowned: agencies assume the client brings content, clients assume it is included, and the gap surfaces in week five when development is ready for real copy and there is none. Even when copywriting is in the agency's scope, the raw material (product knowledge, proof points, approvals from subject experts) still has to come from inside the company. On the critical path: design can proceed with placeholder text, and that is precisely the trap. Everything looks on schedule until the placeholders need replacing, at which point real copy turns out to be longer, shorter, or structurally different from what the design assumed, and pages need rework. Sites sit finished-but-empty for months this way. We have watched a build that took 9 weeks wait 11 more for case studies that were "almost done" at kickoff. The site was not late. The content was. This is common enough that we treat content readiness as the first scheduling question, before anything about design preferences. We go deeper on this specific failure mode in [website content delays](/posts/website-content-delays). ## What does a typical timeline look like, phase by phase? Here is the shape of a typical mid-sized business site in our experience, with the honest range and the thing that stretches each phase: - **Phase — Typical duration — What stretches it** - Discovery and strategy — 1 to 3 weeks — Unclear goals, many stakeholders, missing analytics access - Sitemap, wireframes, content outline — 1 to 2 weeks — Debates about what the site is for (a discovery symptom) - Content production — 2 to 8+ weeks, overlapping other phases — Starting late, no owner, expert reviews, legal sign-off - Visual design — 2 to 4 weeks — Slow feedback loops, conflicting stakeholder opinions - Development and CMS setup — 3 to 6 weeks — Integrations, custom features, e-commerce, multilingual - Content entry, QA, accessibility, performance — 1 to 3 weeks — Content arriving late and unstructured - Launch prep, redirects, DNS — A few days to 1 week — Redirect mapping on large sites, freeze windows Sum the middles and you get roughly 10 to 14 weeks, which matches the 8-to-16 answer at the top. Notice that content production is the widest range in the table and the only phase without an upper bound. That is not an accident. ![36](https://media.secondseason.studio/magnific_recreate-img1_N2DlRo06D9-ce436f0baf55bae4.webp) Two structural notes. Phases overlap: content should run parallel to design, not after it. And the stack changes the shape a little: we build with Next.js and a headless CMS, usually Payload, which means content modeling happens early and content entry can start before development finishes. If you are curious what that architecture buys you, [what a headless CMS is](/posts/what-is-a-headless-cms) covers it. ## Does a redesign take longer than building from scratch? Frequently, yes, and buyers are consistently surprised by this. A redesign carries inventory a new build does not. Somebody has to audit what exists: which of your 240 pages earn traffic, which are duplicates, which are legally required, which should die. Somebody has to map every old URL to its new home, because launching a redesign without redirect mapping is how businesses torch years of accumulated search rankings in a weekend. Somebody has to migrate content that was written for a different structure, and most of it will need rewriting rather than pasting. Redesigns also come with incumbent opinions. A new site has no defenders; a redesign has people attached to the current homepage, the current wording, the way the old nav worked. Those conversations are healthy and they take time. The redesign-specific risk that deserves its own planning is SEO continuity, which has its own checklist of crawl audits, redirect testing, and post-launch monitoring. We wrote that up separately in [redesigning without losing SEO](/posts/website-redesign-without-losing-seo). Budget real time for it; it is the least skippable "invisible" work in the whole project. ## Can a website really be done in a week? Yes, and sometimes it should be. A template on a site builder, or an AI builder output, can be live in days. For a pre-launch startup that needs a credible placeholder, a restaurant that needs hours and a menu online, or an experiment you might kill next quarter, a one-week site is the correct engineering decision, and any agency that tells you otherwise is selling. What the one-week site cannot contain is the work that takes the other eleven weeks: positioning decisions, custom design that differentiates you, content developed rather than improvised, integrations with your actual business systems, accessibility and performance engineering. None of that compresses, because most of it is thinking and coordination rather than production. The honest framing is that a fast site and a built site are different products that happen to both be called websites. We compared them properly in [custom website vs template](/posts/custom-website-vs-template). The pattern to avoid is paying for the twelve-week product on a one-week mindset: signing a custom engagement, then being unavailable for decisions and content. That buys you the slower timeline and the template-level outcome at once. ## What do we see in real projects? After enough launches, you can predict a project's timeline in the kickoff call from two signals, and neither is the size of the site. Signal one: does the content exist? We now ask to see draft copy, real product data, and actual photography before we schedule development. Not final, just real. When a client says "the content is basically ready," we have learned that this means somewhere between 20 and 80 percent ready, and the spread is the whole scheduling problem. One manufacturing client came to us with every product spec sheet complete and a founder who wrote fast; that 60-page site launched in under ten weeks. A ten-page site for a services firm took nearly five months, and every added month was waiting for bios, case studies, and a partner who wanted to rewrite the homepage a fourth time. Same studio, same process. The difference was entirely on the content side. Signal two: who says yes? Projects with one empowered decision-maker move at double the pace of projects where every design goes to a five-person committee. Feedback rounds are the hidden multiplier: three rounds at two days each is a week; three rounds at two weeks each is six weeks, on the identical amount of actual work. Our standing recommendations, which cost nothing and reliably save a month: appoint one content owner with real hours allocated, start content the same week as discovery, agree feedback turnaround times in the contract (we ask for 3 business days), and lock scope before development starts. We would rather push a kickoff by three weeks so content can catch up than start on time and stall in the middle. A late start beats a long pause every time, because momentum is a real force in projects and restarts are expensive. ## How can you tell what your project will take? Skip the generic calculator and answer four questions honestly: 1. Is your content written, or does it exist only as "we know our business"? Unwritten content adds 4 to 8 weeks, running in parallel if you start now, in series if you do not. 2. Can one person approve design within a few days? If approvals go through a committee or a board rhythm, add the gaps between meetings to the calendar. 3. Does the site need to talk to other systems (CRM, e-commerce, booking, ERP)? Each real integration adds development and testing time, and discovery for it should happen before the quote, not after. 4. Is this a redesign of a large site? Add audit and redirect work proportional to the page count. Ready content, fast decisions, no integrations, modest size: you are at the fast end, 4 to 8 weeks. Two or more of the opposite answers and you are realistically at 4 months plus, whatever any proposal says. The good news is that the levers are mostly yours to pull, and pulling them costs far less than the delay does. ![25](https://media.secondseason.studio/magnific_recreate-img1_JNW14UMOq4-2f39e19e4fc5ec05.webp) ## FAQ ### How long does a website redesign take? For most businesses, 8 to 16 weeks from kickoff to launch. A small marketing site with ready content can ship in 4 to 6 weeks. Larger sites with e-commerce, integrations, or multiple languages run 4 to 6 months. In our experience the biggest variable is not design or development but how ready the content is. ### What delays website projects the most? Content. Design and development phases are predictable because the agency controls them. Copy, imagery, case studies, product data, and legal pages come from the client side, and they are routinely underestimated. A close second is decision speed: each feedback round that takes two weeks instead of two days adds directly to the calendar. ### Can a website be built in a week? Yes, with a template or an AI builder, and for some situations that is the right call. What you get in a week is a generic structure with your words poured in. What you cannot get in a week is strategy, custom design, content development, or integration work, because those depend on thinking and coordination that do not compress. ### Does a redesign take longer than a new website? Often, yes, which surprises people. A redesign adds work a new build does not have: auditing existing pages, mapping URL redirects to protect SEO, migrating content, and deciding what to keep. A redesign of a 200-page site can take longer than building a 20-page site from nothing. ### How can you shorten a website timeline? Start content before design, not after. Name a single decision-maker who can approve work within days. Fix the scope and resist mid-project additions. Prepare brand assets, product data, and legal requirements before kickoff. Teams that do these four things routinely launch weeks earlier than teams that treat content and approvals as afterthoughts. SecondSeason designs and builds websites on Next.js and Payload, and we scope the content work honestly at the start instead of discovering it in week five. If you want a realistic timeline for your specific site rather than a range from an article, reach out via /contact and bring whatever content you have. Even drafts tell us a lot.