Start with the person using the screen
What does a visitor need to understand, what concerns them and what should they do next? Those questions shape navigation, copy, service pages and forms. A customer portal also needs roles, history and appropriate data access. Plan the structure before decorating individual screens. The aim is a distinctive design that represents the service and works on a phone, rather than another template distinguished only by its colours.
Test functions as complete journeys
A form is not complete just because a success message appears. Check that the request is saved, the notification is sent and staff can continue the workflow. Apply the same approach to sign-in, search, uploads and payments where included. Plan for errors and repeated user actions. Search readiness means useful pages, a coherent structure and sound technical foundations, not a guaranteed ranking regardless of competition or ongoing content work.
Launch a website you can keep up to date
Before publication, agree who edits content, where assets live and which changes need a developer. Preserve existing form and integration contracts when redesigning, then verify them after changes. Deliver instructions, access and a clear deployment process alongside the pages. Pricing depends on the product, distinct user journeys and integrations. Comparing those honestly is more useful than comparing identical turnkey website labels that hide very different amounts of work.
Two useful questions
Can you redesign without breaking existing forms?
Yes. First document fields, endpoints and behaviour, then change the presentation and repeat the checks. Any necessary logic change is agreed separately.
Will the site work well on mobile?
Mobile journeys are part of design and testing. The device and browser coverage is agreed around the audience and the project’s risk.