Questions about your next website?
Practical answers about website planning, design, development, redesigns and ongoing care.
Explore the topics below. If your project needs a more specific answer, tell us what you have in mind and we can discuss the right starting point.
Planning your project
Scope, timing and the information we need to get started.
The cost depends on the scope: the number and complexity of pages, design requirements, content, language sections, integrations and any custom functionality. We first clarify what you need, then propose an approach and estimate based on the agreed work. Hosting, third-party licences and ongoing services are identified separately where applicable.
The timeline depends on the size of the project, the features involved and how quickly content and feedback are available. After reviewing the requirements, we agree on a delivery plan with key review points. Changes to the scope or delays in approvals can affect that plan.
A short overview of your business, audience, services and goals is a useful start. If available, share your logo, brand guidelines, existing website, draft content and examples you like. You do not need a complete technical specification; we can discuss what needs to be defined during planning.
Content responsibilities are agreed before the project starts. We can plan how text and images fit the pages, while writing, editing, image sourcing or custom visual creation can be included when specified in the scope. We also clarify any third-party image or asset licence requirements.
Design & development
Choosing the right foundation and making the website manageable.
The right choice depends on what the website needs to do and who will maintain it. WordPress is often suitable for content-led business websites with regular updates. A custom approach may be appropriate for specialised workflows or application-like functionality. We compare suitable options against your requirements, resources and future plans.
Responsive layouts are part of the website planning and development approach. We consider how navigation, content, images and forms adapt across desktop, tablet and mobile screens. The devices, browsers and key journeys to review are agreed as part of the project scope.
We plan editable content around the updates your team needs to make. Depending on the implementation, this can include text, images, service pages and reusable page sections. We agree on the editing areas and handover guidance before delivery; changes to custom functionality may still require development.
Yes. A multilingual website can have different pages, navigation and content for each language, rather than matching every page with a translation. We plan the language structure, URLs and visitor journeys around each audience. Translation, localisation and language-specific content preparation are included only when agreed.
Redesign, content & search
Improving an existing website with a considered transition.
We can review the current website and discuss a redesign around your business goals. The review helps identify which content, features and technical elements can be retained, improved or replaced. The final approach depends on the existing platform, available access and the changes you need.
A focused update may be enough if the structure and technology still support your needs. A broader redesign may make sense when the website is difficult to maintain, does not reflect your business or has significant usability or technical limitations. We can assess the main issues and compare practical options before recommending a scope.
Where included in the scope, we consider page structure, headings, editable metadata, internal links, crawlability and other relevant technical foundations. These support a well-organised website, but search performance also depends on content, competition and ongoing work. Rankings or traffic increases are not guaranteed.
We discuss which existing pages and URLs need to be retained, changed or removed. Where migration work is in scope, this can include an old-to-new URL map, appropriate redirects and checks of key links and indexing settings. A careful migration can reduce avoidable disruption, although search rankings may still change after a relaunch.
Performance & technical setup
Speed, maintenance responsibilities and connected systems.
We consider image formats and sizing, page complexity, scripts and suitable caching options as part of the agreed technical work. Hosting and third-party services also affect performance. We can review representative pages and prioritise improvements, while avoiding promises of a fixed score or loading time across every device and connection.
We clarify responsibilities for software updates, backups, access and ongoing monitoring during planning and handover. The arrangements depend on the platform, hosting and any maintenance agreement. Ongoing maintenance, security audits or managed backup services are included only when specifically agreed; no website can be guaranteed completely risk-free.
We can discuss the hosting requirements and help you understand suitable options. Domain registration, hosting purchase, account ownership and any setup work are agreed separately. Where you already have a domain or hosting account, we review whether it fits the project and what access is needed.
Potential integrations depend on the capabilities, APIs and access available in those tools. We first define what information or actions need to connect, then review feasibility and dependencies. Third-party subscriptions, usage charges and custom integration work are identified in the scope where applicable.
Ownership, support & future growth
Understanding what happens after the first release.
Ownership, account access and handover deliverables are agreed as part of the engagement. This includes clarifying access to the website, domain and hosting, along with any source files or documentation included in the scope. Third-party themes, plugins, fonts and other assets remain subject to their own licence terms.
Yes. We can define a useful first release around your most important goals, then plan further pages or features in later phases. Considering likely future needs early helps guide the structure and technical choices. Additional work is scoped separately as priorities become clearer.
We agree on any launch support, handover guidance and ongoing services before delivery. An ongoing arrangement may cover updates, backups or content and functionality changes, depending on the agreed scope. The support period, response arrangements and responsibilities should be clear in the proposal or service agreement.
A business website primarily presents information and helps visitors understand your services or make an enquiry. A web application lets users complete more involved tasks, such as managing records, following workflows or accessing a portal. Some projects combine both, so we define the required user actions before choosing the implementation.
Let’s talk about your project.
Share the challenge you want to solve. We can discuss your requirements and a practical next step.