Project Time CalculatorProject Time Calculator

Website Build Time Estimate: Brief to Launch

A brochure site with a CMS, where content writing runs beside design but launch still waits on templates.

Quick answer

Most-likely critical path is 38 working days through design and templates. PERT expected time on that path is 39.2 days (90% range about 35–43).

These figures are an illustrative plan for a typical project of this type, not industry statistics. Change the tasks to match your site, team and scope.

The sketch team is a designer, a front-end developer, a CMS implementer and a client who writes content. Hosting is already chosen. SEO setup is inside “launch”, not a separate workstream. Content has float unless the writers miss the CMS-ready date.

Task list and live results

What usually causes delays

A design round that adds a third concept, CMS plugins that fight the templates, copy that arrives as screenshots, and a QA pass that finds missing alt text on every image. The pessimistic 14 days on visual design is extra rounds, not slow software.

How to read the 38 days

Content writing is parallel with design and build. Populate cannot start until both copy and CMS exist, so a slow writer only hurts the date if they finish after the CMS (day 27 in the most-likely table). Until then, design and templates set the pace.

PERT expected time on the design chain is 39.2 days. A 42-day deadline sits near the 90% one-sided duration. Client review days are inside the task durations; they are not extra lag on this page.

Use the critical path calculator and PERT calculator to swap in your own tasks. Count hours per page in the task time estimator. A hard go-live date belongs on the project duration calculator.

How to adapt this plan

A five-page brochure with stock components can shrink visual design and templates; content then becomes the long pole if the writers are slow. A headless CMS adds a “wire content model” task before templates and often puts that model on the path. Translation is a successor of populate, not of brief. If SEO is a real workstream (schema, redirects, crawl of the old site), pull it out of launch and give it populate as a predecessor so QA is not pretending to include it.

Thirty-eight working days is about eight weeks. Client review is already inside design and templates on this page. Extra review rounds belong in the pessimistic values, which is why visual design’s P is 14. If the go-live date is fixed (a conference, a campaign), count working days backwards from that date, then either cut pages or overlap content with IA — and say you fast-tracked. Do not keep the 38-day network and also promise a date that only has 25 working days in it.

Written by . Formulas checked against the site's test suite on 11 November 2026. Last updated 10 November 2026. Method: methodology.