Opens in a new tab
All articles
B2B Web Design

7 Website Redesign Timeline Factors: Complete 2026 Guide

Seven factors that set a website redesign timeline: build weeks by site size, the clock a quote runs on, content delays, five smaller delays, backward planning, narrow launches and the checks to keep.

7 website redesign timeline factors. Four experiments found backward planning gave longer, less biased completion predictions (Wiese et al., 2016).

Published 23 January 2025 · Last updated and fact-checked 29 October 2026

Short answer: A five-page site takes 2 to 3 weeks of build once the content is in, a marketing site of 8 to 15 pages takes 4 to 6 weeks, and a landing page takes 1 to 2 weeks. Launch dates slip mostly on late copy and late decisions, and in Buehler’s 1994 studies people’s own time predictions ran too optimistic.

A marketing lead has told her CEO the new site goes live before the spring trade show. The quote said six weeks. It is now week nine. Design was signed off in week three, and the build has sat on a staging server for a month. Her website redesign timeline did not slip in Figma or in code. It slipped in a shared folder, where the services copy is still waiting on comments from three people.

That is not a design problem or a developer problem. It is content delays and late decisions, and you can see both coming on day one. It is why my small-site quote says 2 to 3 weeks from content, not 2 to 3 weeks from signing.

This guide gives you seven factors that set your launch date, in the order I plan them on a project: site size, which clock the quote runs on, content, five smaller delays, backward planning, narrow launches and the checks I never cut. For the money side, see what a website redesign costs in 2026. This page is about weeks.

Key takeaways

  • My published terms are 1 to 2 weeks for a landing page, 2 to 3 weeks from content for a five-page site and 4 to 6 weeks for a marketing site of 8 to 15 pages.
  • Starting the writing on day one instead of after design sign-off can save three weeks on a 10-page site whose copy takes three weeks.
  • Halkjelsvik and Jørgensen’s 2012 review found underestimation was reported more often than overestimation in engineering and management studies.
  • Wiese, Buehler and Griffin ran four experiments in 2016 and found backward planning produced longer, less biased completion predictions.
  • Two revision rounds per phase give a project an end date, because a project without a limit on rounds has none.
FactorQuestion it answersTypical effectStart with
1. Size and platformHow many build weeks?1 to 6 weeks of buildThe page list
2. The clockWhen does the count start?Weeks of difference between quotesThree questions to each vendor
3. ContentWho writes the copy and when?Often 2 to 4 weeksA named owner per page
4. Five smaller delaysWhat else stretches the date?Days to weeks eachA kickoff list with owners
5. Backward planningWhat is the latest safe start?14 weeks in the worked exampleThe launch date
6. Narrow launchesWhat fits in one or three weeks?7 to 21 daysOne page with one decision
7. Checks to keepWhat survives a fixed date?Protects leads and rankingsPayments, redirects, forms
The seven factors that set a website redesign timeline, from site size to the checks you keep

1. How many build weeks does your site size and platform need?

A landing page takes 1 to 2 weeks, a small business site of up to five pages takes 2 to 3 weeks from content, and a marketing site of 8 to 15 pages takes 4 to 6 weeks. Custom B2B builds and stores are set in the fixed quote, because their weeks depend on the page list and the catalogue.

  • Landing page: 1 to 2 weeks once the offer and headline are agreed
  • Small business site: up to 5 pages, 2 to 3 weeks from content
  • Marketing site: 8 to 15 pages, 4 to 6 weeks with a content plan owned page by page
  • Online store: set in the quote by catalogue size, starting from a clean product export
Build weeks by site size on the Jackai Agency price table, with what starts each clock

The build weeks come from my price table. The other columns in my planning sheet are what to watch, because they decide whether the weeks hold. Platform matters less than people expect on a small site. On my price table a five-page site costs less in Framer than in WordPress, but the weeks are the same: 2 to 3 weeks from content on both.

It starts to matter on bigger builds, such as the Snappy Kraken HubSpot CMS project for a B2B FinTech SaaS that serves financial advisors, where I took 6 responsive pages from Figma to production in 3 weeks. Part of that build was HubL templates and a bound design system, so the marketing team could edit pages afterwards without a designer. That is build time you spend once and get back every time someone edits a page.

Stores run on a different clock, because a catalogue is data work and data work grows with products, not pages. For S.T. Dupont Vancouver, a luxury retailer and authorized S.T. Dupont dealer, I moved 290 products from Wix to WooCommerce with taxonomy, pricing and product copy intact. For Cubanbest, a Vancouver premium retailer, the move was 638 SKUs. Changing platform also adds a redirect map for every URL that moves, which my page on website migration without losing search traffic covers.

The Snappy Kraken homepage on HubSpot CMS, a build that took 3 weeks from Figma to production
Snappy Kraken homepage on HubSpot CMS, a Jackai Agency build. Graphic generated with Higgsfield from a screenshot of the live page.

2. Which clock does the quote run on?

Every website redesign timeline runs on one of three clocks: signing, design approval or content delivery. A quote of three weeks and a project of three months can describe the same job, depending on which clock the vendor read. Ask which event starts the count before you compare any two quotes.

  • Clock one: starts when you sign
  • Clock two: starts when the design is approved
  • Clock three: starts when the content is delivered, which is how my small-site quote runs
  • Audit: my Website Audit adds one week before any of them
Three clocks drawn on one calendar: signing, design approval and content delivery

The Snappy Kraken number above is a build clock, 3 weeks from Figma to production, because the design existed before those three weeks began. My small-site quote is a build clock too, counted from the day content arrives. When you ask a vendor how long a redesign takes, ask which clock the answer uses.

The research on time prediction makes the same distinction. Halkjelsvik and Jørgensen separate performance time predictions, such as a number of work hours, from completion time predictions, such as delivery dates, because many studies fail to tell them apart (Halkjelsvik and Jørgensen, 2012). A quote in weeks of work and a quote in a launch date are different promises.

“We summarize similarities and differences between performance time predictions (e.g., number of work hours) and completion time predictions (e.g., delivery dates)”

Halkjelsvik and Jørgensen wrote in the abstract of their 2012 review (University of Oslo and Simula Research Laboratory) (DOI)

Before you compare two quotes, ask each vendor three things. Which event starts the clock: signing, design approval or content delivery. What pauses it: most quotes pause while waiting on client feedback or content. What counts as done: live on your domain, or handed over on a staging server. A vendor who answers all three in one sentence each is giving you a plan. A vendor who answers with a total number of weeks is giving you a hope.

3. Why do content delays move the launch date more than design?

Design and code are done by people whose job that week is your site. Content is written by people whose job that week is everything else. If one person writes all the copy, that person’s calendar is your timeline, and the research on time estimates explains why that person is surprised by it.

  • Owner: whoever writes each page, named, with a date
  • Typical delay: the three weeks in my worked example
  • Why it compounds: late copy reopens approved layouts
  • Fix: start writing on day one, in parallel with design
Copy starting on day one runs beside design; copy starting after sign-off adds three weeks

Here is a worked example. You need a 10-page marketing site, your team writes the copy, the audit takes a week, and design and build take 4 to 6 weeks. Say the copy takes your team three weeks. If writing starts on day one, it runs next to design and costs nothing on the calendar. If writing starts after design sign-off, those three weeks land on top of the build and the launch date moves by three weeks. Same site, same team, same budget.

Buehler, Griffin and Ross found that people underestimated how long their own tasks would take, because they focused on the plan for this task and not on how similar tasks had gone before (Buehler et al., 1994).

“Ss’ predictions of their completion times were too optimistic for a variety of academic and nonacademic tasks.”

Buehler, Griffin and Ross wrote in the abstract of their 1994 study (Simon Fraser University) (DOI)

Content delays also compound in a way design delays do not. I cannot set the final layout of a services page until I know how long the copy is. A heading that fits on one line in a placeholder can wrap to three lines on a phone with the real words. So late copy does not only delay its own page. It reopens design work that was already approved.

4. What are the other five things that stretch a website redesign timeline?

Beyond content, five causes stretch the schedule: a decision-maker who arrives late, pages added after kickoff, missing access, untested integrations and open-ended feedback. Each has a usual owner, and writing the owner down at kickoff is the cheapest fix I know for all five.

  • Late decision-maker: someone senior sees the site for the first time in week five
  • Pages added after kickoff: each adds copy, design and testing
  • Access and integrations: registrar, hosting, CRM, analytics, forms, booking and payments
  • Open-ended feedback: my terms include two revision rounds per phase
Five smaller delays, each with the person who usually owns it

The risk of a late decision-maker grows with every audience the site serves. For W Communications, a Seattle communications and PR firm, four audiences arrived at one homepage: media, clients, event bookers and readers. The rebuild gave each audience its own path. Four paths means four sets of copy to approve, so count reviewers per audience, not per site.

Access deserves a line of its own. A launch can wait days on one password held by someone who left the company. Integrations need testing with real accounts, not test data alone.

Added pages deserve more weight than they get. In a survey study of software projects, changing requirements had a significant effect on schedule overrun and cost overrun (Zowghi and Nurmuliani, 2002).

“requirement volatility has a significant impact on schedule overrun and cost overrun in software projects”

Zowghi and Nurmuliani wrote in the abstract of their 2002 study (University of Technology Sydney) (DOI)

There is one more reason to write these down at kickoff. When Jørgensen and Moløkken-Østvold studied why software estimates went wrong, people tended to name factors outside their own control as the cause, and credited their own skill when estimates were right (Jørgensen and Moløkken-Østvold, 2004).

“a strong tendency to perceive factors outside the respondents’ own control as important reasons for inaccurate estimates”

Jørgensen and Moløkken-Østvold wrote in the abstract of their 2004 study (Simula Research Laboratory) (DOI)

A list of delay causes with an owner on each saves both sides an argument later.

5. How do you build a website redesign timeline that holds?

Start at the launch date and plan backward, break the project into page-level tasks, put a name and a date on every page’s copy, check how long your last project really took, and freeze the page list at kickoff. Each step has a reason in the research on time estimates.

  • Plan backward: start at the launch date and work toward kickoff
  • Unpack tasks: “write the copy” becomes one task per page
  • Name and date: every page has an owner and a due date
  • Freeze the list: new ideas go on a phase-two list with a date
A backward plan from a Monday 1 February 2027 launch to a last-week-of-October kickoff

Planning backward works for a measured reason. Wiese, Buehler and Griffin ran four experiments and found predicted completion times were longer, and less biased in the study that tracked real finish times, when people planned from the end goal backward (Wiese, Buehler and Griffin, 2016).

“Backward planning involves starting a plan at the end goal and then working through required steps in reverse-chronological order”

Wiese, Buehler and Griffin wrote in the abstract of their 2016 paper (Wilfrid Laurier University and the University of British Columbia) (DOI)

Unpacking helps too. People who split a task into its parts gave longer estimates, less biased in two of the experiments (Kruger and Evans, 2004). And plans that tie a specific situation to a specific action help people follow through on goals (Gollwitzer, 1999). “The head of sales sends the services copy on 12 November” is a date someone can chase. “Marketing will handle copy” is not.

“Whenever situation x arises, I will initiate the goal-directed response y!”

Gollwitzer wrote in the abstract of his 1999 paper (University of Konstanz) (DOI)

Here is a plan built backward on a real calendar. Say your launch date is Monday 1 February 2027 and you need a 10-page marketing site. Keep the week of 25 January for launch checks, which means a 4 to 6 week build has to start by 14 December at the latest. The weeks of 21 and 28 December usually lose most reviewers to holidays, so count them as half weeks. That pulls the latest safe build start back to 7 December. The safest plan has the copy written and approved before the build starts, with an audit in the first week of November. That puts kickoff in the last week of October 2026, 14 weeks before a launch you might have pictured as a six-week job.

On kickoff day, have these ready: the page list with one owner and one due date per page, existing copy marked keep, rewrite or cut, brand files, logins for the registrar, hosting, CRM and analytics, every person who signs off by name, and the hard date with the reason for it.

The Snappy Kraken homepage I rebuilt on HubSpot CMS, live in 3 weeks
After: the Snappy Kraken homepage I rebuilt on HubSpot CMS, live in 3 weeks.

6. What does a one-week or three-week launch actually need?

Fast launches happen, but they are narrow builds with a single job. A funnel is one path with one decision at the end, so there is no menu to agree on and no services pages for five people to approve. Fewer pages means fewer content delays, and that is what makes them fast.

  • Copy Chief funnel: World of Financial Copy launched in one week, 56 orders at a 4% conversion rate
  • Crossroads Summit: launched in 14 days, 10x on event ticket sales
  • Snappy Kraken: 6 pages in 3 weeks, with the design already in Figma
  • Rule: shrink the job to fit the week
Three fast launches on one scale: 7 days, 14 days and 21 days

For Copy Chief, a copywriting education business, I built and launched the World of Financial Copy promo funnel in one week on ClickFunnels, ThriveCart and Keap: 56 orders, 4% conversion rate. The Crossroads Summit event funnel launched in 14 days and returned 10x on event ticket sales. These are first-party results from my own client work, not independent audits.

The Snappy Kraken build was larger, 6 pages in 3 weeks, but its clock started with the design already in Figma. If your launch date is a week away, shrink the job to fit the week. A one-week website redesign timeline only works for one page that carries the decision, such as a booking page, an event page or a single offer. Launch that, and let the rest of the site follow on the normal schedule. The test I use is simple: if two different people need to approve the page, it is not a one-week job, because each approval adds a round of comments and a wait. One decision-maker, one page, one offer is the shape that fits.

7. Which checks do you keep when the date is fixed?

When a schedule runs late and the date is fixed, cut pages, not checks. I keep four even when launch is close: payment testing, redirects for every moved URL, lead source on every form and every template checked on a phone. Skipping them trades a launch date for lost sales and rankings.

  • Payments: tested end to end at checkout before launch
  • Redirects: every moved URL pointed to its new page
  • Lead source: carried from the form into the CRM
  • Phones: real copy at real width on every template
Four checks that stay on the plan and four things that can move to phase two

On the S.T. Dupont Vancouver store, I connected Clover POS and tested the payment path end to end at checkout before launch. A store that cannot take money is not launched. Skipping redirects costs search traffic on every old link. My lead attribution method shows how the form-to-CRM path is wired.

What I would cut: secondary pages, old blog posts that nobody reads, and anything on the phase-two list. A site can launch with five strong pages and add three more a month later. It cannot launch with a broken form and earn back the leads it lost. Every lead that arrives in the first week without a source attached is a lead you cannot trace back to the channel that paid for it, and that gap does not close later.

“A site can launch with five strong pages and add three more a month later.”

Joshua Jackai, Vancouver web designer, wrote this in the article

The same logic applies to a late review. If a stakeholder wants a section rewritten in the final week, ask which approved page they would trade for it, and log the rewrite on the phase-two list with a date.

The Snappy Kraken homepage before the rebuild
Before: the Snappy Kraken homepage before the rebuild.

Which timeline factor is hurting your project most?

Use the filter to see which delays you own, which I own and when each shows up. It reads from the same seven factors as the guide, so the answer matches the advice. Pick an owner or a phase and the rows that do not fit are hidden, not deleted, so you can switch back at any time.

Filter the delays

Website redesign delays, who owns each and when it shows
DelayOwnerWhen it showsWhat I do about it
Copy written after design sign-offYouBefore kickoffStart writing on day one, one owner and one date per page
Ambiguous quote clockBothBefore kickoffAgree which event starts the count and what pauses it
Senior reviewer arrives lateYouDesignPut that person in the first review
Pages added after kickoffBothBuildFreeze the page list, move new ideas to phase two
Missing loginsYouBuildCollect registrar, hosting, CRM and analytics access at kickoff
Untested integrationsMeLaunchTest forms, bookings and payments with real accounts
Open-ended feedbackBothDesignTwo revision rounds per phase
Skipped redirectsMeLaunchMap every moved URL before the domain switches

Work out your latest safe kickoff date

Enter your launch date, the build length, the weeks your team needs for copy and whether you want the audit. The planner counts backward and shows the latest safe kickoff. The defaults are placeholders, not results, and the extra buffer week is my working rule, not a researched figure.

Latest safe kickoff planner

Defaults are placeholders, not results. The plan adds one week of launch checks. Count holiday weeks as half weeks by raising the buffer.

Frequently asked questions

How long does a website redesign take?

A landing page takes 1 to 2 weeks, a five-page site 2 to 3 weeks from content and a marketing site of 8 to 15 pages 4 to 6 weeks. Add one week for an audit and the time your team needs for copy, unless it runs alongside design.

What delays a website redesign the most?

Late copy and late decisions. Content is written by people whose week is spent on other work, and late copy reopens approved layouts. Zowghi and Nurmuliani’s survey also found changing requirements significantly affect schedule overrun, so freeze the page list at kickoff and move new ideas to phase two.

Can a website be redesigned in a week?

Only a narrow one. A single page that carries one decision, such as a booking page, an event page or one offer, fits a week. I launched the World of Financial Copy promo funnel in one week. A full multi-page site does not fit, because each page needs approved copy.

When should I start planning a redesign before my launch date?

Plan backward from the launch date. In my worked example, a Monday 1 February 2027 launch for a 10-page site needed kickoff in the last week of October 2026, 14 weeks earlier, with copy written first and holiday weeks counted as half weeks. Check your own calendar the same way.

Book a call before you sign anything

Bring your launch date and your page list. On a 30-minute call with me, we can check your website redesign timeline against the list and see which pages fit and which belong in phase two. Every project gets a fixed quote, two revision rounds per phase, and a site, domain and hosting in your name.

Book a call with Joshua, and I will reply within one business day.

Sources

Peer-reviewed research

Buehler, R., Griffin, D., and Ross, M. (1994). Exploring the “planning fallacy”: Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366 to 381.

Gollwitzer, P. M. (1999). Implementation intentions: Strong effects of simple plans. American Psychologist, 54(7), 493 to 503.

Halkjelsvik, T., and Jørgensen, M. (2012). From origami to software development: A review of studies on judgment-based predictions of performance time. Psychological Bulletin, 138(2), 238 to 271.

Jørgensen, M., and Moløkken-Østvold, K. (2004). Reasons for software effort estimation error: Impact of respondent role, information collection approach, and data analysis method. IEEE Transactions on Software Engineering, 30(12), 993 to 1007.

Kruger, J., and Evans, M. (2004). If you don’t want to be late, enumerate: Unpacking reduces the planning fallacy. Journal of Experimental Social Psychology, 40(5), 586 to 598.

Wiese, J., Buehler, R., and Griffin, D. (2016). Backward planning: Effects of planning direction on predictions of task completion time. Judgment and Decision Making, 11(2), 147 to 167.

Zowghi, D., and Nurmuliani, N. (2002). A study of the impact of requirements volatility on software project performance. Proceedings of the Ninth Asia-Pacific Software Engineering Conference (APSEC 2002), IEEE, 3 to 11.

Industry and first-party sources

Jackai Agency price table, 3 October 2026, and client case studies: Snappy Kraken, S.T. Dupont Vancouver, Copy Chief and W Communications. These are first-party records of my own work, not independent audits.

×

Privacy Preference Center