Let's build something.

We do not publish a fixed price list because the same feature can require very different work in different systems. After an initial conversation, we provide a written range, the assumptions behind it and a clear recommendation for the first useful scope.

New. We are building the company carefully, so we are not using client logos, testimonials or case studies before we have permission and evidence to publish them. You can judge us by the quality of the conversation, the clarity of our thinking and the working preview we create together.

Yes, when the scope suits a focused senior team. We limit the number of projects running at once and explain early if the work needs specialists or capacity beyond the two of us. In that case, we either shape a smaller first phase or decline the project.

We aim to make progress visible in the first two weeks, usually through a working environment, prototype or technical proof. The exact form depends on the project. From there, each increment ends with something concrete to review.

Ownership is agreed clearly in the proposal and contract before work begins. Your data remains yours. For commissioned software, the agreement explains which source code and usage rights transfer to you, and which reusable or third-party components remain under their existing licences.

Yes. We can lead a defined piece of work, add product or engineering capacity, or collaborate through a gradual handover. Responsibilities, access and decision ownership are agreed before delivery starts.

We can continue with maintenance and product development, or hand the system over with the documentation and training your team needs. We agree that path early and keep the code ready for it throughout delivery.

Yes. We can review your documents or provide our own once the company setup is complete. Tell us early about security reviews, penetration tests or supplier questionnaires so the requirements can shape the plan from the start.