The questions people ask before they say yes.

Yes. Once the agreed project is complete and any outstanding invoices are settled, the website and agreed project assets are handed over to you. We can also remain involved for hosting guidance, maintenance and ongoing improvements if useful.

Timing depends on the size of the site, content readiness, integrations and how quickly feedback can be agreed. We set a clear delivery sequence at the start and keep the next decision visible throughout the project.

Yes. A redesign starts with an audit of valuable URLs, content, metadata, internal links and technical signals. Where URLs genuinely need to change, the migration plan should use direct server-side redirects rather than simply deleting established pages.

Technical and on-page SEO foundations are considered during the build, including crawlable structure, semantic HTML, metadata, internal linking, performance and indexation controls. Broader search strategy and ongoing SEO can be scoped separately where needed.

We can help with deployment, hosting decisions, maintenance and ongoing improvements. The exact support arrangement depends on the website, its hosting environment and the level of ongoing involvement you need.

Often, yes. We first review the existing platform, codebase, hosting setup and constraints so we can recommend whether targeted improvements or a wider rebuild is the more sensible route.

Responsive behaviour is designed and tested as part of the project rather than treated as a final resize pass. We focus on current mainstream browsers and devices, accessible interaction patterns and layouts that remain usable across screen sizes.

We shape the scope around what the website needs to achieve, the pages and content required, integrations, e-commerce needs, SEO priorities and the level of ongoing support. We recommend the useful parts rather than forcing the project into a fixed tier.

Yes. The visual system is developed around the business, audience, content and goals rather than selecting a generic theme and changing the logo. Reusable design rules keep the finished site distinctive without making future pages inconsistent.

Yes, where the relevant service provides a suitable integration method. We review the technical requirements first, then connect approved forms, analytics, content systems and APIs with appropriate loading, validation and error handling.

We keep decisions, progress and feedback points clear throughout the build. The aim is to reduce long handoffs and vague revision loops by showing what is being decided now and what happens next.

Send a short project brief through the contact form with the business context, what is not working today and the main outcome you want from the website. You do not need a finished technical specification before getting in touch.