The most expensive mistake happens before the first line of code is written.
Software rarely fails because of technical issues. It fails because no one took the time to observe how the people who are supposed to use it every day actually work. An incorrect user flow isn’t noticed until the rollout – and by then, correcting it costs many times more than it would have during the design phase.
Until recently, this was hard to avoid. A fully designed, clickable prototype took weeks to create, so it was usually developed only after the decision had already been made. That sequence has been reversed. With today’s tools, several fully tested user flows can be created in a matter of days – early enough to discard them.
This is exactly where we come in. Before your team commits to sprints, we make the planned workflow visible, clickable, and verifiable: using real tasks, with real users, and in multiple variations. What proves effective moves on to development. What doesn’t has cost you ten days instead of two quarters.
Which stage are you at right now?
Our services are organized based on your specific situation – not by our expertise.
We have an idea. But we don't yet have a sense of what it feels like.
Flow Sprint
We narrow down the target audience to two or three robust personas, design the complete user journey through the core task, and deliver a clickable prototype – all within ten business days. You can test it with real users before approving a development budget.
Our software can do everything. Yet people are constantly calling support.
UX Audit and Redesign
We analyze where your application is losing users – based on support tickets, usage data, and recorded sessions. You’ll receive a prioritized list: what’s causing problems, what it costs, and what fixing it will achieve. If you’d like, we’ll then implement the changes.
Design and development aren't working in sync here.
Design system, built for interoperability
We build your design system so that design and code share the same source: design tokens for color, spacing, and typography that are identical in both worlds, consistent components with variants, and a connection to your actual front-end building blocks. This is also essential for ensuring that AI-powered code generation adheres to your system rather than inventing its own variants.
We need to become accessible –and we don't know where we stand.
Accessibility according to the German Accessibility Improvement Act (BFSG)
The German Accessibility Improvement Act has been in effect since June 28, 2025. Among others, it applies to online stores, booking tools, and banking services for consumers; the only exceptions are companies with fewer than ten employees and an annual turnover of no more than two million euros. There is no transition period for websites. We test your application against EN 301 549 and WCAG 2.1 AA – both automatically and manually – and provide an action plan with a cost estimate.
We're building an AI feature. How do you actually design something like that?
Interaction Design for AI Features
AI features raise questions that traditional interfaces don’t address: How do you convey uncertainty? When does the system ask a follow-up question, and when does it act on its own? How can a user correct an incorrect answer without losing trust in the system? We design these moments – while taking into account the transparency requirements set forth by the EU AI Act for AI interactions and AI-generated content.
The Flow Sprint: Ten Workdays Until the First Reliable Answer
A clearly defined starting point that doesn't require a lengthy preliminary project. You give us an idea and introduce us to two or three people who will eventually use the software. Ten workdays later, we'll provide you with something you can demonstrate, test, and build upon.
| Day | What happens | Your result |
|---|---|---|
| 1–2 | Kickoff, review of existing data, discussions with users or user-facing roles within your organization | Personas and the one task that matters |
| 3–5 | Flow designs in various versions, generated with AI and curated by us | Two to three complete user flows |
| 6–8 | Development of a clickable prototype in your corporate design | A prototype you can showcase in-house |
| 9–10 | Testing with real users, evaluation, handover | Test Results, Recommendation, Implementation Rate |
The package includes a clickable prototype, a test report, and an implementation proposal that your development team can adopt immediately – either at our office or at your own. If you ultimately decide against the project, you will have invested ten days instead of a quarter.
Where We Use AI – and Where We Deliberately Don't
AI tools have made our work faster, not more arbitrary. Since this is an open question for many clients, we’ll tell you exactly which part is created by what.
| Step | AI Takes Over | We are responsible for |
|---|---|---|
| User Research | Transcription, clustering, initial analysis | Selection of respondents, questions, interpretation |
| Personas | Initial hypotheses based on available data | Validation on real people – never on simulated ones |
| Flows and Variants | Generating multiple alternatives in hours | Selection, Special Cases, Business Logic |
| User Interfaces | Designs based on your design system | Brand quality, attention to detail, consistency |
| Prototype | A clickable structure in hours instead of days | Test setup, facilitation, observation |
| Code | First draft from the design | Semantics, Accessibility, Performance, Review |
Four commitments
-
No fake users.
We do not use AI-generated test subjects as a substitute for real users. Simulated responses sound plausible, but they do not prioritize anything and do not reflect actual behavior.
-
No AI code without a review.
Generated code undergoes the same quality assurance process as any other code we produce.
-
No usage-based rates for your data.
We operate in team and enterprise environments using data processing agreements and standard contractual clauses – not in personal accounts.
-
No automatic guarantees when it comes to accessibility.
Based on an analysis of over 2,000 audits, automated testing identifies about 57 percent of the barriers that actually occur. People identify the remaining 43 percent. Both are part of our service.
For us, design doesn't end with the handover
Most friction in software projects arises during the transition: the design is complete, the development team is implementing it, and both sides are discussing discrepancies. We’re familiar with this transition from both sides – design and development are located in the same building at our company, working on the same projects.
That’s why our designs are technically compatible from the very beginning: with design tokens that are identical in the code as they are in the design, and with components that correspond to your actual front-end building blocks. To achieve this, we use our own toolset that connects product managers, designers, and developers: Changes to the templates are automatically exported and passed on in the correct format, rather than getting lost in a manual handoff process.
The practical result: You pay only once for the process from design to interface, not twice.
Frequently Asked Questions
We don't have any personas or user research yet. Is it too early to do a Flow Sprint?
No, that’s exactly right. The sprint begins with defining the target audience. What we need from you is access to two or three people who will be using the software later on – these can also be colleagues from the department or from support.
We already have a corporate design. Can you use it?
Yes. We'll incorporate your colors, fonts, or any existing components you have. If there isn't a design system in place yet, we'll lay the groundwork for one during the sprint; it will be developed separately.
What happens after the Flow Sprint?
The decision is yours. Either implementation begins – using our development or yours – or the project is scrapped. Both are possible outcomes. There is no obligation to continue working with us.
Does our data stay within the EU?
We use data processing agreements and standard contractual clauses, and we select the tools for each project based on the specific data being processed. When confidentiality is a priority, we do not use cloud-based AI tools. We will set forth in writing what applies to your project before we begin.
Do you also continue to work on existing products?
Yes. A UX audit is the standard first step when an application is already live. After that, we either work on a project-by-project basis or collaborate with the team on an ongoing basis.