Frequently asked questions

I mainly build focused websites for small businesses, freelancers, consultants, and independent professionals. New websites, redesigns, rebuilds, and development from an existing design are all suitable starting points.

Yes. You do not need to arrive with a finished plan. We can clarify what the website needs to achieve, who it is for, what content you already have, and what the most useful next step would be.

Yes. An existing website can be reviewed and rebuilt where the structure, design, technology, content, or overall experience needs improving.

Yes. If you already have an approved design, I can focus on turning it into a responsive, maintainable website rather than creating a new design direction.

Yes. The initial consultation is free and there is no obligation to proceed. It is an opportunity to discuss what you need, whether the project is a good fit, and what the next steps might be. Scope and pricing are only confirmed after that discussion.

The final cost depends on the size and requirements of the project. The Services page provides example starting points to help you understand the likely level of investment before getting in touch.

The main factors are the number and complexity of pages, design requirements, content, editable content needs, multilingual functionality, forms, and any additional features or integrations required.

No. They are example starting points rather than fixed packages. Each project is scoped around what the website actually needs, so the final proposal may be smaller, larger, or structured differently.

Yes. Where it makes sense, a website can begin with a focused set of pages and be extended later. I aim to use a structure that makes future pages and improvements easier to add.

Projects are normally split into two payments: an initial payment to confirm the project and begin work, followed by the remaining balance before launch or final handover. The exact payment terms are confirmed with the project scope before work begins.

No. If you do not already have a design, the required design work can be included in the project. If you already have an established design or clear visual direction, the project can also be built around that.

No. A rough idea of your business, audience, pages, and goals is enough to begin the conversation. Content requirements can be clarified during planning.

Yes. Existing content can be reviewed, simplified, reorganised, and adapted to fit the structure and purpose of the website. The exact level of content support can be agreed as part of the project.

Yes. Multilingual websites can be planned where they are useful for your audience. This can include English and German as well as other language combinations depending on the project.

It begins with an enquiry and an initial discussion about what you need, what the website should achieve, and what information is already available. From there, the scope and next steps can be clarified.

It depends on the size of the website, the amount of design and content work required, and how quickly feedback and materials are available. A realistic schedule is agreed once the scope is clear.

The website is reviewed at clear points during the project rather than leaving everything until the end. Feedback is used to refine content, layout, functionality, and other agreed areas before launch.

You will need to provide the business knowledge, content, feedback, and decisions that only you can provide. I keep those requests focused so it is clear when your input is needed and what decision needs to be made.

Yes, if editable content is included in the project. We can agree which parts of the website should be manageable without changing the underlying page structure, and you will receive access to the agreed editing setup.

The aim is for you to retain control of the important parts of your website setup. Your domain and hosting should remain accessible to you, and the handover makes clear where the website is hosted, what accounts are involved, and what you control.

The website is not built around unnecessary platform lock-in. Some third-party services may have their own fees where they are genuinely useful, but these should be clear rather than hidden or required simply to keep control of the website.

Yes. The website is built on a maintainable technical foundation so another capable developer can work with it later if you choose. You should not need to remain dependent on one developer simply to keep the website usable.

The final stage includes deployment, final checks, and handover. You will know where the website is hosted, what access you have, how any agreed content editing works, and what the next steps are.

Yes. Post-launch support can be arranged for maintenance, content updates, small improvements, performance work, analytics, hosting, or other agreed needs.

Yes. Updates and improvements can be handled after launch as separate work or as part of an agreed ongoing support arrangement.

Yes. New pages, content, functionality, and other improvements can be added later where the underlying structure supports them. The aim is to avoid building the initial website in a way that unnecessarily limits future growth.