Scope & preparation
When this is useful
Website development is useful when a business needs a new site or an existing one is difficult to maintain, navigate or use on a phone. The brief should identify real audiences, content owners and important journeys. A visual reference helps, but it cannot replace functional requirements.
How ADPR can help
ADPR can scope website design and development around an agreed page structure and feature set. Content, accessibility, performance and search metadata belong in the build plan. Hosting, domain access, integrations and ongoing maintenance should have explicit owners before launch.
A typical process
Map audiences, pages and the main user journeys.
Design and implement the agreed content and interactions.
Test forms, navigation, responsive layouts and handover requirements.
What to prepare
- Current site or reference material
- Approved copy and brand assets
- Required integrations and content-editing needs
Possible scope outputs
- Page and component structure
- Responsive website implementation
- Launch checklist and handover notes
The proposal will confirm what is included, who is responsible and the applicable timeline. These are scope examples, not a fixed package.
Questions worth asking
Does a website build include writing all the content?
Content responsibilities should be agreed in the scope. Existing facts, imagery and approvals are needed even when drafting support is included.
Is ongoing maintenance automatic?
No. Hosting, updates and support coverage should be agreed separately or explicitly included in the proposal.