Menu

Digital tools for specific workflows

We build small applications for tasks where existing software falls short – because it's too big, too complex, or simply not made for that specific workflow.

From the first draft to the finished tool: designed from a designer's perspective, built for the people who use them.

Let's discuss your workflow!

Software from a designer's perspective.

There are already enough powerful systems that can do everything. We are interested in what they often cannot do: make a specific workflow so simple that people actually enjoy using it.

That is why we don't start by asking what features a software needs. We start by understanding who uses it, what that person wants to achieve, and where today's process is unnecessarily complicated.
The result is deliberately small: an application that supports precisely the workflow it was built for.

One workflow. Fewer functions.
We build for a concrete task – not for every conceivable case. Therefore, every tool gets only the features that truly make that workflow better. What isn't needed doesn't go in.
The first version doesn't have to do everything. It has to work in everyday use.

What we have built

Each of these tools grew out of a specific problem. Not from the question of what software we can sell, but from the question: What makes this workflow unnecessarily difficult?

 

 

01 / Time Tracking

Less time spent on time tracking.

The problem

Our own time tracking used to be more cumbersome than it needed to be. Recording hours, assigning tasks, entering things retroactively – a small administrative routine that still kept eating up time.

What we built

A custom time-tracking tool tailored precisely to our everyday work. No bloated project management system. No features we don't need. Just the workflow we actually use every day.
 

 

 

The result

Since building it ourselves, we only need a fraction of the time we used to spend on time tracking. The workflow has become simpler – and no one ever needs to be reminded to get it done.

 

02 / Language Processes

Language versions in 40% of the time.

The problem

A client publishes documents in multiple languages. Previously, every change to the source version triggered a chain reaction: translation, layout, proofreading, approval. By the time all versions were updated, the source document was sometimes already outdated again.

Lo que hemos construido

Una línea de traducción que convierte los documentos a los idiomas necesarios y reintroduce los contenidos directamente de vuelta en la maquetación.

 

 

The result

40% of the original turnaround time. At the same time, it reduces the number of errors caused by separately managed language versions – such as differing product names or corrections that didn't make it into every version. The number of languages is secondary here; twenty are hardly more effort than three.

What tool do you need?

You know what you want to achieve, but not yet which tool will support you along the way?

Let's talk!

 

03 / Approvals

125 assets. Five languages. One approval pipeline.

The problem

A campaign with 125 assets in five languages. Relying on email and phone quickly makes it confusing to track which version is current, which feedback has already been incorporated, and which language version is still pending.

 

What we built

An application where all versions are stored in one central place. Feedback is given directly on the asset itself. The approval status is visible at all times – even for those responsible for only a specific section.

 

 

The result

Feedback stays in one place – across all rounds of approval. Previous notes remain traceable, and nothing gets lost. At the same time, it is visible at any time what is new, what has already been approved, and where something is still pending. Questions can be asked and resolved directly on the respective asset. Thus, many separate alignment loops turn into a transparent, trackable approval process.

 

04 / Product Knowledge

Finding answers without knowing the right category.

The problem

A manufacturer had already documented its product knowledge – in manuals, data sheets, and internal guides. The information was there. Finding it reliably was the problem. Anyone with a question first had to know under which term the answer was filed.

 

What we built

A knowledge base as a primary point of contact. Questions can be asked in full sentences, just as you would ask a person. Relevant sections from the existing documents are displayed directly – complete with the source.

 

 

Search is not the problem
Search technology is a mass-market product today. The actual work lies in preparing the existing material in such a way that meaningful and traceable answers are produced.

 

Our contribution:
Understand the content.
Structure the material.
Design the interface.

The right solution begins with your workflow

We don't start with software; we start with your workflow. Together, we look at where friction arises, what can be simplified, and which small step brings the greatest benefit.

Next, we build an initial, streamlined solution, test it in real-world use, and improve it step by step. What isn't needed stays out.

Thanks to modern development using AI, such bespoke tools can now be implemented significantly faster and more cost-effectively – even for small teams. You don't need your own IT department or a traditional software rollout to make it happen.

Let's discuss your workflow!