Structure and usability
Pages, screens and key user journeys follow the task. Website planning includes mobile presentation, clear content and a straightforward way to get in touch.
Software development
We build websites, web applications and internal tools. A specific requirement becomes a defined product with understandable controls and the necessary connections to your systems.
You need a new website, a focused extension or an application that existing software cannot reasonably support. We discuss users, features and technical constraints before defining implementation.

Pages, screens and key user journeys follow the task. Website planning includes mobile presentation, clear content and a straightforward way to get in touch.
We build the agreed features and connect the required interfaces. Existing components and systems are considered so that the solution fits your environment.
The agreed scope includes appropriate checks and implementation documentation. Operation, maintenance and later extensions are discussed explicitly.
We clarify users, main tasks and existing systems to define a first version with clear acceptance criteria.
Interim versions make design and behaviour visible early. Feedback can be incorporated before details become unnecessarily expensive to change.
We test agreed functions and relevant screen sizes. Release, responsibilities and handover are prepared together.
The scope depends on your project and existing systems. Choose a starting point for your enquiry.
A new or refreshed website with a clear structure, useful content and a working enquiry flow.
Select, configure and connect existing systems when an established solution can support your process.
Software or automation for requirements that existing tools cannot reasonably meet.
Yes. Website creation is a delivery service covering structure, design, content, technical development and agreed integrations. It does not mean general business consulting.
When important requirements are not adequately covered by existing systems or adapting them would become disproportionately complex. We first assess whether an available solution is sufficient.
In principle, yes. We first need to review the code, usage rights, dependencies and operating environment. A sensible scope can then be agreed.
These are defined in the specific proposal. Responsibilities, maintenance, operating costs and access to the implementation should be clear before work starts.