Website Development Plan: 12-Week Template With Owners and Example

8 min read ยท 2026-10-25

A website development plan is the roadmap for building a new website or redesigning an existing one, from the first goals to launch day. It sets what the site must achieve, which pages it needs, who writes and approves the content, when design and development happen and how you test before going live.

The template below covers 12 weeks in six phases. Each phase has steps and a milestone you can check, such as an approved sitemap or a passed go or no-go meeting. You will also find a filled-in example, who owns what, the risks that most often delay launch and how to report progress to leadership.

The timeline fits a business site of a few dozen pages built by a small in-house team or an agency. A large site with many templates, languages or integrations needs more time in the content and build phases.

The roadmap at a glance

Goal: Launch the new website with every approved page live, forms connected to the CRM, analytics working and the team trained to publish, by the end of week 12. Duration: 12 weeks

  1. Discovery and goals (Weeks 1-2)

    Agree on what the website must do for the business and who decides.

    • Hold a kickoff with the sponsor, marketing, sales and IT to agree on two or three goals, such as more demo requests or fewer support calls.
    • Define the main audiences and the top tasks each one comes to the site to do.
    • Review the current site with analytics: top pages, traffic sources, conversion paths and pages nobody visits.
    • List technical needs: CMS, hosting, integrations, accessibility target, languages.
    • Name one decision owner for content, design and technology.

    Milestone: A project brief with goals, audiences, scope, budget owner and decision owners, signed off by the sponsor.

  2. Sitemap and wireframes (Weeks 2-4)

    Decide what pages the site has and what goes on each one before any visual design.

    • Draft the sitemap with every page and its parent, and test the main navigation labels with a few users if you can.
    • Write a short brief for each key page: audience, goal, main message and the action you want.
    • Create low-fidelity wireframes for the homepage, a product or service page, a content page and the contact page.
    • Map each old URL to a new one if you are replacing a site.

    Milestone: Sitemap and wireframes for key templates approved by the sponsor and the content owner.

  3. Content (Weeks 3-8)

    Produce the words, images and files every page needs, in time for the build.

    • Build a content tracker: one row per page with writer, reviewer, due date and status.
    • Write the pages with the most traffic and conversions first.
    • Collect or produce images, icons, videos and downloadable files with alt text.
    • Run reviews with subject matter experts and legal where needed.
    • Add SEO basics per page: title, meta description and one main heading.

    Milestone: All key pages written and approved in the content tracker, with images and SEO fields ready.

  4. Visual design (Weeks 4-7)

    Turn the wireframes into a design that fits the brand and works on every screen size.

    • Design the homepage and one inner page first, review them, then extend the style to all templates.
    • Design mobile and desktop versions of each template.
    • Build a small set of reusable components: buttons, cards, forms, navigation and footer.
    • Check color contrast and font sizes against WCAG guidance.

    Milestone: Final designs for every template approved in Figma or your design tool, with mobile versions and a component library.

  5. Build and integrate (Weeks 6-10)

    Build the site in the chosen CMS and connect it to the systems it depends on.

    • Set up the CMS, hosting and a staging environment.
    • Build templates and components, then load the approved content.
    • Connect forms to the CRM or email platform, with a test record for each form.
    • Add analytics, the tag manager and the consent banner.
    • Set up user roles so editors can publish without developer help.

    Milestone: Every page live on staging with real content, forms delivering test records and analytics firing.

  6. Test and launch (Weeks 10-12)

    Check everything works, launch with a plan, and fix issues fast in the first days.

    • Test on the main browsers and devices, and run an accessibility and page speed check.
    • Test every form, link and redirect, and proofread every page.
    • Hold user acceptance testing with page owners and fix the issues they log.
    • Hold a go or no-go meeting, then launch with a checklist: DNS, SSL, redirects, sitemap, analytics.
    • Train editors and watch forms, errors and traffic daily for two weeks.

    Milestone: Site live with no critical issue open, forms delivering leads, the XML sitemap submitted in Google Search Console and editors trained.

Example: a website development plan filled in

Picture an engineering consulting firm with an outdated site that does not work well on phones. The goals are more qualified contact requests and a site the marketing team can update without a developer. An agency builds it, and the marketing manager runs the project. Here is how the plan could look.

Content starts in week 3, while design is still in progress. Waiting for final designs before writing is the most common reason website projects slip.

  • Weeks 1-2 (Marketing manager and managing partner): kickoff, goals set, audiences defined as facility managers and procurement leads. Milestone: brief signed.
  • Weeks 2-4 (Agency UX designer): sitemap of about thirty pages, wireframes for five templates, old URLs mapped. Milestone: sitemap approved.
  • Weeks 3-8 (Marketing manager and engineers as reviewers): service pages and case studies written, project photos collected. Milestone: content tracker all green.
  • Weeks 4-7 (Agency designer): homepage and service page designed first, then all templates and mobile. Milestone: designs approved.
  • Weeks 6-10 (Agency developers and IT): CMS set up, contact forms connected to the CRM, analytics and consent banner added. Milestone: full site on staging.
  • Weeks 10-12 (Marketing manager and agency PM): UAT with partners, go or no-go, launch on a Tuesday, editor training. Milestone: live with no critical issue.

Who owns what

Website projects involve many people who each own a small part. When nobody owns a decision, such as the final homepage message, the whole project waits.

Write a RACI in the project brief and share it at kickoff. Limit approvers to one per area, plus the sponsor for the final sign-off.

  • Sponsor (CEO, CMO or managing partner): goals, budget, final approval.
  • Project manager or marketing manager: plan, tracker, weekly status, go or no-go meeting.
  • Content owner: sitemap, page briefs, writing and approvals.
  • UX and visual designer: wireframes, designs, components.
  • Developers: CMS, templates, integrations, performance.
  • IT: domain, DNS, hosting access and security review.
  • Page owners and subject matter experts: review content and test their pages in UAT.

The launch checklist

Run this checklist on staging the week before launch and again on the live site on launch day. Assign each line to an owner and record the result in a shared sheet.

Pick a launch day early in the week, when the team is available for fixes. Avoid the days before a holiday or a big campaign.

  • Every form submits and the record appears in the CRM or inbox.
  • Old URLs redirect to the right new pages with 301 redirects.
  • Titles, meta descriptions and headings set on every page.
  • Analytics, tag manager and consent banner working.
  • SSL certificate active and every page loads over HTTPS.
  • Staging blocked from search engines and that block removed from the live site.
  • XML sitemap submitted in Google Search Console.
  • Backups and a rollback plan in place.

Risks and dependencies

Most website projects slip for the same few reasons. Write them in a RAID log at kickoff, with an owner and a fallback for each, and review it every week.

Content and approvals cause more delays than code. Plan reviewer time in their calendars at the start, not when the draft is ready.

  • Content late: owner is the content owner, fallback is launching with fewer pages and adding the rest after launch.
  • Too many approvers: owner is the sponsor, fallback is one approver per area with a two-day review limit.
  • Integration not ready: owner is the tech lead, fallback is a simpler form that emails the team until the CRM link works.
  • Scope creep: owner is the project manager, fallback is a post-launch backlog for new requests.

How to build the plan in a spreadsheet or Gantt chart

In Excel or Google Sheets, make one row per task with these columns: phase, task, owner, start date, end date, status and dependency. Add a timeline to the right with one column per week and fill the cells for each task's weeks with the phase color. This gives you a simple Gantt view without special software.

Keep a second tab for the content tracker, one row per page. The project manager updates both tabs before the weekly status meeting, so everyone works from the same version.

How to present it to leadership

Put the plan on one slide: the goals, the six phases on a 12-week timeline, the launch date, the owners and the decisions you need. Leadership wants to know whether the date holds and what they must approve.

Each week, send a short status: phase, a red, amber or green rating, what moved, what is blocked and who needs to act. Show designs and content only when you need a decision on them.

Common mistakes to avoid

  • Starting visual design before the sitemap and page briefs leads to pretty pages with no clear purpose, so approve structure and messages first.
  • Waiting for final designs to start writing delays launch, so start content in parallel with design.
  • Letting every stakeholder approve every page stalls the project, so name one approver per area and set review deadlines.
  • Testing forms only on staging misses live problems, so submit every form again on launch day and check the CRM.
  • Forgetting redirects from the old site loses search traffic and bookmarks, so map every old URL and test the redirects before launch.
  • Handing over the site without editor training means it goes stale, so train editors before launch and give them a short publishing guide.

Frequently asked questions

How long does it take to develop a website?

It depends on the number of pages and templates, the content work and the integrations. A business site of a few dozen pages often takes about three months. Larger sites or sites with complex features take longer, mostly because of content and approvals.

What should a website development plan include?

Goals and audiences, scope, a sitemap, page briefs, a content plan, design and build phases, a testing plan, a launch checklist and post-launch checks. Add owners for each phase, a RAID log and a weekly status rhythm.

What are the phases of website development?

Most plans follow discovery, sitemap and wireframes, content, visual design, build and integration, then testing and launch. Content usually runs in parallel with design and build so it is ready when pages are.

Who should be involved in a website project?

A sponsor, a project manager, a content owner, designers, developers and IT, plus page owners who review content and test their pages. Keep the approval group small and name one approver per area.

What is the difference between a website development plan and a website redesign plan?

A development plan covers building any site, new or replacement. A redesign plan is a development plan for a site that already exists, so it adds a content audit of the old site, a URL redirect map and a baseline to compare traffic and conversions after launch.

Generate this roadmap with AI