What needs to change for the business?
A redesign should begin with a business problem. Perhaps visitors cannot understand the offer, the company has entered a new market or the site makes it difficult to inquire. Write down the change you want to see before collecting visual references.
Choose a few practical measures, such as qualified inquiries or completion of a key journey. A traffic increase alone may not tell you whether the website is helping the business.
What should be preserved?
List the useful assets: the official logo, real project work, effective copy, important URLs and working contact channels. Record the source of each item so the redesign does not accidentally replace genuine brand equity with invented material.
Review existing search data if it is available. Pages that already attract relevant visitors deserve a deliberate migration decision, even when their layouts need to change.
What will visitors need to understand?
Map the major questions: what the company does, who it serves, what proof is available and how to take the next step. Build the navigation and page structure around those decisions.
Avoid multiplying pages just to repeat a phrase. A service page should answer useful questions specific to that service and connect to relevant work.
Who will maintain it?
Decide who changes copy, replaces images, publishes articles and manages inquiry notifications. Editing needs affect the content model and may influence whether a CMS is worthwhile.
Ask for a demonstration of a routine update during handover. Replacing a photograph should not require rewriting a component or animation.
What does launch include?
A launch plan should cover redirects, metadata, contact forms, phone links, analytics configuration and direct access to nested pages. It should also name the person responsible for the domain and hosting.
Review mobile behavior, keyboard access and reduced motion alongside desktop visuals. Keep a record of the deployed version and a practical rollback path. The first production release is the start of an operating website, not the end of responsibility.