01. Understand the starting point
We begin with your business and the people you want to reach. You tell me what you offer, what the website needs to do and what you have prepared. If there is an existing website, it helps us discuss what to keep and what to change. Visual references can help too, especially when you explain what appeals to you about each one.
This conversation identifies questions, priorities and dependencies. Who will prepare the text? Are several languages needed? Are external tools involved? Recording these points grounds the project in specific needs and reveals decisions that we cannot yet take for granted.
02. Define the scope and structure
With that initial context, I organise the pages and their roles. The site structure should help visitors move from a first impression of the business to the information they need before making contact. We also define the features and materials involved in this first version.
Before the build begins, the proposal should make deliverables, exclusions and responsibilities clear. Reviews, access requirements and external services are defined at this stage. If a new need appears later, we assess its effect on the agreed scope instead of assuming it is already covered.
03. Shape the content and design
Content brings order to what you want to explain. We work on the main message, the sections and the next step on each page. Your review is essential to confirm that the services, conditions and claims accurately represent the business. Translations also need their own review when they are part of the project.
Using that information, the design sets the visual hierarchy and navigation. We consider how the page reads, what stands out and how it works on different screens. Each decision should be understandable in terms of its usefulness and its fit with the identity of the project.
04. Build and review
The build turns the structure and design into pages people can use. Review covers page routes, links, contact elements and how content appears at different screen sizes. We also check the SEO elements included in the scope, such as page titles and indexing instructions.
Before considering the website ready, we review the content and any outstanding points. If a feature depends on an external service or the publishing environment, it needs to be checked in suitable conditions. Issues should be identified and resolved with a clear understanding of what is required.
05. Prepare for publishing and what follows
Publishing requires the relevant domain, hosting and account access to be confirmed. It also helps to identify the tasks involved in managing the website afterwards. Handover and any guidance on use or updates are defined according to the chosen solution.
Once published, the website can evolve through real customer questions and data, where collection has been planned. Further development or ongoing support is considered according to your needs; it is not assumed to be included in the initial build.