Most business website redesigns take from a few weeks to a few months. As a rough guide, a small brochure site of five to ten pages can often be delivered in four to eight weeks, while a larger site with many page types, custom features or heavy content migration may take three to six months or more. These are typical ranges, not promises. The timing depends more on decisions and content than on design itself.

What shapes the timeline

Several factors matter most:

• The number of page types and templates

• How much new copy and photography is needed

• Integrations such as booking, CRM or payments

• How quickly feedback and approvals arrive

• Whether a brand refresh is happening at the same time

Delays usually come from waiting on content or approvals, rather than from the designers and developers.

A typical sequence

Projects usually move through discovery, structure, design, build, testing and launch. Discovery clarifies goals and audiences. Structure covers the sitemap and page layouts. Design shapes the look and feel. Build brings it to life in the chosen platform, and testing checks speed, accessibility, forms and tracking. Some stages overlap, but skipping them tends to cause rework. If a modern visual builder such as Framer is used, build time can be shorter than with a fully custom approach, though planning and content still take the time they take.

Content is the real critical path

The most common reason a launch slips is copy. Pages cannot be finished until the words and images exist, and writing good service content takes longer than most teams expect. Decide early who writes, who edits and who signs off. Strong copy also pays back, as we explain in website copywriting for service pages. Google's guidance on creating helpful content is worth a read before you start.

Build in time for migration and testing

If you have a lot of existing pages, moving them, mapping redirects and checking metadata adds time, particularly when changing platform. Our website redesign checklist shows the steps involved. Allow a week or more at the end for testing and fixes. Rushing this stage is how broken forms and missing redirects reach live sites.

How to keep it moving

Name one person to gather feedback, prepare content early and agree review dates before the project begins. Consolidate comments into a single round rather than sending them piecemeal. Limit the number of approvers, and decide in advance who has the final say if opinions differ. Treat new ideas mid-project as a separate phase unless they are essential.

Common causes of delay

• Late or changing copy

• Too many people approving

• New requirements mid-project

• Complex migrations

• Waiting on third-party access, such as domain or hosting logins