Frequently Asked Questions
Do you work on existing systems or only new projects?
Both. Some projects start from scratch, others involve improving, restructuring or extending existing systems.
Do you also build software or only design systems?
Both. We design systems, but also implement them. That includes architecture, development, testing and long-term evolution. The goal is not just to define a solution, but to make it work in practice.
Do you work with a fixed tech stack?
No. Technologies are chosen based on the problem — not the other way around. The stack depends on the context, constraints and long-term goals of the system.
Can we first explore if there’s a fit without commitment?
Yes. A first conversation is meant to understand the context, the problem and whether there is a good match. There is no obligation — it’s simply a way to explore if and how we can help.
Who owns the code?
You do. All code and deliverables belong to you. The goal is to build systems that you can understand, maintain and evolve independently over time. At the same time, we take responsibility for the technical direction — making architectural and implementation choices that best fit the problem, context and long-term goals.
Do you work time & materials or fixed-price?
Both are possible. The choice depends on the nature of the project. For well-defined scopes, a fixed-price approach can make sense. For more complex or evolving work, time & materials is often more appropriate. This is always discussed upfront, so expectations are clear.