The time needed to build a website depends on the scope, the state of the content and how quickly the project can move through decisions. A clear brief with approved material is a different starting point from a project that also needs positioning, copywriting and new photography.
For a straightforward business website, a schedule measured in weeks may be appropriate. A larger project with substantial content, multiple stakeholders or complex integrations may need months. The useful estimate is the one built around your actual requirements.
Before committing to a launch date, ask the agency to show the stages behind it. You should be able to see what happens, what depends on your input and where testing fits.
Planning and discovery
The first stage establishes what the website needs to achieve and what is included. It may involve reviewing the existing site, discussing audiences, defining functions and agreeing the main page structure.
The output should be clear enough for design and development to proceed without repeatedly reopening fundamental questions. On an established website, this is also the point to identify valuable content and search performance that the rebuild must take into account.
Rushing this stage can leave the team designing pages before it understands what belongs on them.
Content preparation
Content work can run alongside other stages, but it needs its own schedule. Service descriptions may require interviews and internal approval. Project examples may need client permission. Photography may depend on access to people or locations.
Assign an owner and a due date to each content item. A general instruction that “the client will supply copy” is not enough to plan around.
If some material will arrive late, agree which parts of the website can proceed and which decisions must wait. Designing around placeholder text can be useful temporarily, but it should not hide unresolved content requirements.
Design and feedback
Design translates the agreed structure and content into layouts. The team needs time to consider desktop and mobile presentation, navigation and important interactions.
Feedback works best when it is consolidated. If several people are reviewing the design, appoint someone to resolve conflicting comments before sending them to the agency. Explain the reason behind a requested change so the designer can address the underlying concern.
A schedule should allow for review. It should also state what approval means and how later changes will affect the work.
Development and content entry
Development turns the approved design into a working website. The time required depends on the layouts, editing tools, forms and integrations involved.
Page count alone will not tell you how long this takes. A large set of similarly structured articles may be relatively straightforward to import. A smaller site with complex permissions or an unfamiliar third-party system may need more development and testing.
Ask whether content entry is part of this stage and whether the agency is waiting for access, documentation or decisions from another supplier.
Testing, approval and launch
The finished site needs time for review before it replaces the live one. Allow for checking content, mobile layouts, forms, links, integrations and agreed accessibility requirements. A redesign also needs the relevant migration checks.
Plan time to fix what the review finds. A schedule that ends development on Friday and assumes an unquestioned Friday launch leaves no room for that work.
Launch itself requires coordination: final approval, access to accounts, responsibility for any hosting changes and checks on the live domain.
An illustrative eight-week schedule
This is a planning example for a defined business website, not an industry average or a Think Digital delivery commitment. It assumes no major integration work and timely access, content and approvals.
| Period | Main activity | Client contribution |
|---|---|---|
| Week 1 | Discovery, scope and page structure | Confirm objectives and provide access |
| Weeks 2–3 | Content development and key designs | Supply material and consolidate feedback |
| Weeks 4–6 | Development and content entry | Resolve questions and review working pages |
| Week 7 | Testing and final review | Approve content and complete user acceptance |
| Week 8 | Final fixes, handover and launch | Authorise launch and confirm operational contacts |
Some projects need fewer stages or less time. Others require additional rounds of research, procurement, content review or development. The estimate should explain those assumptions rather than presenting one duration as suitable for every site.
What if you have a fixed deadline?
Explain why the date matters at the first conversation. An event, business launch or contract change may create a genuine constraint.
Then decide what must be ready for that date. A phased launch can be sensible if the first release is complete and useful in its own right. Essential service information and a working enquiry route might launch before a larger resource library.
Ask the agency to identify the decisions that could put the date at risk and when those decisions must be made. That gives you a schedule you can manage.
Use our website brief template to prepare your requirements. Then talk to Think Digital about the scope and timing of your website project.
