Fair Contract

To us, fairness is the basis for a long- term successful coop. Our project contracts are designed so that you as a customer will receive the necessary transparency and flexibility to steer our common project to fully meet your needs at any time.

A fair contract design allows us to concentrate fully on the development of your product and does not waste time negotiating contract details or what a change or defect is. We don’t want you to be bound to us by a contract, but by the high quality of our work.


1The quality of our implementation is not determined by a rigid specification, but by your current require­ments. If you do not like the implementation of a prod­uct function at the end of an iteration, you do not have to pay for it. We will then fine-tune it until you are satisfied. However, the conti­nious involvement of custo­mer represen­tatives du­ring implemen­tation ensures that this case does not usually occur.


2You can finish the project after each iteration, i.e. ev­ery 1 to 4 weeks. If, for example, you are of the opinion that the functionality imple­mented so far is sufficient for your purposes, you can end the project at the end of the current iteration. In practice, it can happen that customers have changed a large part of their original requirements and achieved their project goals below the originally planned budget.


3 We offer you differ­ent ways to pay for our services. We have made the best experiences with Pay per Hour, because in this way the highest transparency in the project is achieved. In combination with regu­lar inspections and flexible exit options, a win-win situation is guaran­teed.
However, you can also pay by volume if you do not feel comfortable with purely expense-based pay­ment. We call this Pay per Point: The scope is estimated in points per requirement. However, we do not offer a classic fixed price, since in our experi­ence there is always a loser here.


4 An important factor in the satisfaction of customers, sup­pli­ers and their employees is, in addition to quality, pricing. Nobody wants to pay too much or earn too little. As a nearshore ser­vice provider, we are able to offer significantly lower prices than local software companies. We are and do not want to be the cheapest, because we know that quality also has its price in Bulgaria. We pay this price in the form of fair wages and addi­tional services for our employees.


5According to agile understanding, the detailed specifi­ca­tion of requirements be­fore a project and the subsequent explicit man­age­ment of change re­quests is a waste. In agile projects, requirements are therefore only docu­mented to the extent that a rough estimate and planning is possible. The details are then clarified immediately before and during their implemen­tation. Short delivery cy­cles and the continuous involvement of the cus­tomer provide the neces­sary transparency to quickly adjust estimates and planning. Experience shows that this empirical, flexible approach leads to considerably higher cus­tomer satisfaction at lower project costs.