It is important to us that software developers think along with us and do not implement specifications bit by bit. This gives a concept the chance to be meaningfully improved even during implementation.

We value an iterative and agile approach to software development. In this way, the developed solution can be tested parallel to the project and feedback can be included in the further development at an early stage.

A software development project – realistically speaking – cannot be specified in detail in advance. Let us be agile in your project. This significantly improves the quality of the solution and greatly reduces the risk typically associated with development projects.

The twentyZEN framework forms the basis for interactive web applications with support for various hybrid mobile apps for the interaction of different user groups.

An example of this is a logistical application. Orders between customers, drivers and the head office are arranged and invoiced. Our framework forms part of the overall solution and is linked to the customer’s existing IT backend.

The webZunder framework forms the basis of our social media management platform webZunder.com. This includes the following functions:

• a user administration with various registration options
• a responsive user interface
• Integration of external services as information sources via API
• Output of information to external services via API
• Scheduling of actions
• Invoicing via a payment service provider

We rely on agile software development – this has advantages for you! At the beginning of the project we define the goal together. At this point in time, the level of detail defined for the conversion is not yet very high. Nevertheless, this allows a first rough estimation of the effort.

We divide the “way” into so-called sprints. Depending on the scope of the project, these are typically project phases of 14 days to one month.

Sprint by sprint we refine the exact “route”. In this way we achieve our common goal and avoid unexpected surprises, which often occur towards the end of a project in classic project planning.

The agile approach seems at first glance to be difficult to estimate in scope. In contrast, a classic project planning with a fixed price offer seems to be the safer choice with regard to budget planning. Reality shows that precise precision landing is rarely possible.

The model of an “agile fixed price” combines the advantages of both approaches: the agility is maintained and a target budget is also set. If the project scope and the framework conditions do not change during the project, the price remains unchanged.

A more efficient implementation rewards both, you as the client and us by sharing the savings. If the completion takes an unforeseeably longer time than we estimated at the beginning, we share the additional work.

Modern software development projects are increasingly being integrated with other systems. This is very useful when it comes to integrating complete function blocks (e.g. payment processing, invoicing, etc.) or connecting communication channels. This is done via Application Programming Interfaces (API). Through our development of webZunder we have gained experience with various interfaces, so that we do not list them individually.

You can be sure: as soon as an application offers an API, we will be able to integrate it.