My 6-Step Process for New Website Builds

Most custom website projects take 30-80+ hours of focused delivery. The difference between a stressful build and a smooth one is almost always process.

This is the exact 6-step framework I use on WordPress development projects, from initial scope through to launch and long-term support.

Gantt Chart Breakdown

The timeline I use is usually a 4-6 week shape, with overlap between discovery, design, development, QA, and content population.

The key point in the Gantt is dependency: design and copy sign-off control delivery speed, and final launch quality depends on enough time allocated to QA and deployment prep.

gantt
title Typical WordPress Project Timeline (Week 1-6)
dateFormat  YYYY-MM-DD
axisFormat  Week %W
excludes    weekends
section Week 1
Discovery call                                           :milestone, a1, 2026-01-05, 0d
Initial high-level design review                         :a2, after a1, 2d
Scope review and proposal QA                             :a3, after a2, 2d
Contract signed                                          :milestone, a4, after a3, 0d
Deposit paid                                             :milestone, a5, after a4, 0d
section Week 2
Detailed design review and technical feedback            :b1, after a5, 2d
Dev and staging setup                                    :b2, after b1, 1d
Build Gutenberg blocks and components                    :b3, after b2, 5d
Build desktop layouts                                    :b5, 2026-01-19, 5d
Weekly client call - review and feedback                 :milestone, b4, 2026-01-16, 0d
section Week 3
Content migration (if needed)                            :c2, 2026-01-26, 5d
Weekly client call - review and feedback                 :milestone, c3, 2026-01-23, 0d
section Week 4
Build mobile layouts                                     :d1, 2026-01-26, 5d
Third-party integrations                                 :d2, 2026-01-26, 3d
Weekly client call - review and feedback                 :milestone, d3, 2026-01-30, 0d
section Week 5
Training call for non-technical managers                 :milestone, e3, after d1, 0d
Content updates                                          :e5, after e3, 5d
Weekly client call - review and feedback                 :milestone, e4, 2026-02-06, 0d
section Week 6
Final QA                                                 :f1, after e5, 2d
Pre-launch content updates and SEO checks                :f2, after f1, 2d
Weekly client call - launch readiness                    :milestone, f3, 2026-02-13, 0d
Deployment to Production                                 :milestone, f4, after f3, 0d
Performance optimizations                                :f5, after f4, 1d
Launch                                                   :milestone, f7, after f5, 0d
Final payment                                            :milestone, f6, after f7, 0d
section Ongoing
Post-launch call and review                              :milestone, g2, after f7, 1w
Ongoing support with a WordPress Care Plan               :active, g1, after f7, 1w

Step 1: Project Scoping

This stage defines what we are actually building and why. We map business goals to required pages, user journeys, integrations, and constraints.

Core outputs:

• Scope boundaries and priorities
• Page / template list
• Required integrations and functional requirements
• Delivery milestones and review points

If this step is rushed, everything downstream gets more expensive.

Step 2: Web Design and Copywriting

Design and messaging are developed in parallel, then validated against the agreed journeys from scoping.

Core outputs:

• Wireframes and page-level hierarchy
• Visual direction and component styling
• Conversion-focused copy and CTAs
• Mobile-first layout decisions

This is where projects either gain clarity or start accumulating revision debt.

Step 3: Web Development

Development turns approved design and copy into a production-ready build.

Core outputs:

• Custom WordPress theme implementation
• Reusable block/component setup
• Form, CRM, analytics, and third-party integrations
• Technical SEO foundations and performance setup

The Gantt overlap here is deliberate: content prep and QA begin before every page is 100% complete, which keeps momentum high.

Step 4: Manager Training

Before launch, stakeholders need confidence managing the site without developer dependency.

Core outputs:

• CMS training sessions for your team
• Editing workflows for key templates
• Publishing and content governance guidance
• Short handover documentation

Good training prevents post-launch bottlenecks.

Step 5: Deployment

Deployment is controlled and checklist-driven, not a last-minute push.

Core outputs:

• Production environment validation
• DNS / SSL / caching checks
• Redirect mapping and launch QA
• Go-live monitoring and rollback readiness

A calm launch is usually the result of disciplined prep in the previous phases.

Step 6: Ongoing Support and Maintenance

Launch is the start of optimisation, not the finish line.

Core outputs:

• Security and update management through a WordPress Care Plan
• Performance and uptime monitoring
• Iterative UX and conversion improvements
• Priority fixes and roadmap support

For teams that want continuous improvement, this is where the real long-term value compounds. You can see the full support scope on the WordPress Care Plans service.

Why This Process Works

The Gantt structure keeps work visible, dependencies clear, and expectations realistic. Every step has a defined purpose and measurable outputs, so projects stay aligned and move forward without guesswork.

If you are planning a new build, you can see how this is applied in practice on my WordPress Development service.