01
Content and journeys
Identify your important service pages, the information customers need and the actions visitors should be able to complete. Keep useful material while addressing unclear navigation or repeated content.
Existing websites
Think about what a visitor must understand and what your team needs to manage. We help UK businesses connect page structure, useful content and an enquiry journey so a website design has a job beyond making a good first impression.

01
Identify your important service pages, the information customers need and the actions visitors should be able to complete. Keep useful material while addressing unclear navigation or repeated content.
02
List forms, account systems, analytics, payment services and other integrations. Agree what must continue working and what needs replacement or a new connection.
03
Record existing page addresses, files and important inbound links. Prepare an explicit redirect map for URLs that change, and include image and document handling in the plan.
01
Plan backups and testing before changes. Website files, databases, domain records and company email can have separate dependencies and responsibilities.
02
Check the agreed pages, responsive layout, forms, account links and essential metadata in the prepared website. A launch checklist should reflect the actual project.
03
Agree editing access, training, documentation, maintenance and support. The people who manage the website need to understand the new workflow.
Share the website address, the main problems, important integrations and any timing constraints. The quotation will define the deliverables and migration responsibilities.
BAZECITY UK
Identify the services or products people need to compare, the proof they need to trust the business and the next action you want them to take. Existing content can be reviewed before it is moved into a new design. Prioritise clarity on phones and readable calls to action rather than adding sections with no clear purpose.
Confirm who supplies text, photography, branding and approval feedback. Decide which platform the team will edit and what forms or external systems need to connect. Website development, hosting and ongoing maintenance should be scoped separately, with a handover that gives the responsible people the access and instructions they need.