What happens during discovery?
Discovery defines the business offer, customers and required action. We review the existing site and gather constraints such as integrations, approvals and launch dependencies. A written scope identifies deliverables and exclusions before design work starts.
- Business goals and customer questions
- Existing assets and account access
- Required pages and integrations
- Approval responsibilities
How are content and design planned?
Content planning assigns one main answer to each search intent. Service pages describe the offer; guides answer supporting questions. The design then establishes a clear reading order, responsive layout and consistent visual system. Approved content and assets reduce rework during implementation.
What is tested before launch?
Testing checks the agreed customer journeys, not only whether the homepage loads. Forms, payment flows, mobile navigation and errors need representative input. Existing-site migrations also require URL and redirect checks.
- Desktop and mobile navigation
- Forms, validation and confirmation states
- Checkout or booking scenarios where applicable
- Canonical tags, indexing instructions and internal links
- Analytics configuration and consent behaviour
What belongs in handover?
Handover records account access, publishing instructions and maintenance responsibilities. Domain control, source files, licences and support terms need an explicit agreement. The person maintaining the site should complete a representative content update before the handover is considered usable.
How is the timeline agreed?
The timeline follows scope, content readiness and approval dependencies. A simple information site and a complex shop need different testing. We agree a schedule in the proposal rather than applying one generic deadline to every project.
Related reading