New business websites
Commission a new business website
Service hub
Build something useful, improve what is there, or fix the part that is getting in the way. Start with the customer task.
01 / Service hub
An outdated look and a broken customer journey are different problems. Review what visitors need to do, which pages support it and what already works before deciding how much to replace.
02 / Service hub
A website scope should identify the audience, page map, content responsibilities, design approach, implementation, responsive checks and handover. Forms, third-party tools, hosting and launches need their own clear boundaries.
03 / Service hub
Hypothetical planning specimen. It explains the decisions and checks to agree; it is not a completed customer deliverable or a fixed offer.
| Starting condition | Explore | Expected scope distinction |
|---|---|---|
| No usable site | New website | Page/content responsibility plan and first-build acceptance. |
| Structure or design must change | Redesign | Keep/change assessment and protected existing URLs/tasks. |
| One bounded defect | Repair | Reproduction, diagnostic stop point and regression-tested change. |
| One campaign offer | Landing page | One audience, promise and measurable action. |
| Catalog and checkout | Storefront scope | Product/variant and test-order dependencies. |
| Platform, domain or data move | Migration | Inventory, mapping, cutover and rollback. |
| Measured loading or interaction problem | Performance work | Comparable baseline, bottleneck and retest. |
04 / Service hub
A new business site, a campaign landing page and a redesign have different inputs and acceptance checks.
Commission a new business website
Improve an existing website without losing what works
Create a focused campaign or offer page
Build or improve an online store
Move a site without avoidable data or search loss
Resolve a bounded site issue without a full rebuild
Diagnose and improve a slow website
05 / Service hub
Decide who controls the domain, hosting, source files, content and licenses before work starts. A handover should explain common updates and any ongoing dependencies. WordPress and other platforms need a fit check for the actual task.
To define editing, files and account responsibilities: Review the handover checkpoints
06 / Service hub
The regional Now projects are owned work, with a publishing context. They should be assessed for the contribution and decisions that can be verified, rather than treated as client testimonials or evidence for an unrelated specialist service.
For an owned example of different reader entrances: Inspect RVN task-led navigation
For an owned example of geographic information structure: Inspect regional and city navigation
For an owned example of changing information and its limits: Inspect source and date cues
07 / Service hub
Original copy, custom data, integration complexity, content migration, risk to an existing site and the amount of review all affect the job. Page count alone does not describe the work.
08 / Service hub
Use the refresh-or-rebuild guide to decide what to preserve. Then list the customer action you want to improve and the pages that support it.