From our experience, we have described here some payment patterns. If none of these seems convenient to you, though, please fell free to suggest any other pattern which would suit you fine, as we are always willing to discuss ways and means.

    If this way of payment is chosen, our customer has not to pay for the development until after delivery of the complete solution. As a rule, costs of development are calculated when the Design and Architecture stage is over and development and QA plan ready.

    This pattern is usually perfect for small-scale software products where project involves 3-5 specialists and lasts for 1 month at most; such as web designing for a small business.

    Advantages: The complete solution shall be postpaid.
    Disadvantages: Limited project time and complexity.

    This pattern is also good for a starting stage of cooperation, such as the Pilot Project, since it enables our prospective customers to appreciate quality of our work with no financial risk involved.

    If this way is chosen, software development is divided into phases which can be easily supervised, and each partial payment is effected upon completion and handing-over of each respective phase works.

    This pattern allows our customers both the absolute control of their project progress and payment just for actual development results they can check and approve, while a final payment will not have to be effected until the goods are delivered.

    Advantages: Medium term and complexity projects are possible.
    Disadvantages: When a project is large-scale and long-term, with a lot of developers involved, following such procedure makes budget calculation and payment scheduling quite difficult.

    This way of payment usually proves convenient in case of systems, which cannot be confined within the Fixed Price Project because of their long-term or complex development, although not so long-term and complex as to call for a good many developers.

    If this way of payment is chosen, our customer has to pay for net development or QA testing hourage.

    In order to let our customer know and check such net hourage, as well as general development progress and effective time spent by each developer or QA engineer, we have introduced efficient planning and reporting systems.

    This pattern is perfect for complex and resource-intensive software projects where various development stages may call for a various number of experts involved.

    If this way of payment is chosen, our customer pays for net development or QA testing hourage per calendar month.

    In order to let our customer know and check such net hourage, as well as general development progress and effective time spent by each developer or QA engineer, we have introduced efficient planning and reporting systems.

    This pattern is perfect for any long-term project in which our regular development and QA team is involved, as well as for IT Outsourcing / Outstaffing.