During the time that we are engaged in the creation of corporate systems we have developed a set of principles the observance of which helps us and our customers successfully implement projects.
After the traditional stage of a survey of customer’s working processes and collecting the customer’s wishes about the functionality he would like to see in the future system we develop a pilot version of the system and offer it to the customer for the observation.
The observation brings a list of tasks for changes and development of the system according to customer’s wishes. We make the appropriate refinement and provide a system for the observation again, and so on until the moment when the customer considers the system (or some of its modules) suitable for implementation.
Such an approach allows us to come to the implementation stage with confidence that the adaptation of the system after the commencement of the implementation process will be minimal and will not affect neither timing nor resources.
We respect the interests of our customers and understand their risks associated with the creation and implementation of modern complex computer systems.
Also, we are confident in our ability to create systems that meet the needs of our customers.
Therefore, the customer pays only after he has ascertained the suitability of the system or module for the implementation and use. Thus we remove our customers’ risks that they will pay not for what they would like to have.
improvement and facilitation of employee’s work with the help of a new system, not only for top management but for all future users of the system.
Therefore we carefully listen to all users at different levels to facilitate their work and improve their efficiency.
Implementing such proposals within a system is the aforementioned "bonus" which every user gets.
The main thing is that our customers can afford such an approach within the system implementation because the accomplishment of such proposals insignificantly effects the budgets of projects.
One of the main arguments against bespoke systems is the assumption that the Customer becomes dependent from the creator of the code.
The program code of our systems is written in one of the most common programming languages (PHP) and has a typical structure, it is well understood by any experienced programmer.
The open source code allows the customer to take actions that allow removing such risks. Throughout the time of the system operation the customer has an opportunity to study the source code which gives a confidence in the stability of operation and professional support of the system in all possible situations.