Good to know.
Before we start.

We design and build websites, landing pages, funnels, web applications and client portals. That includes brand and interface design, and connecting digital systems.

Whether your specific project fits is something we clarify from your requirements. An overview is on the services page.

It depends on the scope: number of pages, design, content, features and integrations all make a difference. After the first conversation you receive a proposal with the work clearly described.

If you name a budget range, we can judge early which starting point makes sense and which features to prioritise.

No. An idea, or a description of the problem, is enough for the first contact. It helps if you can say who should use the result and what should get better because of it.

Structure, content and the set of features are then worked out within the agreed frame.

No. The inquiry is how we get to know the project. A contract exists only once the collaboration and its terms have been expressly agreed.

A single landing page and a portal with several user roles have very different requirements. We agree the schedule once the scope is clear.

Existing content, the access we need and the pace of feedback also affect the build. You can name a preferred start or launch date in the inquiry.

Depending on the project, existing brand documents, text, images and information about your services are helpful. For an existing website or system, the relevant access may be needed.

You receive an agreed list of what is required. Missing content is discussed before it becomes an open task.

Yes, if the current foundation is suitable. We look at where things stand and discuss what can be carried over and what should be built anew.

That lets us weigh a focused revision against a full relaunch.

We review important milestones together. You give feedback in gathered form where you can, and we work it in within the agreed rounds of revision.

The number and extent of those rounds are part of the project agreement. New features or larger changes of direction are discussed separately before extra effort begins.

Yes, that can be part of the project. We clarify which content already exists and where support with writing, design or imagery is needed.

The choice and use of external or newly created material is agreed with you. If extra licence costs arise, they are discussed beforehand.

Depending on the task, AI-supported tools can help with ideas, design, text or engineering. What matters is whether the result fits your project in substance, design and engineering.

Project requirements, the tools used and the handling of your data are agreed specifically when that is needed. Sensitive content does not belong in external services without a check.

If you want to change content yourself on a regular basis, we plan a suitable way to manage it. Which areas should be editable is agreed before we build.

For smaller pages that rarely change, a leaner technical solution can also make sense. The decision follows your working day.

Yes. Those features belong to custom web applications and portals. Together we define which data is needed and which users may see or change which content.

The technical approach is matched to the features and requirements of your project. More on web apps & portals.

That is possible when those systems offer suitable access or interfaces. Typical cases are forms, booking tools, contact management or transferring project data.

Feasibility, limits and possible ongoing costs are checked before we build. More on automation & integrations.

The handover is set out in the proposal. It can include project files, exports, source code, access and documentation.

Rights of use, and any existing third-party licences, are considered separately. So it is clear before the start what you receive and can continue to use.

The domain, hosting and, depending on the project, further services usually have ongoing costs. These are considered separately from the one-time project work.

We discuss which services are needed, who manages the accounts and which costs can be expected. Existing setups are included when they fit the project.

Later support can be agreed separately. It can include content changes, technical care, help with questions, or developing features further.

What is included, and response times, follow the agreement. So it stays clear which support is covered.

In principle, yes. If you plan more pages, features or integrations, we look at the existing foundation and the extra effort.

Known next steps are considered in the concept where we can. That separates a sensible first scope from later extensions.

A well-built website can make it easier for visitors to understand your offer and get in touch. How many inquiries follow also depends on demand, reach, the offer and pricing.

We therefore do not promise blanket results. Instead we design clear ways to get in touch and discuss which goals, and which measurement if any, make sense for your project.