How we would like to work together

We are convinced that a successful partnership is based on trust, honesty, transparent communication and pragmatic efficiency. Below we have listed a few key points on how we would like to structure our collaboration in order to implement projects as smoothly and results-oriented as possible.

We have general guidelines

Together with our team, we have developed guidelines to create a pleasant and positive working environment. Our aim is to promote an atmosphere in which everyone feels valued, supported and inspired. These general guidelines should also form the basis for collaboration with our customers and partners.

What do we specifically want when working with our customers? 

Rather "you" than "you" 

We believe that mutual respect has nothing to do with formality of address. We want to work in partnership with our customers as equals and therefore like to maintain relaxed and trusting communication with our customers – by being on first-name terms. We believe that friendly and trusting communication forms the basis for successful collaboration. 

A handshake is better than a contract 

Contracts are undoubtedly important, but we often rely on the trust and integrity of a non-bureaucratic "handshake" – or a simple verbal or textual commitment. We always strive for transparency and fairness and benefit from long-term partnerships. We want a relationship of trust in which both sides can take it for granted that promises will be kept and that fair solutions will be found in case of doubt. 

Better agile than waterfall 

In principle, it has been known for over two decades that the traditional waterfall model in project management is unsuitable for software development. Software projects are not linear and cannot be planned in detail in advance. For good solutions, we also need a high level of customer involvement and the opportunity to incorporate new findings by changing requirements. The waterfall model does not provide for either of these, which is why a large number of agile PM methods have now been devised by very capable people. Agility allows us to react flexibly to changes and constantly receive feedback from our customers for improvements. We are convinced that continuous collaboration and adaptation during the project leads to more cost-effective and better results. 

Better digital than paper 

Paper is a wonderful medium. However, with our digital orientation, we have the most contact with paper in bureaucratic processes. We deal a lot with the digitalization of administrative and business processes for professional reasons alone and consider the use of paper to be completely unnecessary and outdated in this area. A declaration of intent or data has no greater value on paper and is no more forgery-proof. In our highly digitized everyday office life, most paper documents are either scanned or destroyed in the end - or both. This consumes unnecessary resources, which is why we want to consistently rely on digital documents. 

Asana is better than email 

Due to its enormous acceptance and prevalence, traditional e-mail is a very low-threshold form of digital communication. However, due to the daily flooding of our email inboxes and the inefficiency of lengthy coordination, especially with several people, it is of little use. To organize projects efficiently, we rely on project management tools such as Asana, which enable clear task distribution and tracking. We would rather use our time to develop helpful solutions for our customers than to sift through email inboxes. 

Budget rather than price 

Since we develop individual products together with our customers, it is generally very difficult for us to talk about prices. We don't take a finished product off the shelf that we can sell, but rather work out the details of the end product together as the project progresses. This does not mean that we cannot work with limited financial resources, but we think in terms of budgets and not prices. This offers flexibility to respond to changing requirements, promotes customer-oriented cooperation and enables a stronger focus on good results. 

Better finished than perfect 

We are absolute perfectionists and can fully understand any quest for perfection. However, perfection must never stand in the way of a good result that could be used. In principle, our software products are never finished and changes are always possible. With our user-centered products, however, it is extremely important to get them into use as quickly as possible in order to receive broader feedback for improvements. Instead of "finished", you could also say: "released" is better than perfect.