Websites that build trust and bring you inquiries.

Q&A

Still have questions?

Here are the questions I get asked most often.

• Who owns the website afterwards?

  You do. Domain, hosting access, content, and the finished code run through accounts registered in your name and are handed over to you. You keep full control of your website.

• What does a project cost?

  The price depends on the project range, so I never pull a number out of thin air. We talk about your goal and the actual effort first, then you receive a written fixed-price offer with no hidden items. Anything that comes up later is agreed with you in advance.

• How does project kickoff work?

  Project kickoff means onboarding with me: we look through the available assets, go through the ideas in detail once more, and define how the site should look in the end. I also need the access, photos, videos, and any other material required to build the website so I can start cleanly.

• How many revision rounds are included?

  How many are included exactly depends on the project. We decide that individually and spell it out in your offer. Anything beyond that is agreed in advance.

• What is typically not included in the offer?

  What is usually not included: hosting, domain, external tool or license costs, and integrations outside the agreed project range. I normally write the texts myself unless you explicitly want it differently. Images and videos are ideally provided by you; if nothing is available yet, I can use AI or stock material for the time being.

• What happens after launch?

  I do not disappear after go-live. Usually that moves into ongoing maintenance or support if you want it. It matters to me to keep supporting clients reliably and professionally after launch. In theory, though, you can also take over the website and keep it running without any further collaboration. What comes next depends on what makes sense for you.

• Can I edit the content myself later?

  Yes. As a rule I handle changes for you: you send me a short message about what needs updating and I take care of it. For most clients that is the faster route. If you would rather maintain content yourself, we build in a CMS and discuss that before the project starts.

• What do I need from you for a clean start?

  I need timely feedback, approvals, the required access, and, where available, your texts, images, and videos. Most of that happens once, during onboarding. If responses take longer, the timeline shifts accordingly.

• How are additional requests handled?

  Requests outside the agreed frame are not implemented silently. I first share the impact on effort, timeline, and price, and proceed only after short written confirmation by email.

• Which tools do you use?

  I work with Next.js, Tailwind, Vercel, and Resend. The stack stays deliberately lean: fast load times, little maintenance, no unnecessary dependencies. Technical responsibility for architecture, review, and QA stays with me.

• When is a project considered completed?

  A project is complete once the agreed scope has been delivered and the site is live or handed over. Anything after that is treated as its own follow-up assignment if it goes beyond the agreed frame.