We know the domain. And design the software for it.

Complex domain logic. Clear workflows.
You do not need to explain what a VIN is. We start with what makes your product specific: your data, rules, user roles and the decisions people make in their daily work.
We design clear paths for frequent tasks. Additional inputs and exceptions become accessible where they are needed, such as selecting a model and its equipment manually.
Capturing data on a tablet and continuing on a desktop are part of the same product. We adapt information, interactions and states to each context of use.
Shared components and interaction patterns give new modules a clear foundation. A design system connects existing areas with the next stage of development.
Realistic prototypes let you test critical workflows with your users. We define rules and states, align them with engineering and support implementation.
Fast for everyday tasks. Precise in the details.
We design clear paths for frequent tasks. Additional inputs and exceptions become accessible where they are needed, such as selecting a model and its equipment manually.
Usable at the vehicle and at the desk
Capturing data on a tablet and continuing on a desktop are part of the same product. We adapt information, interactions and states to each context of use.
A consistent foundation for growth
Shared components and interaction patterns give new modules a clear foundation. A design system connects existing areas with the next stage of development.
Validate decisions before implementation
Realistic prototypes let you test critical workflows with your users. We define rules and states, align them with engineering and support implementation.
Your starting point
More features, more exceptions
- Vehicle data, equipment variants and different roles come together in one application. Among all these options, the common task becomes harder to find.
Established software, new requirements
- Your customers know the existing workflows. At the same time, the product needs to work on new devices and remain consistent as it evolves.
Modernise the UI
- Your product works, but its interface feels dated. You want a contemporary, consistent interface with a clear visual hierarchy while preserving familiar workflows for your customers.
Integrate AI features
- You want to bring AI into existing workflows, such as extracting data from vehicle documents, finding information or preparing inputs. We clarify the use case and design how users review, correct and accept suggestions. Data access and technical integration are agreed with your engineering team.
An idea for a new product
- The domain knowledge is there. Which users, workflows and features should define the first version is still an open question.
Close to your product. Directly with your team.
Together, we clarify your workflows, business rules and next product goal.
We join where you need us – including a single workflow or module.
We join where you need us – including a single workflow or module.


Software should feel good to use. Make work easier. And explain itself. Even when the data is complex. That is exactly what we design automotive software for.
What to know before getting started.
We have defined, designed and built the frontend for a connected B2B workflow covering vehicle capture, model and equipment configuration, valuation, trade-ins, quotes and contracts. We clarify your product-specific rules with your domain experts.
Yes. We can start with a core workflow or a single module. Together, we clarify which familiar patterns should remain and where changes make sense. We incorporate existing concepts, designs and technical foundations.
We align user flows, components, states and interfaces with your development team early on. Depending on the engagement, we deliver design and documentation, support implementation with reviews or take on an agreed frontend area.
Yes, where the scope and technical requirements fit. We develop based on our own or existing concepts and designs. We selectively take on backend development and operations on our Node-based SaaS stack, with explicitly agreed requirements for security, integrations and responsibilities. Existing .NET or Java backends remain with the team responsible for them.
A short description of your product and the task ahead is enough for an initial conversation. Together, we define the desired outcome. You receive an individual quote with a fixed total price for the defined scope. Extensions are agreed separately. A focused review or prototype is also possible without a subsequent full project.
Let’s talk about your automotive software. We bring industry experience to your next product decision.

Marco or someone from the team will get back to you, within 24 hours on working days.
