esp fra deu por




esp fra deu por

Items: {{calculateProductsNum()}}

Go to cart

LITE x{{liteItem.quantity}}

$ {{liteItem.price}}

Update subscription x{{liteItem.quantity}}

$ {{liteItem.license.price}}

PRO x{{proItem.quantity}}

$ {{ proItem.monthly_status ? proItem.monthly_price : proItem.price }}

{{}} x{{proItem.quantity}}

$ {{ proItem.monthly_status ? module.monthly_price : module.price }}

Update subscription x{{proItem.quantity}}

$ {{proItem.license.price}}


SERVER, Connections: {{serverRedaction.serverConnections}} x1

$ {{serverRedaction.offers[serverRedaction.serverConnections].price}}

Update subscription

$ {{serverRedaction.license.price}}

Licenses renewal

License renewal {{itemUpdate.lic}} x1

$ {{itemUpdate.updateLic.price}}

License renewal {{itemUpdate.lic}} x1

$ {{ itemUpdate.updateLic.price }}

License renewal {{itemUpdate.lic}} x1

$ {{itemUpdate.updateLic.price}}

Add.connections for Server: +{{newServConn.updateLic.connectionsNum}} x1

$ {{newServConn.updateLic.price}}


$ {{parsePrice(module.price_en)}}



$ {{parsePrice(service.price_en)}}

total $ {{ calculateFullPrice() }}

Principles of pricing

Fix price

Fix price

Based on "the waterfall model", using in software developing, when all requirements are clearly formulated and do not change until the completion of all work on the project
Time and materials

Time and materials

Based on "time and materials model", when requirements can be developed and changed in the course of project implementation, and labor costs are paid based on the number of people employed on the project and the time spent on producing the functionality of the developed product

An example of an algorithm for working on a project, implemented with the use of "Time and materials model" pricing:

  • 1 Identification of terms, prices, as well as general requirements for the system, specification of requirements, generation of the initial prototype and the list of detailed requirements of the system version V (where V = O)
  • 2 Joint planning of implementation of priority requirements from the general list for the V-version system
  • 3 A two-week (or more) implementation of a version V system with the requirements approved in step 2 and send it to the customer
  • 4 Correction of requirements (if necessary), reorganization of the list of detailed requirements to the system of the new version V (where V = V + 1)
  • 5 If the list of requirements is not empty, go back to Step 2, if the list is empty, - we release the final version of the system and support it for the agreed time
Please wait There is a
sending of form data
and attached files